Computer Learning Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Bill Fischofer who wrote (24338)	1/5/2002 12:10:43 PM
From: Stang	Read Replies (1) of 110653

Bill: Thanks for the info. Security seems to be the weakest link. The Extremtech article has very good tips on securing Wireless networks. Good tips with the Mac address and static ip's configuration. I will research 802.xx solutions and report back here when/if I deploy my Home wireless lan. On the security issues. (Disclaimer, I'm far away here from my domain of expertise) SSL (https) is widely used on the Web to transmit/receive: - sensitive information like credit cards - some folks use SSL for login and passwords (Instead of sending them in plain text) - some folks even use SSL to send and receive files via https I know that Organizations need to obtain a certificate from folks like Verisign to SSL enable their servers. Here's what I'm getting at: Would it not make sense for Wireless vendor's or 802.xx developpers to SSL enable their transmitters and receivers? Certificates would not be required for private lans. As far as I know SSL is not owned by anyone. Heck all major browsers support SSL out of the box. I guess somehow enabling SSL for tcp/ip instead of http. Stang in Dreamland

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next