1996-12-07 - Re: “Family Channel” of the Internet?

Header Data

From: “Mark M.” <markm@voicenet.com>
To: Cypherpunks <kkirksey@appstate.campus.mci.net>
Message Hash: 23ddbca2344a6fabdef6a46dd287a37660a2135eedd04d47d697dc1800f14e0f
Message ID: <Pine.LNX.3.95.961206195302.1431B-100000@gak.voicenet.com>
Reply To: <199612062239.RAA26100@aus-c.mp.campus.mci.net>
UTC Datetime: 1996-12-07 01:00:37 UTC
Raw Date: Fri, 6 Dec 1996 17:00:37 -0800 (PST)

Raw message

From: "Mark M." <markm@voicenet.com>
Date: Fri, 6 Dec 1996 17:00:37 -0800 (PST)
To: Cypherpunks <kkirksey@appstate.campus.mci.net>
Subject: Re: "Family Channel" of the Internet?
In-Reply-To: <199612062239.RAA26100@aus-c.mp.campus.mci.net>
Message-ID: <Pine.LNX.3.95.961206195302.1431B-100000@gak.voicenet.com>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

On Fri, 6 Dec 1996, Ken Kirksey wrote:

> 1) Is it technically possible for them to limit access to only approved 
> IP addresses?  If so, how can they do this, and is it possible to get 
> around these measures.

Packet filters can do this.  This could be thwarted by using a proxy
located on a trusted host.  There are more complicated ways (source routing,
IP spoofing, etc.) but these would require the cooperation of the target host.
Very improbable.

> 3) In general, how would you use crypto to ensure that your users only 
> connected to approved sites, regardless of the platform or browser 
> software they were using?

Crypto would probably only be used for authentication.  A simple password
system would work, but wouldn't be as secure, of course.  The ISP could
pass the packets through the appropriate filter rules depending on the user.
I don't know how much overhead would be associated with this technique, but
it seems to be the most secure way to do this.
 
> 
> I asked the guy to send me some technical details.  If I receive them, 
> I'll share unless he makes me sign an NDA.
> 
> Ken
> 

Mark
- -- 
finger -l for PGP key
PGP encrypted mail prefered.
0xf9b22ba5 now revoked

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQEVAwUBMqjCVSzIPc7jvyFpAQE7egf+OMTzXyu/zzEg1+KE1v1/LgoyKXFc6QSr
7X5cqhyyX7kDzjUC+g/yklu9AQK1PRpM8SsYTP5uSSEWW/joBjMmUaVPdlnTctgD
Osa8rE2EPL1QkojK3thEaSn5OrxAzmEvTYnhJH53c2WIPFpsGm1Ipi9SHaMGQtgY
xFFR03gRSN1TeiULYzQHWXdovKFWFFNtYNgGTHd1et/TJvr67E30zRjOMIP0fD21
GN6fOPMsbbdtEwQsohrUkdsR+kMcOJDtYvBP/eJm4WCiie8SrEhCBSS7SKmkaWzX
zzc/UOIX3/LY9t5dt52fO4T8vNfoSsc4plc5wIsDkJbdbBwc9RlCsw==
=tFgY
-----END PGP SIGNATURE-----






Thread