On Sat, 4 May 2002, Mikael Olsson wrote: > > In a world where very smart, very well-known vendors with crypto > > products have initialization vector issues in shipping products, > > That one did put a big dent in my view of the world. I mean, argh, > predictable IVs _by definition_ defeat the purpose of having an IV > in the first place.
The fact that it's happened more than once kind of did it for me. ICSA Labs *only* reports on products which have *passed* certification (and therefore the vendor has FIXED the issues necessary to comply with the criteria, including non-predictable IVs.) I know of at least two others which aren't reported here. Here are five that were reported by the Labs: http://www.icsalabs.com/html/communities/ipsec/lab/notes/10b/intel_3130VPN.shtml # Original version submitted was 6.81p2 which had a repeating IV problem. Version 6.81p4d2 was then submitted however this was creating IV's by taking the last 8 octets received and using it as the IV. The IV problem was corrected in version 6.81p7 using Manager version 6.81p2. http://www.icsalabs.com/html/communities/ipsec/lab/notes/NetScreenOS.shtml * During initial testing four problems were discovered: 1. Non-random IV's After testing against seven products before testing against TimeStep with no major problems observed Mucho started sending a constant IV. The only time the IV was observed changing was following a QM and occasionally following an info packet. This constant IV problem which is unacceptable using DES-CBC was corrected in a new image build. http://www.icsalabs.com/html/communities/ipsec/lab/notes/10b/IBM_390_V2R8.shtml # During initial testing, the IV's were observed to be constant. PTF UQ47405 was applied then later APAR PQ54013 was applied. The IV's are now observed randomly changing. http://www.icsalabs.com/html/communities/ipsec/lab/notes/10b/avaya_vsu100_3166.shtml # Crypto Lab discovered non-random IV's being used. This was corrected in version 3.1.51. http://www.icsalabs.com/html/communities/ipsec/lab/notes/NAI_Webshield.shtml * Initial testing disclosed duplicate IV's. This problem was corrected with gvpn.patch.1a.shar. When executed created a subdirectory. In this subdirectory ./apply was executed. It'd almost be cool to have a security product auditing requirement that standardized the reporting of fixed bugs kind of like an accounting audit reporting requirement. Paul ----------------------------------------------------------------------------- Paul D. Robertson "My statements in this message are personal opinions [EMAIL PROTECTED] which may have no basis whatsoever in fact." _______________________________________________ Firewalls mailing list [EMAIL PROTECTED] For Account Management (unsubscribe, get/change password, etc) Please go to: http://lists.gnac.net/mailman/listinfo/firewalls
