News for hackers. Stuff that matters.

mned

Re:Internet Draft: SMTP Strict Transport Security on Sunday March 20, 2016 @03:56AM (#11322191)
You have said you have been thinking of a DNSSEC2 proposal for a while, that your protocol differs in multiple ways and that it is easier to implement. Given this you should be able to concretely articulate how your protocol differs and where its advantages are gained. Thus far you have not shown the ability to do this.
Re:Internet Draft: SMTP Strict Transport Security on Sunday March 20, 2016 @02:45AM (#11322058)
Online signing and white lies are already in DNSSEC. What you've described so far doesn't seem to be different to the status quo. Even deprecation of older cryptographic signatures is being worked through at the moment.
Re:Internet Draft: SMTP Strict Transport Security on Sunday March 20, 2016 @01:10AM (#11321906)
> It is a selling point in that it simplifies the protocol, making it easier to implement.

In the current protocol the only difference between offline and online signing is in how authoritative servers are implemented. There the differences aren't all that significant (relative to building an authoritative server as a whole) -- the same data needs signing, etc -- so please explain how your protocol makes implementation simpler.

> Obviously it would not be the only difference.

Can you please expand on that? You've said you've been thinking of a DNSSEC2 proposal for a while so you must have more to say.

Re:Internet Draft: SMTP Strict Transport Security on Saturday March 19, 2016 @11:00PM (#11321599)
Having no support for offline signing in and of itself isn't a selling point. What else does your approach have to offer?