Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: SPF: SRS

Sender Rewriting Scheme and open relays.

 

 

SPF srs RSS feed   Index | Next | Previous | View Threaded


dwmw2 at infradead

Feb 25, 2004, 6:29 AM

Post #1 of 3 (2021 views)
Permalink
Sender Rewriting Scheme and open relays.

On Mon, 2004-02-23 at 17:23 -0600, Seth Goodman wrote:
> Here is a revised approach for fixing the open-relay problem that has
> been pointed out,

I think you may have hit on a better answer in another forum, where you
suggested private/public key encryption could be used to generate
one-time addresses.

If an SRS0+... address contains a hash which is signed by a private key,
and the corresponding public key is in the DNS, then a third party can
_easily_ verify that it's a real SRS0+ address from a domain which is
really doing SRS, and not an attempted attack.

If you mandate that SRS1+... addresses should only be rewritten back to
SRS0+... addresses if the hash is verified against the pubkey in DNS,
you've basically fixed the relaying problem, haven't you?

--
dwmw2

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss [at] v2


daniel at roe

Feb 25, 2004, 6:50 AM

Post #2 of 3 (1902 views)
Permalink
Re: Sender Rewriting Scheme and open relays. [In reply to]

David Woodhouse <dwmw2 [at] infradead> [2004-02-25/13:29]:
> If an SRS0+... address contains a hash which is signed by a private
> key, and the corresponding public key is in the DNS, then a third
> party can _easily_ verify that it's a real SRS0+ address from a domain
> which is really doing SRS, and not an attempted attack.

There might be some potential practical problems with this approach.

First, a signature is significantly larger than a hash (HMAC), and I see
no way you could shorten the signatures the way you can HMACs. It'll be
difficult to get a rewritten address with signature to fit into a 64
chars case insignificant local part.

Second, public key crypto is rather expensive in terms of CPU cycles.

Cheers,
Dan

--
Daniel Roethlisberger <daniel [at] roe>
GnuPG key ID 0x804A06B1 (DSA/ElGamal)

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss [at] v2


dwmw2 at infradead

Feb 25, 2004, 6:56 AM

Post #3 of 3 (1913 views)
Permalink
Re: Sender Rewriting Scheme and open relays. [In reply to]

On Wed, 2004-02-25 at 14:50 +0100, Daniel Roethlisberger wrote:
> David Woodhouse <dwmw2 [at] infradead> [2004-02-25/13:29]:
> > If an SRS0+... address contains a hash which is signed by a private
> > key, and the corresponding public key is in the DNS, then a third
> > party can _easily_ verify that it's a real SRS0+ address from a domain
> > which is really doing SRS, and not an attempted attack.
>
> There might be some potential practical problems with this approach.
>
> First, a signature is significantly larger than a hash (HMAC), and I see
> no way you could shorten the signatures the way you can HMACs. It'll be
> difficult to get a rewritten address with signature to fit into a 64
> chars case insignificant local part.
>
> Second, public key crypto is rather expensive in terms of CPU cycles.

Both true. Such a scheme allows brute force attacks too, without any
need for an oracle.

--
dwmw2

-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=srs-discuss [at] v2

SPF srs RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.