Re: [rtcweb] Support of SDES in WebRTC

[Randell Jesup <[e-mail]>]

On 3/29/2012 5:59 PM, Gregory Maxwell wrote:
> Oscar Ohlsson [[e-mail]] wrote:
>> That's why I wrote "the entire webapp" below. If it was not clear I meant that the
>> - main HTML page
>> - all external CSS files, JavaScript files, images, etc
>> - all XmlHttpRequests
>> - all WebSocket connections
>> are protected with TLS. This is obviously verifiable and it's a feature supported by all modern browsers (no mixed content).
>
> Even this is insufficient.

[long nice analysis of security in JS vs in the stack deleted]

>  Really, cryptographic
> negotiation is not properly an application feature, it belongs lower in
> the stack, and many applications that roll their own crypto have done
> a poor job of it.
>
> It's also inadequate on purely technical grounds: Javascript provides
> no mechanism for working with mlocked memory,  no mechanism to ensure
> that garbage collected data gets zeroized.  Your crypto app in JS could
> easily have its long term keying material pulled out of free ram by
> malware long after it runs, or pulled off the disk from swap.
> The breakneck pace of fancy JIT systems makes it seem unlikely to me
> that javascript will provide for that any time soon.

I rarely do this sort of reply for obvious reasons, but:

I agree!  :-)

-- 
Randell Jesup
[e-mail]