Re: md5 checksum server
From: Mike Hoskins (mike@adept.org)
Date: 10/10/02
- Next message: Lyndon Nerenberg: "Re: md5 checksum server"
- Previous message: Mike Hoskins: "Re: md5 checksum server"
- In reply to: Lyndon Nerenberg: "Re: md5 checksum server"
- Next in thread: Lyndon Nerenberg: "Re: md5 checksum server"
- Reply: Lyndon Nerenberg: "Re: md5 checksum server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 9 Oct 2002 16:45:06 -0700 (PDT) From: Mike Hoskins <mike@adept.org> To: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
On Wed, 9 Oct 2002, Lyndon Nerenberg wrote:
> DNS isn't the right place for this.
You could make the same arguments about portsdb.org...
> 1) it requires DNSSEC to ensure the MD5 record data isn't forged
Easy enough.
> 2) DNS caching would hide updates for the duration of the TTL
> attached to the TXT record
Tuneable.
I didn't say this was ideal, but it's easy to setup does work in the wild
now for some datasets. Regardless, I'm not attached to any one
proposal... Feel free to make others. :)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
- Next message: Lyndon Nerenberg: "Re: md5 checksum server"
- Previous message: Mike Hoskins: "Re: md5 checksum server"
- In reply to: Lyndon Nerenberg: "Re: md5 checksum server"
- Next in thread: Lyndon Nerenberg: "Re: md5 checksum server"
- Reply: Lyndon Nerenberg: "Re: md5 checksum server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|