BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] AeroFS
- Subject: [Discuss] AeroFS
- From: richard.pieri at gmail.com (Richard Pieri)
- Date: Sun, 20 Apr 2014 11:29:40 -0400
- In-reply-to: <li6oazw6naq.fsf@panix5.panix.com>
- References: <CAL8cYW1fEhj-reUNptW4+vfU5nywX-OB0=PCKUOQE_Vt1qCD=A@mail.gmail.com> <5352BED2.7020908@gmail.com> <5352E966.5020102@gmail.com> <5f076efda37e4520883033872ccf6dc9@CO2PR04MB684.namprd04.prod.outlook.com> <li6oazw6naq.fsf@panix5.panix.com>
Mike Small wrote: > How do you examine closed source crypto? It's a fair argument that the > code being available isn't sufficient to have all its bugs (intentional > or normal) found, but if the code's not available at all... That's both simple and not so simple: you compare what should be deterministic results, and you look for deterministic results when there should be none. In other words, you attack the closed cipher or hash implementation of an algorithm the same way you would attack an open source implementation of that algorithm. -- Rich P.
- Follow-Ups:
- [Discuss] AeroFS
- From: smallm at panix.com (Mike Small)
- [Discuss] AeroFS
- References:
- [Discuss] Ubuntu One file services
- From: genuineaudio at gmail.com (Stuart Conner)
- [Discuss] Ubuntu One file services
- From: richard.pieri at gmail.com (Richard Pieri)
- [Discuss] AeroFS
- From: tmetro+blu at gmail.com (Tom Metro)
- [Discuss] AeroFS
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- [Discuss] AeroFS
- From: smallm at panix.com (Mike Small)
- [Discuss] Ubuntu One file services
- Prev by Date: [Discuss] AeroFS
- Next by Date: [Discuss] Good and Bad Crypto
- Previous by thread: [Discuss] AeroFS
- Next by thread: [Discuss] AeroFS
- Index(es):