| lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
From: lord_ph at comcast.net (bryce) Subject: Re: spoofing Can you share your answer, some of us don't know it. ;) thanks, bryce sir kaber wrote: >Nevermind, found my answer. > >-kaber >;http://vertexabuse.cjb.net > >----- Original Message ----- >From: "sir kaber" <kaber@...ansystems.com> >To: <full-disclosure@...ts.netsys.com> >Sent: Sunday, November 16, 2003 11:24 PM >Subject: spoofing > > > > >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>Hi. >>I was just wondering, but what kind of measures have the big cable >>companies taken to prevent ip spoofing ? It seems like a simple >>problem to solve on the local router side, just make sure all ip >>packet source address originated from within the local network and >>most spoofing methods should be fixed ? Or are most big cable >>companies allowing you to generate ip packets with bogus info? >> >> >>- -kaber >>;http://vertexabuse.cjb.net >> >> >> >>-----BEGIN PGP SIGNATURE----- >>Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com> >> >>iQA/AwUBP7h3qVIfUl3yRgwCEQJmJACeP+y3XzAxnJwKEMn3tGjal2+BS7IAoOGq >>8rNc4pThCOHxSoLatRbPaHYi >>=CkNT >>-----END PGP SIGNATURE----- >> >> >> > >_______________________________________________ >Full-Disclosure - We believe in it. >Charter: http://lists.netsys.com/full-disclosure-charter.html > > >
Powered by blists - more mailing lists