[squeak-dev] Crypto support?

Nicolas Cellier nicolas.cellier.aka.nice at gmail.com
Tue Nov 19 21:27:23 UTC 2013


It's because crypto must not rely on pseudo random generated numbers, they
are considered too easy to crack.
I guess that sound input was seen as a universal way to get some hardware
noise...
Nowadays, shouldn't it be something like /dev/random?


2013/11/19 Frank Shearar <frank.shearar at gmail.com>

> Does anyone know the current state of play of the crypto team?
>
> We have a DSA implementation in "System-Digital Signatures" that
> should belong in a package called "Crypto-Something", but if the other
> stuff was better I'd rather delete this and use the proper stuff.
>
> Also, we need a better encapsulated source of randomness than
> "SoundService default randomBitsFromSoundInput: 512" because crypto
> shouldn't depend on a sound package. I don't care if something _plugs
> that in_, but the direct reference is suboptimal.
>
> frank
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20131119/6dea6c62/attachment.htm


More information about the Squeak-dev mailing list