On Thursday 22 June 2006 23:14, Colin Davis wrote: > Wouldn't this be a case that we could use a KSK to get a "short name" > to map the e-mail address to? > The KSK could point to the longer SSK. > > This would allow you to e-mail the much more memorable dbkr at dbkr-machine > > > (Although I had doubts that KSKs are secure, in a prior thread it was > insisted that they are much more difficult to forge in the .7 > architecture. )
This might be an optional extra for the future, for people who aren't too worried about people hijacking their addresses. (It's possible to hijack a KSK even if it means inserting it into my data store by hand and manually changing my node's location to correspond to that KSK.) Fundamentally, we need something secure. > > -Colin > > > On Jun 22, 2006, at 2:23 PM, Dave Baker wrote: > > > Hi, > > > > So a Freemail address needs to express an SSK public key at which a > > 'mailsite' > > can be fetched containing all the data necessary to set up some > > communication. The problem is that Freenet keys are case sensitive, > > and email > > addresses aren't. My mail client mangles the address to lowercase, > > meaning > > you can't just put the SSK into the address. > > > > Can anyone think of a (ideally standard) way of encoding an SSK to > > case > > insensitive ASCII? I'm currently using Hex encoding, but that makes > > Freemail > > addresses like: > > > > dbkr at 667265656e65743a53534b40317574304a6b7a57614c6b672d556b4d44704a684 > > a5a65646332346672306445362d74394d7a7e43517e552c54475668325272505564614 > > c505a775858454d6f51737177376f4e36634964704c73794f61355974584e382c41514 > > 1424141452f.freemail > > > > Not great. > > > > I don't really want to write another encoding scheme. > > > > Dave
