Virginia Tech Wifi: Difference between revisions

imported>Waldrep
Waldrep (talk | contribs)
m Undo revision 7818 by Waldrep (talk)
Tag: Undo
 
(32 intermediate revisions by 6 users not shown)
Line 1: Line 1:
<!--There are three wireless networks on campus.  One network, called VT-Wireless, encrypts all traffic and is secured with [[EAP-TLS]] or PEAP-MSCHAPv2. A second network, CONNECTtoVT-Wireless, is an unencrypted, captive portal wireless network designed to set up connecting to VT-Wireless without offering Internet access. Due to user issues faced during deployment, CONNECTtoVT-Wireless began offering captive portal access to VT users.
On campus, there are 2 wireless networks:
-->
* '''eduroam''': uses federated credentials and is the preferred method.
On campus, there are 2 wireless networks. '''Eduroam''' is the preferred method, which uses PEAP-MSCHAPv2 to authenticate to the RADIUS server, while the second SSID, '''VirginiaTech''', provides a captive-portal
* '''VirginiaTech''': for guests and devices that cannot use the authentication method of '''eduroam'''.
and allows for guest account creation.
Any remotely modern/complete Linux or Unix system will be able to connect to eduroam without any issues.


As of January 2015 the [https://www.computing.vt.edu/content/eduroam preferred method] of wireless access at Virginia Tech is through the [https://eduroam.org/ Eduroam] network. Eduroam is a secure wireless access service that was developed for the use of research and educational institutions. One of the advantages of the Eduroam network over the VT-Wireless network is that you will be able to connect to the Internet at any participating institution using your Virginia Tech credentials. The Eduroam-US site provides a [https://www.eduroam.us/technical_overview technical overview] of how the network authenticates you to the Virginia Tech RADIUS servers.
Because '''eduroam''''s credentials are federated, it means that a VT user is able to automatically connect to the Internet at participating institutions. The eduroam-US site provides a [https://www.eduroam.us/technical_overview technical overview] of the authentication system.


==General Connection Information==
==General Connection Information==
===eduroam===
===eduroam===
The following settings are recommended for connecting to the Eduroam network:
The following settings are recommended for connecting to the eduroam network:


* '''SSID:''' eduroam
* '''SSID:''' eduroam
* '''EAP:''' PEAP
* '''EAP:''' PEAP
* '''Phase 2:''' MSCHAPv2
* '''Phase 2:''' MSCHAPv2
* '''Root CA:''' [https://2029.globalsign.com GlobalSign Root CA - R3] or pin the certificate (see below)
* '''Root CA:''' "USERTrust RSA Certification Authority" or pin the certificate (see below)
* '''Server Name:''' eduroam.nis.vt.edu
* '''Server Name:''' eduroam.nis.vt.edu
* '''Identity:''' pid@vt.edu (So if your PID was "hokiebird", hokiebird@vt.edu)
* '''Identity:''' pid@vt.edu (So if your PID was "hokiebird", hokiebird@vt.edu)
Line 25: Line 25:
The certificate presented by the RADIUS server is chained as such:
The certificate presented by the RADIUS server is chained as such:


* GlobalSign Root CA - R3
* USERTrust RSA Certification Authority
** Trusted Root CA SHA256 G2
** InCommon RSA Server CA  
*** Virginia Tech Global Qualified Server CA
*** eduroam.nis.vt.edu
**** eduroam.nis.vt.edu


Below is where to obtain each of these, along with some metadata. The filenames are arbitrary, but will be used for the rest of this article. For every certificate (''especially'' the root, the signature chain helps with the rest), consider where you are obtaining it from and how much trust that you are getting what you think you are. You will probably want the PEM formatted certificate, if you have the option.
Below is where to obtain each of these, along with some metadata. The filenames are arbitrary, but will be used for the rest of this article. For every certificate (''especially'' the root, the signature chain helps with the rest), consider where you are obtaining it from and how much trust that you are getting what you think you are. You will probably want the PEM formatted certificate, if you have the option.


====GlobalSign Root CA - R3====
====USERTrust RSA Certification Authority====


''Filename:'' GlobalSign_Root_CA_-_R3.pem
''Filename:'' USERTrust_RSA_Certification_Authority.pem


''Subject:'' OU = GlobalSign Root CA - R3, O = GlobalSign, CN = GlobalSign
''Subject:'' C = US, ST = New Jersey, L = Jersey City, O = The USERTRUST Network, CN = USERTrust RSA Certification Authority


This is a common root CA and should have shipped with your OS. It is likely located in <code>/etc/ssl/certs/GlobalSign_Root_CA_-_R3.pem</code>. If you are unable to locate it in your OS, you can get it directly from [https://2029.globalsign.com/ GlobalSign].
This is a common root CA and should have shipped with your OS. It is likely located in <code>/etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem</code>. Note that if you follow the Authority Information Access of the intermediate certificate, it may direct you to a URL which points to a different version of this certficate, which is cross signed by AddTrust and expired in May 2020. The one in your cert store is self-signed and expires in 2038. You want the one from your cert store.


====Trusted Root CA SHA256 G2====
====InCommon RSA Server CA====


''Filename:'' TrustedRootCASHA256G2.pem
''Filename:'' InCommonRSAServerCA_2.pem


''Subject:'' C = BE, OU = Trusted Root, O = GlobalSign nv-sa, CN = Trusted Root CA SHA256 G2
''Subject:'' C = US, ST = MI, L = Ann Arbor, O = Internet2, OU = InCommon, CN = InCommon RSA Server CA


This is an intermediate certificate, again issued by GlobalSign. You can get it directly from GlobalSign [https://support.globalsign.com/customer/portal/articles/1211591-trusted-root-intermediate-certificates here].
This is an intermediate certificate issued to InCommon. You can get it directly from InCommon [http://crt.usertrust.com/InCommonRSAServerCA_2.crt here].
 
====Virginia Tech Global Qualified Server CA====
 
''Filename:'' VirginiaTechGlobalQualifiedServerCA.pem
 
''Subject:'' C = US, ST = Virginia, L = Blacksburg, OU = Global Qualified Server CA, O = Virginia Polytechnic Institute and State University, CN = Virginia Tech Global Qualified Server CA
 
This can be obtained from the Virginia Tech PKI [http://www.pki.vt.edu/developer/rootca.html#globalqualifiedserver website]. This website is only available from VT IP addresses (including VPN). Although certificates higher in the chain are also provided here, the page does ''not'' support https. '''''DO NOT''''' get your root CA here.


====eduroam.nis.vt.edu====
====eduroam.nis.vt.edu====


''Filename:'' eduroam.nis.vt.edu.crt
''Filename:'' eduroam.nis.vt.edu.pem


''Subject:'' C = US, ST = Virginia, L = Blacksburg, O = Virginia Polytechnic Institute and State University, CN = eduroam.nis.vt.edu
''Subject:'' C = US, postalCode = 24061, ST = Virginia, L = Blacksburg, street = 800 Washington St. SW, O = Virginia Polytechnic Institute and State University, OU = Secure Identity Services, CN = eduroam.nis.vt.edu


This can be obtained from the [https://apps.pki.vt.edu/ca-manager/search VTCA Certificate Manager]. This requires PID login. Search for "eduroam.nis.vt.edu". '''Note''': As of 2017 June 19, there will be 2 results, due to some internal testing. Download the certificate with the serial 3699307517ED7E8B. The certificate with serial 7A083CC134D0303D is ''incorrect''.
This can be obtained from the [https://certs.it.vt.edu/search VT Certificate Manager]. This requires PID login. Search for "eduroam.nis.vt.edu". Grab the certificate most recently issued.


===Validating the certificate===
===Validating the certificate===
Line 69: Line 60:
<li> Obtain ''all'' certificates in the chain ''in PEM format'' </li>
<li> Obtain ''all'' certificates in the chain ''in PEM format'' </li>
<li> Concatenate the non-leaf certificates in to a single file: </li>
<li> Concatenate the non-leaf certificates in to a single file: </li>
<pre>$ cat GlobalSign_Root_CA_-_R3.pem TrustedRootCASHA256G2.pem VirginiaTechGlobalQualifiedServerCA.pem >> ca.pem</pre>
<pre>$ cat USERTrust_RSA_Certification_Authority.pem InCommonRSAServerCA_2.pem > ca.pem</pre>
<li> Verify the certificates are signed correctly </li>
<li> Verify the certificates are signed correctly </li>
<pre>$ openssl verify -verbose -purpose sslserver -CAfile ca.pem eduroam.nis.vt.edu.crt
<pre>$ openssl verify -verbose -purpose sslserver -CAfile ca.pem eduroam.nis.vt.edu.pem
eduroam.nis.vt.edu.crt: OK</pre>
eduroam.nis.vt.edu.pem: OK</pre>
<li> For at least the root and leaf certificates, verify the subject (compare to above) </li>
<li> For at least the root and leaf certificates, verify the subject (compare to above) </li>
<pre>$ openssl x509 -in file_of_cert_you_want_to_check -noout -subject</pre>
<pre>$ openssl x509 -in file_of_cert_you_want_to_check -noout -subject</pre>
Line 83: Line 74:
Validate the certificate (see above) then generate the sha256 hash:
Validate the certificate (see above) then generate the sha256 hash:


  $ openssl x509 -in VT-Wireless.cns.vt.edu.crt -outform der | sha256sum
  $ openssl x509 -in eduroam.nis.vt.edu.crt -outform der | sha256sum
  9b5163a3360f07b2dce2fd1e958c541687cf4c5360bb8adc87fa821c1c969910  -
  9b5163a3360f07b2dce2fd1e958c541687cf4c5360bb8adc87fa821c1c969910  -


It is recommended that you perform these steps yourself rather than trusting the certificate hash presented in the configurations below.
It is recommended that you perform these steps yourself rather than trusting the certificate hash presented in the configurations below.


'''Note:''' As we are pinning the certificate instead of relying on a PKI, when NI&S rotates the certificates being used (at least every 2 years), the configuration will need to be updated to match the new certificate.
'''Note:''' As we are pinning the certificate instead of relying on a PKI, when NI&S rotates the certificates being used (at least every year), the configuration will need to be updated to match the new certificate.
 
===Getting your network password hash===
MSCHAPv2 verifies the NT4 hash of your password, not the password itself. This means knowing the hash of the password is sufficient to connect to authenticate. Depending on the client, you may be able to store the hash in your config instead of the password. To reiterate, '''this hash is just as sensitive as your password'''. The hash is less human memorable, though, and does act as a deterrent to shoulder-surfing.
 
To derive the password hash, you can:
<pre>
printf 'YOUR-NETW-ORKP-SSWD' \
  | iconv -f ASCII -t UTF-16LE \
  | openssl dgst -md4 \
  | cut -d ' ' -f 2
</pre>
 
If you are using OpenSSL 3, you will need to specify the legacy provider:
<pre>
  | openssl dgst -md4 -provider legacy \
</pre>


===A Word of Caution===
===A Word of Caution===
Although you can verify connection to the Virginia Tech RADIUS servers you must keep in mind that you are connecting to a network that you do not control. It is possible that there are network monitors in place which can record and potentially modify traffic.
Although you can verify connection to the Virginia Tech RADIUS servers you must keep in mind that you are connecting to a network that you do not control. It is possible that there are network monitors in place which can record and potentially modify traffic.


We encourage you to take precautions against network eavesdropping and mischief (on the Eduroam network, and in general). Potential countermeasures that one might want to employ include using [https://www.eff.org/HTTPS-EVERYWHERE HTTPS when connecting to sites], using a [https://www.computing.vt.edu/content/virtual-private-network VPN], or using the [https://www.torproject.org/ Tor Browser Bundle].
We encourage you to take precautions against network eavesdropping and mischief (on the eduroam network, and in general). Potential countermeasures that one might want to employ include using [https://www.eff.org/HTTPS-EVERYWHERE HTTPS when connecting to sites], using a [https://www.computing.vt.edu/content/virtual-private-network VPN], or using the [https://www.torproject.org/ Tor Browser Bundle].


For general tips on improving your security while using the network, consider reading the EFF's [https://ssd.eff.org/ Surveillance Self-Defense] tips, reading [https://www.hokieprivacy.org/ Hokie Privacy], and/or contacting the [https://security.vt.edu/ Virginia Tech Information Security Office].
For general tips on improving your security while using the network, consider reading the EFF's [https://ssd.eff.org/ Surveillance Self-Defense] tips, reading [https://www.hokieprivacy.org/ Hokie Privacy], and/or contacting the [https://security.vt.edu/ Virginia Tech Information Security Office].
Line 99: Line 106:
==NetworkManager Instructions==
==NetworkManager Instructions==


* In your wireless configuration program, select eduroam.
In the list of wireless networks, select "eduroam". Set the following options:
* Choose PEAP as the EAP type.
 
* Choose MSCHAPv2 as the authentication method.
* Wi-Fi security: WPA & WPA2 Enterprise
* Use PID@vt.edu and network passphrase as your login credentials.
* Authentication: Protected EAP (PEAP)
* Use anonymous@vt.edu as your Anonymous Identity
* Anonymous identity: anonymous@vt.edu
* '''TODO:''' Certificate verification (Warning, until certificate verification is added, it is ''not'' recommended that you use this method of accessing the network.)
* Domain: nis.vt.edu
* CA certificate: Select <code>/path/to/USERTrust_RSA_Certification_Authority.pem</code> via the file picker
* PEAP version: Automatic
* Inner authentication: MSCHAPv2
* Username: PID@vt.edu
* Password: YOUR_NETWORK_PASSWORD
 
[[File:Nm settings.png]]


==wpa_supplicant Instructions==
==wpa_supplicant Instructions==
Line 124: Line 138:
     phase2="auth=MSCHAPV2"
     phase2="auth=MSCHAPV2"
     anonymous_identity="anonymous@vt.edu"
     anonymous_identity="anonymous@vt.edu"
    #THIS HASH IS OUT OF DATE, PLEASE FOLLOW INSTRUCTIONS ABOVE
     # if you prefer to pin the certificate, follow the instructions above to generate a hash
     # if you prefer to pin the certificate
     ca_cert="hash://server/sha256/0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff"
     ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a"
     # if you prefer to dynamically validate the certificate by its cryptographic attributes
     # if you prefer to dynamically validate the certificate by its cryptographic attributes
     ca_cert="/path/to/GlobalSign_Root_CA_-_R3.pem"
     ca_cert="/path/to/USERTrust_RSA_Certification_Authority.pem"
     domain_match="eduroam.nis.vt.edu"
     domain_match="eduroam.nis.vt.edu"
     identity="YourPidHere@vt.edu"
     identity="PID@vt.edu"
     password="YourNetworkPasswordHere"
     password="YOUR_NETWORK_PASSWORD"
  }
  }


Line 145: Line 158:


More thorough documentation is available at [https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf]
More thorough documentation is available at [https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf]
===OpenBSD Instructions===
Since the [[OpenBSD]] network stack doesn't support 802.1x authentication, wpa_supplicant is needed to connect. wpa_supplicant on OpenBSD is different from its Linux counterpart in that it is only capable of 802.1x authentication and nothing more. First, install wpa_supplicant from ports if it is not already installed. After that, add just the <code>network={ .. }</code> portion of the above configuration to <code>/etc/wpa_supplicant.conf</code>. The wpa_supplicant service can be enabled with (where iwm0 is your wireless interface):
$ rcctl enable wpa_supplicant
$ rcctl set wpa_supplicant flags -c /etc/wpa_supplicant.conf -s -D openbsd -i iwm0
$ rcctl start wpa_supplicant
Finally, connect to the network with (again, replacing iwm0 with your wireless interface):
$ ifconfig iwm0 join eduroam wpa wpaakms 802.1x up
$ dhclient iwm0
$ ifconfig iwm0 inet6 autoconf


==netctl Instructions==
==netctl Instructions==
Line 167: Line 193:
     'anonymous_identity="anonymous@vt.edu"'
     'anonymous_identity="anonymous@vt.edu"'
     'ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a"'
     'ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a"'
     'domain_match="VT-Wireless.cns.vt.edu"'
     'domain_match="eduroam.nis.vt.edu"'
     'identity="YourPidHere@vt.edu"'
     'identity="YourPidHere@vt.edu"'
     'password="YourNetworkPasswordHere"'
     'password="YourNetworkPasswordHere"'
Line 195: Line 221:
Name = eduroam
Name = eduroam
EAP = peap
EAP = peap
CACertFile = /etc/ssl/certs/GlobalSign_Root_CA_-_R3.pem
CACertFile = /etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem
DomainMatch = eduroam.nis.vt.edu
DomainMatch = eduroam.nis.vt.edu
AnonymousIdentity = anonymous@vt.edu
AnonymousIdentity = anonymous@vt.edu
Line 201: Line 227:
Identity = PID@vt.edu
Identity = PID@vt.edu
Passphrase = NETWORKPASSWORD
Passphrase = NETWORKPASSWORD
</pre>
==iwd Instructions==
This is a sample configuration, usually located at something like <code>/var/lib/iwd/eduroam.8021x</code>. For details, read <code>iwd.network(5)</code>.
<pre>
[Security]
EAP-Method = PEAP
EAP-Identity = anonymous@vt.edu
EAP-PEAP-CACert = embed:USERTrust_RSA_Certification_Authority
EAP-PEAP-ServerDomainMask = eduroam.nis.vt.edu
EAP-PEAP-Phase2-Method = MSCHAPV2
EAP-PEAP-Phase2-Identity = PID@vt.edu
EAP-PEAP-Phase2-Password-Hash = 8846f7eaee8fb117ad06bdd830b7586c
[@pem@USERTrust_RSA_Certification_Authority]
-----BEGIN CERTIFICATE-----
MIIF3jCCA8agAwIBAgIQAf1tMPyjylGoG7xkDjUDLTANBgkqhkiG9w0BAQwFADCB
iDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5ldyBKZXJzZXkxFDASBgNVBAcTC0pl
cnNleSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAsBgNV
BAMTJVVTRVJUcnVzdCBSU0EgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNMTAw
MjAxMDAwMDAwWhcNMzgwMTE4MjM1OTU5WjCBiDELMAkGA1UEBhMCVVMxEzARBgNV
BAgTCk5ldyBKZXJzZXkxFDASBgNVBAcTC0plcnNleSBDaXR5MR4wHAYDVQQKExVU
aGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAsBgNVBAMTJVVTRVJUcnVzdCBSU0EgQ2Vy
dGlmaWNhdGlvbiBBdXRob3JpdHkwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIK
AoICAQCAEmUXNg7D2wiz0KxXDXbtzSfTTK1Qg2HiqiBNCS1kCdzOiZ/MPans9s/B
3PHTsdZ7NygRK0faOca8Ohm0X6a9fZ2jY0K2dvKpOyuR+OJv0OwWIJAJPuLodMkY
tJHUYmTbf6MG8YgYapAiPLz+E/CHFHv25B+O1ORRxhFnRghRy4YUVD+8M/5+bJz/
Fp0YvVGONaanZshyZ9shZrHUm3gDwFA66Mzw3LyeTP6vBZY1H1dat//O+T23LLb2
VN3I5xI6Ta5MirdcmrS3ID3KfyI0rn47aGYBROcBTkZTmzNg95S+UzeQc0PzMsNT
79uq/nROacdrjGCT3sTHDN/hMq7MkztReJVni+49Vv4M0GkPGw/zJSZrM233bkf6
c0Plfg6lZrEpfDKEY1WJxA3Bk1QwGROs0303p+tdOmw1XNtB1xLaqUkL39iAigmT
Yo61Zs8liM2EuLE/pDkP2QKe6xJMlXzzawWpXhaDzLhn4ugTncxbgtNMs+1b/97l
c6wjOy0AvzVVdAlJ2ElYGn+SNuZRkg7zJn0cTRe8yexDJtC/QV9AqURE9JnnV4ee
UB9XVKg+/XRjL7FQZQnmWEIuQxpMtPAlR1n6BB6T1CZGSlCBst6+eLf8ZxXhyVeE
Hg9j1uliutZfVS7qXMYoCAQlObgOK6nyTJccBz8NUvXt7y+CDwIDAQABo0IwQDAd
BgNVHQ4EFgQUU3m/WqorSs9UgOHYm8Cd8rIDZsswDgYDVR0PAQH/BAQDAgEGMA8G
A1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEMBQADggIBAFzUfA3P9wF9QZllDHPF
Up/L+M+ZBn8b2kMVn54CVVeWFPFSPCeHlCjtHzoBN6J2/FNQwISbxmtOuowhT6KO
VWKR82kV2LyI48SqC/3vqOlLVSoGIG1VeCkZ7l8wXEskEVX/JJpuXior7gtNn3/3
ATiUFJVDBwn7YKnuHKsSjKCaXqeYalltiz8I+8jRRa8YFWSQEg9zKC7F4iRO/Fjs
8PRF/iKz6y+O0tlFYQXBl2+odnKPi4w2r78NBc5xjeambx9spnFixdjQg3IM8WcR
iQycE0xyNN+81XHfqnHd4blsjDwSXWXavVcStkNr/+XeTWYRUc+ZruwXtuhxkYze
Sf7dNXGiFSeUHM9h4ya7b6NnJSFd5t0dCy5oGzuCr+yDZ4XUmFF0sbmZgIn/f3gZ
XHlKYC6SQK5MNyosycdiyA5d9zZbyuAlJQG03RoHnHcAP9Dc1ew91Pq7P8yF1m9/
qS3fuQL39ZeatTXaw2ewh0qpKJ4jjv9cJ2vhsE/zB+4ALtRZh8tSQZXq9EfX7mRB
VXyNWQKV3WKdwrnuWih0hKWbt5DHDAff9Yk2dDLWKMGwsAvgnEzDHNb842m1R0aB
L6KCq9NjRHDEjf8tM7qtj3u1cIiuPhnPQCjY/MiQu12ZIvVS5ljFH4gxQ+6IHdfG
jjxDah2nGN59PRbxYvnKkKj9
-----END CERTIFICATE-----
</pre>
</pre>


Line 212: Line 288:


Steps:
Steps:
* From the home screen, press the menu button and choose "Settings"→"Wireless & networks"→"Wi-Fi settings".
* Navigate to the list of Wi-Fi networks.
* Remove any existing entries for eduroam.
* "Forget" any existing entries for eduroam.
* From the "WiFi networks" listing, click on eduroam.
* From the "WiFi networks" listing, click on eduroam.
* Choose PEAP as the EAP method and MSCHAPv2 as the phase two authentication mechanism.
* Choose PEAP as the EAP method and MSCHAPv2 as the phase two authentication mechanism.
* For the CA certificate, select "Use system certificates". Optionally, import the root CA from above, and select that instead for better security.
* For the domain, enter ```eduroam.nis.vt.edu```
* Enter your pid@vt.edu for the identity
* Enter your pid@vt.edu for the identity
* Enter "anonymous@vt.edu" for the anonymous identity
* Enter "anonymous@vt.edu" for the anonymous identity
Line 221: Line 299:
* Press "Connect".
* Press "Connect".


'''TODO:''' Android certificate validation
NOTE: Older versions of Android do not allow not verifying the server certificate. Setting both the root CA and the domain are essential for protecting your credentials. Although older versions will get you connected, use at your own risk.


==Frequently Asked Questions==
==Frequently Asked Questions==
===Is eduroam free?===
===Is eduroam free?===
Eduroam at Virginia Tech is free for:
eduroam at Virginia Tech is free for:
* VT affiliates with VT-Wireless access and network passwords
* VT affiliates with wireless entitlements (includes students) access and network passwords
* Users at other participating institutions
* Users at other participating institutions


===Why is eduroam the preferred SSID?===
===Why is eduroam the preferred SSID?===
Using eduroam has several advantages:
Using eduroam has several advantages:
* Your wifi probes identify you as an eduroam user, rather than a VT affiliate
* The unencrypted portion of your authentication optionally identifies you as "anonymous@vt.edu" rather than revealing your PID
* You have access to seamless roaming if you ever travel to another participating college campus
* You have access to seamless roaming if you ever travel to another participating college campus
* The anonymous identity feature separates RADIUS authentication logs from the network access provider's logs
* The anonymous identity feature separates RADIUS authentication logs from the network access provider's logs


The main disadvantage is that Virginia Tech's eduroam implementation does not appear to support the deprecated [[EAP-TLS]] system, while VT-Wireless does (as of February 2015).
===Does eduroam support EAP-TLS?===
Currently, the Virginia Tech eduroam RADIUS servers are not configured for EAP-TLS.


==References==
==References==
Line 246: Line 325:
[[Category:Howtos]]
[[Category:Howtos]]
[[Category:Campus computing resources]]
[[Category:Campus computing resources]]
[[Category:Needs restoration]]