There is XML digital signature support in.NET. Since it was released prior to the W3C recommendation it may not be fully compliant but it looks similar. Hopefully now they will update their implementation (what were they supposed to do, delay.NET until W3C got around to publishing the recommendation?).
What if someone using this keygen generates my key that has already been activated? It will look to Microsoft like the key-in-question is being installed on a different computer with different hardware. Then the next time I go to re-install XP my legitimate key won't work.
About two months ago I was at Denver International Airport and I decided to plug in my Wi-Fi card (SSID: "Denver Int'l Airport", no WEP). I was able to get an IP address from their DHCP server but any attempt to access the web redirected me to a generic username/password entry screen.
I figured they were going to offer a for-pay service to business travelers. It's alarming that they would be using this for actual airport services!
The e-mail from AT&T points you to http://newuser.attbi.com. That page doesn't exist yet but will be activated "if necessary." But if you want to see it now this page looks like a test-run of what's to come. It includes a FAQ and a new Subscriber Agreement too.
This does not mean that the networks are compromised. One way to set this up would be to leave the 802.11b interface wide open (thus making it easier for laptop-users to roam onto the network), but to place the wireless access point outside the firewall. Legitimate users VPN into the network (with VPN encryption of course). The exposure is no worse than any other point at which a private network is exposed to the public internet through a firewall.
One problem is that "anyone" can set up a wireless access point for their personal use -- without realizing that they are exposing their company's LAN (Apple Airport anyone). A contributing factor is a false sense of security because most notebook 802.11b cards have a far shorter range than the access point broadcasts. Your notebook may not be able to pick up the signal outside the office but someone with an external antenna can pick it up at much greater range.
Slashdot Mirror
There is XML digital signature support in .NET. Since it was released prior to the W3C recommendation it may not be fully compliant but it looks similar. Hopefully now they will update their implementation (what were they supposed to do, delay .NET until W3C got around to publishing the recommendation?).
See this page for more info and sample code.
What if someone using this keygen generates my key that has already been activated? It will look to Microsoft like the key-in-question is being installed on a different computer with different hardware. Then the next time I go to re-install XP my legitimate key won't work.
About two months ago I was at Denver International Airport and I decided to plug in my Wi-Fi card (SSID: "Denver Int'l Airport", no WEP). I was able to get an IP address from their DHCP server but any attempt to access the web redirected me to a generic username/password entry screen.
I figured they were going to offer a for-pay service to business travelers. It's alarming that they would be using this for actual airport services!
The banknotes were designed by Austrian artist Robert Kalina.
Besides, Switzerland isn't even part of the EU.
Does that iMac have... breasts?
The e-mail from AT&T points you to http://newuser.attbi.com. That page doesn't exist yet but will be activated "if necessary." But if you want to see it now this page looks like a test-run of what's to come. It includes a FAQ and a new Subscriber Agreement too.
Since 802.11b uses a flawed encryption scheme there is no way to make the over-the-air protocol truy secure.
This does not mean that the networks are compromised. One way to set this up would be to leave the 802.11b interface wide open (thus making it easier for laptop-users to roam onto the network), but to place the wireless access point outside the firewall. Legitimate users VPN into the network (with VPN encryption of course). The exposure is no worse than any other point at which a private network is exposed to the public internet through a firewall.
One problem is that "anyone" can set up a wireless access point for their personal use -- without realizing that they are exposing their company's LAN (Apple Airport anyone). A contributing factor is a false sense of security because most notebook 802.11b cards have a far shorter range than the access point broadcasts. Your notebook may not be able to pick up the signal outside the office but someone with an external antenna can pick it up at much greater range.