lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
From: frank at (Frank Knobbe)
Subject: defense against session hijacking

On Mon, 2003-11-17 at 16:44, Damian Gerow wrote:
> Thus spake David Maynor ( [17/11/03 17:30]:
> > This would break things like NATed machines and such.
> Could you explain how, please?

I think David was hinting at pooled NAT address. Image an internal
network that gets NATed to addresses a.b.c.d.5 until a.b.c.d.12. Kinda
like Gary's "ganged" proxies.

The debates over using IP addresses, ports, TTLs and other connection
based elements do come up from time to time. However, you are trying to
authenticate/verify the user on the other end, not networking equipment
in between. Logically you should check user elements (such as browser ID

Or wrap it in SSL, use hard to guess/brute session ID's and hope for the
best.... like the rest if us :)


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url :

Powered by blists - more mailing lists