Re: Private Address Spaces
From: Hairy One Kenobi (abuse_at_[127.0.0.1)
Date: 12/03/03
- Next message: Jonathan de Boyne Pollard: "Re: Private Address Spaces"
- Previous message: Hairy One Kenobi: "Re: email spam"
- In reply to:(deleted message) mchiper: "Re: Private Address Spaces"
- Next in thread: Jonathan de Boyne Pollard: "Re: Private Address Spaces"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 3 Dec 2003 13:23:06 -0000
"mchiper" <notnuts@yahoo.com> wrote in message
news:sq8rsv4iiuqi53sn53if9io9pcb3j271ck@4ax.com...
> In alt.computer.security, Msg ID:
<YPwwb.6673$4Y6.5171@newsfep4-winn.server.ntli.net>
> "Hairy One Kenobi" <abuse@[127.0.0.1]>, wrote:
>
> >"mchiper" <notnuts@yahoo.com> wrote in message
> >news:4tg4svoaoitffcp5u1piatsfdsi47pu9th@4ax.com...
> >>
> >> In alt.computer.security, Msg ID:
> ><Agrwb.2791$qn4.21696@newsfep4-glfd.server.ntli.net>
> >> "Hairy One Kenobi" <abuse@[127.0.0.1]>, wrote:
> >> >You haven't actually stated a problem, just sprayed a response over a
> >number
> >> >of more-or-less innocent newsfroups.
> >> >
> >> >If you're stating that you "own" a particular IP assigned by your ISP,
> >then
> >> >scoot along to your local Registry (I'm guessing that you're US-based,
so
> >> >that would be ARIN). They should be able to set you straight on the
> >> >difference between ownership and allocation.
> >>
> >> What I am stating is.
> >> If you are stating that my privacy is my problem.
> >> The I will state that your safety is your problem.
> >> Buy your self a mine detector, before you venture outside your home.
> >
> >?
> >
> >Did you, perchance, pass your posting through
> >
> >http://www.tashian.com/multibabel/
> >
> >and is an English translation available?
> >
> >Oh, and I see that you snipped all relevant points - misunderstanding, or
a
> >pure troll..?
> No.. It's not a troll.
> It's a simple point, and I am replying to a message that was
> posted in alt.computer.security, and cross posted to others.
>
> I can't understand how it's possible to talk about security,
> without this simple matter being perfectly understood by all parties.
>
> I can't quite get the difference between Address spaces, private address
spaces,
> VPN and access to WANs provided by ISPs..
> My ISP provides access to their servers, as well as the Internet...
> But, I can comprehend reserved addresses, which may be private,
> or used for other purposes.. But public, escapes me...
OK. A couple of definitions (undoubtedly with holes in, but should suffice
for the conversation)
Private = a resource (e.g. a network, network address, or even telephone)
that can only be used by its controller
Public = everything else (e.g. a web site on the internet [as opposed to a
file & print server in the bowels of the Accounting department], an Internet
address that can be reached from outside of the organization [e.g. that web
site, or perhaps a helpdesk], or a telephone kiosk)
Virtual = acts like something else, but isn't really "there".
These can be combined.. e.g. VPN = a private network that really isn't.
Basically, you take a publicly accessible network, and use some gimcrackery
to make it look like a private network. Think of it as a leased-line without
the need to actually install a physical bit of wire.
Now, let's take another look at those public addresses. Now, in theory I
could just set up a server, call myself 1.2.3.4 and everyone'd be able to
connect, right?
Wrong.
They'd need to know where I was, in order to direct requests to me. Which is
where ICANN comes in - basically to make sure that the same address(es)
can't get registered to different people, and that everyone one knows where
to send requests to. There's a whole hierarchy here, so let's just leave it
at that ;o)
Just think of it as making sure that two people don't end up with the same
phone number.
Because lots of people have networks, they've also set across a few blocks
that are designated as Private - i.e. are only for use inside corporations,
and shall not be accessible from outside. Taking the phone analogy once
more, thing of this as a PBX - if you dial 123 to talk to Bill, there's no
guarantee that, if you move to a different company/PBX, dialling 123 will
get you through to the same person.
> Basically, I want to know why my ISP needs to include my IP address
> in messages I post on their server..
> While when I purchase access to another server, they do not include my
> IP address in the header of messages I post on their server.
> My connection, in both casses is thru at least some portion of the network
> controlled by my ISP...
Ah. And now, I think, we have the /real/ question.
Messages posted in (e.g.) Usenet use a particular protocol that sits way,
way above IP. So do email servers.
A few years back, we started getting the phenomenon of spam - unwanted
messages. This quickly moved from Usenet (where the term originated) to
email. Adding a header with the original poster's address was a way to
combat that, but allowing spammers to be traced.
These headers might not be mandatory, but they are recommended. If you can
find someone willing to ignore the recommendation, then you can use their
machines to post with. If they charge (and most probably will), then first
make sure that they've not been blacklisted for spamming.
> For example, the speed with which I am able to send, and receive data
> to the other news server, is limited by the speed limits imposed by my
ISP.
>
> Everything I've read says that IP addresses are used to communicate
between
> a router, and
<the rest appears to have been lost..?>
IPs are like that phone number - if your ISP receives a complaint, then they
can consult their "secret" phonebook to tell you off. If you're /really/
unlucky, then someone else might be able to guess your town. If they get
anything closer, then you've "leaked" the information elsewhere.
HTH
H1K
- Next message: Jonathan de Boyne Pollard: "Re: Private Address Spaces"
- Previous message: Hairy One Kenobi: "Re: email spam"
- In reply to:(deleted message) mchiper: "Re: Private Address Spaces"
- Next in thread: Jonathan de Boyne Pollard: "Re: Private Address Spaces"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
