|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Sat, 22 Jan 94 18:25:27 CST To: com-priv@psi.com From: walkerl@med.ge.com (Larry Walker) > Marc Horowitz <marc@MIT.EDU> writes: > 2. Modular connectors at actual Pay Phones. >The newest line of AT&T pay phones, the Public Phone 2000, has a >modular jack. The only place I've ever seen these is in airports, so >you wouldn't find one on the street, but hopefully, if they get used, >this will change. Yes, I struggled with one of those in the Detroit airpaort last week. It screwed up my PPP dialing script, which goes into an 800 number, then pauses and transfers to an extension that's on the Portmaster. The Public Phone 2000 seemed to snarf my 800-NXX-XXXX number, then replay it. When the ACD answered and my dialing script did the *8-transfer, the modem was cut off, and the transfer failed. A fairly annoying trait for a public dataphone, IMHO. >>> Now this is an idea I've also toyed with since wandering the streets of >>> Amsterdam last year looking for a phone connection. > >Stop thinking analog. Consider a hypothetical ISDN payphone. You >plug your laptop in (what media? I'm not sure. UTP ethernet maybe?), >set up a packet connection directly from the phone to your favorite >ISDN/Internet gateway, and run IP over that packet link. This would >require some clever engineering, and some even cleverer software if >this is to be user-transparent, but all the protocols you need already >exist. It would just require the telco to support ISDN from the >street corner. I've read of/seen pictures of exactly this in Japan. But a simple plainly-wired RJ11 in public places lets lots of only-slightly-techie people get good PPP connectivity. >>> Do you really want your desktop PC sitting "unprotected" on the Internet >>> while you are traveling with a notebook PC that needs to get files from >>> home? > >When I travel, I carry a laptop with SLIP/PPP, Kerberized versions of >rlogin and rcp, and an AFS client. Admittedly, this is not a simple >turnkey solution, requiring quite a bit of custom work on the client >and server end, but it alleviates my security concerns wherever I >happen to be. If people who were interested in being secure were to >make their desires known to their vendors, I'm sure packaged solutions >would start appearing. > > Marc I'm quickly coming to the same conclusion. Maybe not Kerberos per se, but some standardized public-key encryption/validation scheme. Once an encryted IP conversation is established (and a critical mass of public domain and commercial applications can use it), the problem is solved big time. Any lesser measures, such as firewalls and packet filters, seem half-hearted and jury-rigged to me. Larry Larry Walker System Architect email: walkerl@med.ge.com GE Medical Systems phone: 414.785.8262 P.O. Box 414 / NB-902 fax: 414.785.4331 Milwaukee, WI 53201 dialcomm: 8*322-8262
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |