[164104] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Security over SONET/SDH

daemon@ATHENA.MIT.EDU (Mike A)
Tue Jun 25 15:22:48 2013

Date: Tue, 25 Jun 2013 14:22:25 -0500
From: Mike A <mikea@mikea.ath.cx>
To: nanog list <nanog@nanog.org>
In-Reply-To: <CABidiTK=U7381e1s-hhV_b6G_PYrg7jmQZtOPJYDosUMRcp5zQ@mail.gmail.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Mon, Jun 24, 2013 at 11:19:52PM -0500, Philip Dorr wrote:
> On Mon, Jun 24, 2013 at 9:59 PM, Christopher Morrow
> <morrowc.lists@gmail.com> wrote:
> > it's fair to say, I think, that if you want to  say something on the
> > network it's best that you consider:
> >   1) is the communication something private between you and another party(s)
> >   2) is the communication going to be seen by other than you +
> > the-right-other-party(s)
> >
> > and probably assume 2 is always going to be the case... So, if 1) is
> > true then make some way to keep it private:
> >   ssl + checking certs 'properly' (where is dane?)
> >   gpg + good key material security
> >   private-key/shared-key - don't do this, everyone screws this up.
> 
> SSH + SSHFP + DNSSEC does public/private key pretty well

If one or another of the TLAs hasn't solved, say, the BIGNUM_factoring
problem. If they have, then elliptic curve crypto looks interesting. 

-- 
Mike Andrews, W5EGO
mikea@mikea.ath.cx
Tired old sysadmin 


home help back first fref pref prev next nref lref last post