From: Christopher Fowler <cfowler@outpostsentinel.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Blowfish encryption
Date: Thu, 10 Mar 2005 19:10:33 +0000 [thread overview]
Message-ID: <1110481833.18073.447.camel@linux.linxdev.com> (raw)
In-Reply-To: <1110403872.18073.330.camel@linux.linxdev.com>
I think the thing I'll want to use is ECP. Does pppd come with it?
On Thu, 2005-03-10 at 14:00, James Carlson wrote:
> Christopher Fowler writes:
> > Some of these tin-hat people I tell them to simply buy encrypted modems
> > that do the encryption between the. Are there anyone out there selling
> > good ones anymore?
>
> Dunno. Google seems to think so:
>
> http://www.securtelecom.com/Products/Corporate/EncryptionSolutions/encryptionsolutions.htm
>
> > Th issue is that there are two boxes connected via a modem and using PPP
> > for IP traffic. The customer wants to be sure all traffic across that
> > phone line is encrypted.
>
> That's just baffling. So, they are concerned that someone will tap
> the telephone line and manage to decode a V.90 data stream, but
> they're unconcerned whether the next hop itself (the modem at the
> other end) is itself "secure," or that hazards may exist between that
> modem and the ultimate packet destination, which may be many hops
> away.
>
> How does that work?
>
> That's why I was asking about the threat model. It doesn't sound
> rational. In the particular case of irrational requests, it tends to
> be difficult to design sufficient technical solutions. :-/
>
> > Since they use so many network product some
> > old those protocol may be plain-text. By having ppp encrypt what it
> > sends that would cover any data that travels across.
>
> Again, ECP and IPsec are likely the best ways to deal with this,
> though they solve very different problems.
>
> ECP solves the PPP link encryption problem. It does *not* help with
> any traffic once it's forwarded past that single link. It's therefore
> of very limited utility in providing real security.
>
> IPsec solves the end-to-end problem. It does *not* help if the peer
> you're talking to is compromised, but, then, likely nothing other than
> scissors will.
>
> http://www.physics.usyd.edu.au/~matthewa/scissors.pdf
next prev parent reply other threads:[~2005-03-10 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 21:31 Blowfish encryption Christopher Fowler
2005-03-10 12:36 ` James Carlson
2005-03-10 17:53 ` Bill Unruh
2005-03-10 18:01 ` Christopher Fowler
2005-03-10 18:17 ` James Carlson
2005-03-10 18:24 ` Christopher Fowler
2005-03-10 19:00 ` James Carlson
2005-03-10 19:10 ` Christopher Fowler [this message]
2005-03-10 19:13 ` James Carlson
2005-03-10 19:13 ` Bill Unruh
2005-03-10 19:17 ` Bill Unruh
2005-03-10 19:43 ` John Hasler
2005-03-10 19:59 ` James Carlson
2005-03-10 20:06 ` Christopher Fowler
2005-03-11 10:50 ` Bill Unruh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1110481833.18073.447.camel@linux.linxdev.com \
--to=cfowler@outpostsentinel.com \
--cc=linux-ppp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.