[NTLUG:Discuss] Strange iptables problem on CentOS 4.4

[. Daniel]

Actually, if I recall correctly, the link between the cable modem and the 
source is encrypted.  So not only would someone need to have hardware to 
access the cable modem network, they'd have to get past the encryption 
links to get anything useful from it.  That said, I think the hardest part 
would be in getting the right kind of hardware...

...hrm... anyone know what kind of hardware one could acquire that might be 
available to the consumer?


>. Daniel wrote:
> > That's an interesting question.  I had seen something like that not too
> > long ago.  It too was CentOS 4.4 in fact.  I think when I saw the 
error, I
> > hadn't yes corrected a router configuration mistake I had made.  I was
> > attempting to forward all data for a given IP address to a specific 
machine
> > within the firewall.  What I failed to do was make the machines 
responses
> > MASQ through the same IP address.  Once I made the Masq correction, it
> > worked just fine.
> >
> > My first impression was that "hey, this must be the 'secure' part of 
ssh."
> > I still don't understand why ssh is better than telnet... other than 
the
> > plain text thing, but then again, who will be sniffing in average
> > situations?
>
>You would be surprised.  Think of the poor folks on cable (a giant
>neighborhood ethernet hub).... very easy to sniff out passwords
>and such.
>
>
>_______________________________________________
>http://www.ntlug.org/mailman/listinfo/discuss

_________________________________________________________________
人気タレントや俳優、アーティストなど著名人の「Live.jp」を一挙公開！ 
http://mylivestory.jp