At 04:00 PM 7/10/99 -0500, Steve Hawkinson wrote: >Does anybody have any ideas on what would be a good algorithm for >encrypting filenames? I would like for the alogorithm to do compression >also. CFS uses an algorithm that lengthens the filename, thereby shortening >the maximum allowed length of the clear text filename. I want to avoid >this and possibly store extra metadata in the filename. What are you trying to accomplish by encrypting them? What's the environment you're planning to use them in? What's your threat model? Is it ok to always use the same key? (Thus, 3-DES is fine.) Do you need two-way encryption, or is a 1-way hash adequate? Thanks! Bill Bill Stewart, [EMAIL PROTECTED] PGP Fingerprint D454 E202 CBC8 40BF 3C85 B884 0ABE 4639
- Re: ICSA certifies weak crypto as secure Arnold G. Reinhold
- Re: ICSA certifies weak crypto as secure Eric Murray
- Re: ICSA certifies weak crypto as secure David Jablon
- Re: ICSA certifies weak crypto as secure John Kelsey
- Re: ICSA certifies weak crypto as secure John Gilmore
- Encrypting filenames Steve Hawkinson
- Re: Encrypting filenames Bill Stewart
- Re: Encrypting filenames Steve Hawkinson
- Re: Encrypting filenames Frank O'Dwyer
- Re: ICSA certifies weak crypto as secure Steven M. Bellovin
- Re: ICSA certifies weak crypto as secure Arnold G. Reinhold
- Salt (was: ICSA certifies weak crypto as s... Greg Rose
- Re: Salt (was: ICSA certifies weak cry... Arnold G. Reinhold
- Re: Salt (was: ICSA certifies wea... Bill Frantz
- Re: ICSA certifies weak crypto as secure Anonymous
- Re: ICSA certifies weak crypto as secure Arnold G. Reinhold
- Re: ICSA certifies weak crypto as secure John Kelsey