public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: DSL and AT&T.  About time.
Date: Sun, 9 Aug 2009 10:29:26 +0100	[thread overview]
Message-ID: <200908091029.37534.michaelkintzios@gmail.com> (raw)
In-Reply-To: <h5j0e3$cft$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2028 bytes --]

On Saturday 08 August 2009, Grant Edwards wrote:
> On 2009-08-08, Nikos Chantziaras <realnc@arcor.de> wrote:
> > On 08/08/2009 05:29 AM, Dale wrote:
> >> I had thought about picking up a Linksys router and putting it
> >> between my desktop and the modem.
> >
> > Your modem is probably a router anyway.

+1

I don't think I have seen a proper adsl modem for years now.  99% of them are 
modem+router combos or half-bridged routers.

> Almost certainly (at least in the US).  DSL modems with
> Ethernet interfaces almost always are routers/firewalls (and
> have been since way back when).  It used to be common for Cable
> modems to be bridges, but that seems to be getting less
> common.

Yes, most cable so called modems are half-bridged routers.

> > Furthermore, right now you're accessing the internet without
> > any form of protection anyway.  If you're with dial-up, that
> > means you're connected directly to the internet.  And don't
> > forget this is Linux, not Windows.
> >
> > Even without a firewall, remote break-in is highly improbable,
> > especially since you're not running any Apache or MySQL
> > servers on your machine (at least I assume you don't.)
>
> That's what I thought back when I was using dialup on a Linux
> box that didn't have any servers running.  Then one day I got
> root-kitted.
>
> IMO, safely attaching a Linux machine directly to the Internet
> takes a fair bit of skill and lot of diligence.  Safely
> attaching a Windows machine directly to the Internet is at
> least an order of magnitude more difficult.

I think that both are exactly the same in terms of measures that need apply.  
A firewall and practicing safe-hex.

Of course the Linux machine has the added benefit that it should not be 
opening or listening on all sort of ports that you did not ask it to and as a 
rule in Linux you are not running a desktop and its applications logged in as 
root, but the basic premise of using a firewall is the same.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-08-09  9:29 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 23:45 [gentoo-user] DSL and AT&T. About time Dale
2009-08-08  0:12 ` [gentoo-user] " Nikos Chantziaras
2009-08-08  1:09   ` Dale
2009-08-08  1:29     ` Nikos Chantziaras
2009-08-08  1:18 ` [gentoo-user] " David
2009-08-08  2:03   ` [gentoo-user] " Grant Edwards
2009-08-08  2:14     ` David
2009-08-08  2:29     ` Dale
2009-08-08  3:02       ` Nikos Chantziaras
2009-08-08  3:19         ` Dale
2009-08-08  3:49           ` Nikos Chantziaras
2009-08-08  3:56             ` Dale
2009-08-08  4:54         ` Grant Edwards
2009-08-09  9:29           ` Mick [this message]
2009-08-08 13:12 ` [gentoo-user] " Michael Sullivan
2009-08-08 14:17   ` Dale
2009-08-08 14:44     ` [gentoo-user] " Nikos Chantziaras
2009-08-10  1:55 ` [gentoo-user] " Paul Hartman
2009-08-10  3:03   ` Dale

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200908091029.37534.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox