Thread: Wireless at Osh
View Single Post
  #27  
Old June 26th 06, 06:35 AM posted to rec.aviation.piloting
external usenet poster
 
Posts: n/a
Default Wireless at Osh

"Brian O" wrote in message
...
What is SSH?


A simplistic description would be that it's telnet with security.

I guess Im right about the https being encrypted.


By definition, https is encrypted. But then, I didn't see you make any
statement like "https is encrypted". How are you right?

I doubt you
would have any problems as long as you are using web stuff.


It just depends. Many users don't have a clue whether they are using an
encrypted link or not (http vs https). Any web site dealing in sensitive
information *should* be using https, but the user should confirm that and
I'll bet the majority don't even know *how* to confirm it, never mind do
they do so.

Also, not all POP, SMTP, or NNTP servers require encrypted passwords and
many users may not be using encrypted passwords. Heck, as far as I can
recall, the DUAT web sites don't use https.

As far as your original statement that "They are just as encrypted as they
would be over a landline or dsl connection", I suppose that's true depending
on your definition of "encrypted". Technically, with respect to the actual
data being transmitted over the Internet, you're right. But the very nature
of a wireless network makes it less secure. It is relatively safer to
transmit unencrypted data over a hard-wired network connection than it is to
do so over a wireless connection, because it's more difficult to extract the
data being sent over a hard-wired network connection than it is to do so
over a wireless connection (especially a public one that is likely not using
any encryption such as WEP or WPA).

Of course, that said, I think it's a good idea for anyone to treat *any*
public or quasi-public network connection as unsecured and equivalent to
wireless whether wireless or not. Not that one's home DSL connection is
guaranteed to be secure either, but the likelihood of someone intercepting a
private line like that is fairly remote, especially compared to the
likelihood of a public service provided by a third party being compromised.

And of course, *that* said, there's probably not much reason for a user to
not be avoiding plain-text passwords and sensitive data regardless of their
network connection. So the advice to not use such things on a wireless
network is perfectly valid, but probably ought to be applied across the
board and not just while at OSH.

Pete