Is the cable system insecure?

Is the cable system insecure?

NewsGroups | Search | Tools
 comp.dcom.modems.cable  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Is the cable system insecure? Nonapeptide 10-03-2007
Posted by on October 9, 2007, 7:20 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
On Oct 4, 11:01 am, rodsm...@nessus.rodsbooks.com (Rod Smith) wrote:
> Nonapept...@gmail.com writes:
>
>
>
> > I just stumbled across a blurb in a networking book that said that the
> > infrastructure for cable internet access is slightly insecure. The
> > allegation was that since all cable drops in an area trace back to a
> > distribution node (which in turn make their way to the head end)
> > someone on the same distro node could, with some "technical
> > prowess" (direct quote from the source) could eavesdrop on your
> > communications. Is this true? I couldn't get Google to cough up any
> > further info on the subject, but then again I couldn't seem to piece
> > together completely relevant search terms.
>
> > This is perturbing news for someone who tends to be
> > paranoid. ::glances nervously at the cable modem:: Is it time to go
> > back to tin cans and string?
>
> There is some truth to the claim; however, most cable companies today
> encrypt the last-mile data, which would make it difficult (perhaps to the
> point of impossibility, except maybe for national intelligence agencies)
> for somebody on the same cable node to decrypt your data.
>
> That said, most Internet traffic is not encrypted, and there are lots and
> lots of places on the Internet that it can be intercepted. If you're just
> concerned about your nosy neighbor knowing that you've been reading all
> the latest Star Trek rumors, this isn't a big deal, since your nosy
> neighbor probably doesn't have ready access to all the routers between you
> and the Star Trek sites. OTOH, if you're concerned about Big Brother
> snooping on your activities, that's another matter. Likewise if you're
> concerned about shady characters acquiring a profile on you and using it
> against you (for identity theft, say). Data passed over the Internet is
> compromised every day. Often this is a matter of theft of credit card
> numbers, but these are typically stolen from retailers' computers, not
> while they're in transit. If criminals were to compromise a router,
> though, they could sift through the data it manages and grab some of yours
> -- passwords or other personal information, say. There have been
> allegations that the US government is doing this for data to and from
> foreign countries, the difference being that the feds are alleged to have
> the cooperation of the data carriers, or at least some of them, and of
> course they claim to be doing it in the interests of national security --
> or they would if they admitted they were doing it.
>
> The bottom line is this: Whether you're using a cable modem, DSL, a T1
> line, a dial-up telephone modem connection, or anything else, you
> shouldn't consider your Internet transactions secure. If you pass anything
> sensitive over the Internet, you should ensure that you're using an
> encrypting protocol to do it. Fortunately, most Web retailers employ
> encryption on their order pages, or at least on the ones that ask for
> credit card numbers -- but as noted, data thieves manage to steal CC
> numbers from the retailers' servers. (Local CC transactions are also at
> risk in the same way or by waiters or whatnot copying the information by
> hand, so don't swear off Internet purchases for this reason.) If you
> routinely log into remote systems (getting a command prompt or desktop to
> use it as if it were local), use an encrypting protocol such as SSH. For
> sensitive sites, such as a bank, use a unique password, and don't store it
> on your computer. (With all the Trojans and viruses out there, passwords
> stored by your browser might not be secure even on your own computer.)
> Particularly if you're using Windows, run anti-virus software, and keep it
> updated. Use a NAT router, if your cable modem doesn't incorporate that
> functionality, to help protect your home system. These basic steps will
> minimize the risks, but security isn't an all-or-none thing. The only way
> to be 100% sure that your Internet data won't be snooped is to not use the
> Internet, and the only way to be 100% sure that your computer's data won't
> be compromised is to not use a computer. In today's world, neither of
> these is a practical approach, so you'll have to accept some degree of
> risk.
>
> --
> Rod Smith, rodsm...@rodsbooks.comhttp://www.rodsbooks.com
> Author of books on Linux, FreeBSD, and networking

Thank yuo all for the responses. Much to think about.

@Rod

I suppose my initial confusion centered on this alleged ability of a
member of your shared last mile on the cable system to snoop on your
communication. To my limited understanding of networking, a snooper
would have to have some way of having direct access to that
multiplexer (or whatever the cable system uses) and then have some way
of replicating the traffic from the multiplexer back down the line to
himself. If a multiplexer (or whatever) is vulnerable, it would seem
to me that any medium, not just cable, is just as vulnerable. The book
I was reading stated that cable was more insecure by comparison to
other mediums but didn't offer any further explanation. Maybe I should
just calm down and go back to reading my Windows Administration
books... ;)


Nonapeptide


NMFall 20%
Posted by Bill M. on October 9, 2007, 11:31 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
On Tue, 09 Oct 2007 23:20:40 -0000, Nonapeptide@gmail.com wrote:

>Thank yuo all for the responses. Much to think about.
>
>@Rod
>
>I suppose my initial confusion centered on this alleged ability of a
>member of your shared last mile on the cable system to snoop on your
>communication. To my limited understanding of networking, a snooper
>would have to have some way of having direct access to that
>multiplexer (or whatever the cable system uses) and then have some way
>of replicating the traffic from the multiplexer back down the line to
>himself. If a multiplexer (or whatever) is vulnerable, it would seem
>to me that any medium, not just cable, is just as vulnerable. The book
>I was reading stated that cable was more insecure by comparison to
>other mediums but didn't offer any further explanation. Maybe I should
>just calm down and go back to reading my Windows Administration
>books... ;)

By any chance, is the copyright on the book about 7-10 years old?
IIRC, that's about how long it's been since a cable customer could
browse his neighbor's open shares and print to neighboring printers.

--
Bill

Posted by on October 10, 2007, 1:21 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
> On Tue, 09 Oct 2007 23:20:40 -0000, Nonapept...@gmail.com wrote:
> >Thank yuo all for the responses. Much to think about.
>
> >@Rod
>
> >I suppose my initial confusion centered on this alleged ability of a
> >member of your shared last mile on the cable system to snoop on your
> >communication. To my limited understanding of networking, a snooper
> >would have to have some way of having direct access to that
> >multiplexer (or whatever the cable system uses) and then have some way
> >of replicating the traffic from the multiplexer back down the line to
> >himself. If a multiplexer (or whatever) is vulnerable, it would seem
> >to me that any medium, not just cable, is just as vulnerable. The book
> >I was reading stated that cable was more insecure by comparison to
> >other mediums but didn't offer any further explanation. Maybe I should
> >just calm down and go back to reading my Windows Administration
> >books... ;)
>
> By any chance, is the copyright on the book about 7-10 years old?
> IIRC, that's about how long it's been since a cable customer could
> browse his neighbor's open shares and print to neighboring printers.
>
> --
> Bill- Hide quoted text -
>
> - Show quoted text -

Okay, if you all /must/ know, here it is:
http://www.amazon.com/gp/product/1592007929/ref=s9_asin_title_1/102-8221281-5400930?pf_rd_m=ATVPDKIKX0DER&pf_rd_s=center-1&pf_rd_r=19SHBA73JHMW2TAGT55J&pf_rd_t=101&pf_rd_p=278240701&pf_rd_i=507846

Nonapeptide


Posted by on October 11, 2007, 3:49 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
>
> (Upstream data also goes over the same shared set of cables and
> so is vulnerable, too.)

It's worth noting, however, that cable modems transmit in an entirely
different range of frequencies than they receive. So, while it is
theoretically possible to hack a cable modem to receive data being sent
*to* other modems on the cable segment, it is physically impossible for
it to receive data being sent *from* those other modems.

-Larry Jones

You can never really enjoy Sundays because in the back of your
mind you know you have to go to school the next day. -- Calvin

Posted by Tom Stiller on October 11, 2007, 6:27 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
wrote:

> >
> > (Upstream data also goes over the same shared set of cables and
> > so is vulnerable, too.)
>
> It's worth noting, however, that cable modems transmit in an entirely
> different range of frequencies than they receive. So, while it is
> theoretically possible to hack a cable modem to receive data being sent
> *to* other modems on the cable segment, it is physically impossible for
> it to receive data being sent *from* those other modems.
>
No one said one had to use the same tuner to capture data going both
directions.

You can tune one device to (e.g.) 34.8 MHz to capture the upstream
traffic and to (e.g.) 723 MHz to capture the downstream traffic.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF

Similar ThreadsPosted
NT kernel & System March 14, 2007, 9:00 pm
Re: NT kernel & System March 14, 2007, 9:00 pm
BroadbandEdge 2000 System (Terayon) CMTS March 6, 2006, 6:24 pm
Support Now Live Chat Support System June 30, 2007, 7:04 pm
Cable modem not working with TV cable plugged in November 2, 2006, 1:34 am
cable Internet cable October 23, 2006, 6:24 am
DSL or Cable October 18, 2005, 4:51 pm
Do I need a new cable modem? February 15, 2005, 12:00 pm
what cable modem to ge March 30, 2005, 7:15 am
Rca cable question August 4, 2005, 4:52 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map