On Wednesday 22 October 2014 15:54:57 Julien Pierre wrote:
Hubert,
On 10/22/2014 05:27, Hubert Kario wrote:
Problem is that if something doesn't work in one browser and does in
another users blame the browser. Even if the browser that doesn't work
does the right thing.
What if all
Forwarding to dev-tech-crypto where this is more on-topic.
-Dan Veditz
---BeginMessage---
NSS was designed when physically distributed smart cards were anticipated to
become the norm.
This didn't really happen but instead we got mobile devices with support for
TEEs (Trusted Execution
Hubert,
On 10/23/2014 07:53, Hubert Kario wrote:
Are there phone/tablets which can't install any 3rd party browsers at all ?
AFAIK, iOS devices require you to use the system TLS stack.
I see, I didn't know.
But it still would seem that any second connection (fallback) would be
dictated by
Your subject, time to dump NSS, intimately affects NSS developers who
will have to worry about replacing all the things NSS does for us before
they can even start to think about the additional concepts.
If you're proposing a mechanism that can live on the side without
actually dumping NSS then I
4 matches
Mail list logo