=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Brian" =3D=3D Brian Kelly writes:

Jack Oh, and I get that you're not talking about setting up your own
Jack network in the encryption-free manner in which you describe.
Jack I'm just trying to show that there are many good ways to make
Jack wireless work such that you can be friendly to your neighbors
Jack while protecting your assets.

Brian I use a very simple all-platforms bulletproof "security
Brian protocol" Jack. I don't put anything of a sensitive nature on a
Brian hard drive in a computer which is networked, particulary when
Brian the network includes the Internet, *nothing*. Net result is
Brian that my sensitive info can't possibly get hacked and I don't
Brian have to diddle with any contorted encryption and firewall sorts
Brian of pushups. I could care less if this computer gets hacked,
Brian there's nothing in it which is of any pecuniary or
Brian "intelligence" value at all to anybody else. What do I care if
Brian somebody taps into my antenna modeling files, e-mail to N2EY or
Brian my .jpegs of family and such which are in this box?!

It is interesting that your primary concern is to keep your
information secure -- that is indeed a very valid concern. The
approach you describe is the one that was followed at the defense
contractor where I started my career. It works very well for many
many cases and is "the right way" to handle most kinds of classified
information. However, there is a concern which isn't addressed by
your system, which is being a good Internet citizen and preventing
your computer from being used for Evil. You could care less if the
machine gets hacked, but if it gets hacked and used as an open proxy
for delivering spam or as part of a distributed denial of service
attack, your negligence leads directly to the economic losses of
others. That's something worth considering.

Brian Of course in the process I'm giving up a lot of current-tech
Brian conveniences like online banking, online shopping and
Brian others. But that's OK where I come from, my telephone still
Brian works and I still dial around to place orders with the plastic,
Brian the banks are still issuing statements, the post office still
Brian sells stamps, yadda, yadda. I have yet to run into a
Brian transaction or an instance of passing out any other type of
Brian sensitive info which was stymied by doing it offline.

In some ways it's harder to do business offline these days, but just
as you can still use a pulse telephone without Touch-Tone, you can
still use the phone instead of the Internet.

Brian Depends on the tradeoffs you make between security and
Brian convenience, I've taken the easy way out of the whole endless
Brian computer security swamp.
=20
That is indeed one approach, and other than the blind spot I described
above, it's a perfectly reasonable and consistent approach. You can
still send all your Internet traffic over AX.25[1] and I can't, which
is also a plus for you. But I've got a versatile tool, a profitable
source of income, an engaging hobby, and a space heater all in one,
and that doesn't completely suck.

Jack Jack.

Brian w3rv

Jack (one of those paranoid computer security types)

Brian (ya done it to yerself Jack)

Of course, and I'm totally okay with it -- just issuing a disclaimer
to let folks know that my perspective, while reasonable and consistent
=2D From where I sit, may be completely insane from another's point of
view.=20

Jack.
[1] ObTopicalReference
=2D --=20
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBJOHqGPFSfAB/ezgRAliCAJ928F5+DAa1FYNE15xHITf36NJHdACg+mXR
kOD6x00BbZuDwOSvgkhaK4o=3D
=3D3vLr
=2D----END PGP SIGNATURE-----