19
edits
Changes
m
There On campus, there are three 2 wireless networks on campus:* '''eduroam''': uses federated credentials and is the preferred method. One network, called VT-Wireless, encrypts all traffic * '''VirginiaTech''': for guests and is secured with [[EAP-TLS]] devices that cannot use the authentication method of '''eduroam'''.Any remotely modern/complete Linux or PEAP-MSCHAPv2. A second network, CONNECTtoVT-Wireless, an unencrypted, captive portal wireless network designed Unix system will be able to set up connecting connect to VT-Wireless eduroam without offering Internet access. Due to user any issues faced during deployment, CONNECTtoVT-Wireless began offering captive portal access to VT users.
As of January 2015 the [https://www.computing.vt.edu/content/Because '''eduroam preferred method] of wireless access at Virginia Tech is through the [https://eduroam.org/ Eduroam] network. Eduroam is ''''s credentials are federated, it means that 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 user is that you will be able to automatically connect to the Internet at any participating institution using your Virginia Tech credentialsinstitutions. The Eduroameduroam-US site provides a [https://www.eduroam.us/technical_overview technical overview] of how the network authenticates you to the Virginia Tech RADIUS serversauthentication system.
====Certificate pinning====''Regardless of what software you use to establish your connection, you must first set your remote (network) passphrase by going to [https://my.vt.edu my.vt.edu]→Settings→Change Network Password.''
Where possible, we opt for ===Obtaining the highest level of verification of the certificate: manually pinning the hash of the certificate we expect to be presented. The canonical form of the hash used by many network managers is the SHA256 hash of the DER encoding of the certificate.Certificate Chain===
In order to generate the certificate hash, download the The certificate presented by clicking the "Download" link on the [httpsRADIUS server is chained as such://ash.eprov.seti.vt.edu/EJBCAWebRequest/certSearch?cmd=search&keyword=VT-Wireless Certificate Search for VT-Wireless] (Unfortunately this site is only available to Virginia Tech IPs)
Validate that the downloaded certificate is in fact signed by the (Now Obsolete) [https://secure* USERTrust RSA Certification Authority** InCommon RSA Server CA *** eduroam.hostingnis.vt.edu/www.pki.vt.edu/developer/rootca.html#globalserver Virginia Tech Global Server CA] chain.
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 (TODO''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.
Then generate the sha256 hash (in the directory where the certificate downloaded to):====USERTrust RSA Certification Authority====
We encourage you to take precautions against network eavesdropping and mischief (on To derive the Eduroam networkpassword hash, and in general). Potential countermeasures that one might want to employ include using [httpsyou can://www.eff.org/HTTPS<pre>printf 'YOUR-NETW-ORKP-SSWD' \ | iconv -f ASCII -t UTF-16LE \ | openssl dgst -EVERYWHERE HTTPS when connecting to sites], using a [https://www.computing.vt.edu/content/virtualmd4 \ | cut -privated ' ' -network VPN], or using the [https://www.torproject.orgf 2</ Tor Browser Bundle].pre>
For general tips on improving your security while If you are using the networkOpenSSL 3, consider reading reading you will need to specify the EFF's [httpslegacy provider://ssd.eff.org/ Surveillance Self<pre> | openssl dgst -md4 -Defense] tips and/or contacting the [https://security.vt.eduprovider legacy \</ Virginia Tech Information Security Office].pre>
At DefCon 20 We encourage you to take precautions against network eavesdropping and mischief (on the eduroam network, and in July 2012, an attack was announced for MSCHAPv2 general). Potential countermeasures that allows the protocol one might want to be cracked quickly with a 100% success rate.<ref>employ include using [https://www.cloudcrackereff.comorg/blogHTTPS-EVERYWHERE HTTPS when connecting to sites], using a [https:/2012/07www.computing.vt.edu/29content/crackingvirtual-msprivate-chap-v2network VPN], or using the [https://www.torproject.org/Tor Browser Bundle]</ref> '''Use of MSCHAPv2 is strongly discouraged.'''
==NetworkManager=====eduroam (preferred)===* In your the list of wireless configuration programnetworks, select "eduroam".* Choose PEAP as the EAP type.* Choose MSCHAPv2 as Set the authentication method.* Use PID@vt.edu and network passphrase as your login credentials.* Use anonymous@vt.edu as your Anonymous Identity* '''TODOfollowing options:''' Certificate verification
===VT* Wi-Wireless Fi security: WPA & WPA2 Enterprise* Authentication: Protected EAP (legacyPEAP)===* In your wireless configuration program, select VT-WirelessAnonymous identity: anonymous@vt.edu* Choose PEAP as the EAP typeDomain: nis.vt.edu* Choose MSCHAPv2 as CA certificate: Select <code>/path/to/USERTrust_RSA_Certification_Authority.pem</code> via the file picker* PEAP version: Automatic* Inner authentication method.: MSCHAPv2* Use your {{{identity|Username: PID}}} and network passphrase as your login credentials@vt.edu* Password: YOUR_NETWORK_PASSWORD
===eduroam (preferred)===
===VT-Wireless Alternate config options, besides domain_match are as follows (legacyobviously not correct)===Add the following lines to <code>/etc/wpa_supplicant.conf</code>:
ctrl_interfacesubject_match=DIR"/C=US/runST=CA/wpa_supplicant GROUPL=San Francisco/CN=wheel update_configTest AS/emailAddress=1as@example.com" fast_reauthdomain_suffix_match=1"nis.vt.edu" ap_scan=1 More thorough documentation is available at [https://w1.fi/cgit/hostap/plain/wpa_supplicant/wpa_supplicant.conf] network={ ssid="VT-Wireless" proto=WPA2 key_mgmt=WPA-EAP eapOpenBSD Instructions=PEAP phase2="auth=MSCHAPV2" identitySince 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="your {{{identity|PID.. }}}"</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): password="your passphrase" $ rcctl enable wpa_supplicant ca_cert=" $ rcctl set wpa_supplicant flags -c /etc/ssl/certs/GlobalSign_Root_CAwpa_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.pem1x up $ dhclient iwm0 }$ ifconfig iwm0 inet6 autoconf
===eduroam (preferred)===
'domain_match="eduroam.nis.vt.edu"'
* Create a file, '''/etc/netctl/VT-Wireless''' and place this in it:[service_wifi_3c15c2e29584_656475726f616d_managed_ieee8021x] DescriptionType ="VT-Wireless PEAP-MSCHAPv2"wifi InterfaceName =wlan0eduroam ConnectionEAP =wirelesspeap SecurityCACertFile =wpa-configsection /etc/ssl/certs/USERTrust_RSA_Certification_Authority.pem IPDomainMatch =dhcpeduroam.nis.vt.edu IP6AnonymousIdentity =statelessanonymous@vt.edu WPAConfigSection=( 'ssid="VT-Wireless"' 'proto=RSN' 'key_mgmt=WPA-EAP' 'eap=PEAP' 'phase2="authPhase2 =MSCHAPV2"' 'identityIdentity ="YOUR IDENTITY"'PID@vt.edu 'passwordPassphrase ="NETWORK PASSWORD"NETWORKPASSWORD 'ca_cert="/etc/ssl/certs</GlobalSign_Root_CA.pem"' )pre>
Make sure to change '''IDENTITY''' to your {{{identity|PID}}}==iwd Instructions==This is a sample configuration, and '''NETWORK PASSWORD''' to your usually located at something like <code>/var/lib/iwd/eduroam.8021x</code>. For details, read <code>iwd.network password(5)</code>.
* After creating this file, make sure to change the owner to root (<codepre>sudo chown root[Security]EAP-Method = PEAPEAP-Identity = anonymous@vt.eduEAP-PEAP-CACert = embed:root /etc/netctl/VTUSERTrust_RSA_Certification_AuthorityEAP-Wireless</code>) and change the permissions so that it can be read only by the owner (<code>sudo chmod 0600 /etc/netctl/VTPEAP-Wireless</code>)ServerDomainMask = eduroam.nis.vt. This will ensure that your private key password cannot be read by others easilyeduEAP-PEAP-Phase2-Method = MSCHAPV2EAP-PEAP-Phase2-Identity = PID@vt.eduEAP-PEAP-Phase2-Password-Hash = 8846f7eaee8fb117ad06bdd830b7586c
* To connect, simply type the following in a terminal:[@pem@USERTrust_RSA_Certification_Authority] sudo netctl start VT-Wireless----BEGIN CERTIFICATE-----MIIF3jCCA8agAwIBAgIQAf1tMPyjylGoG7xkDjUDLTANBgkqhkiG9w0BAQwFADCBiDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5ldyBKZXJzZXkxFDASBgNVBAcTC0plcnNleSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAsBgNVBAMTJVVTRVJUcnVzdCBSU0EgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwHhcNMTAwMjAxMDAwMDAwWhcNMzgwMTE4MjM1OTU5WjCBiDELMAkGA1UEBhMCVVMxEzARBgNVBAgTCk5ldyBKZXJzZXkxFDASBgNVBAcTC0plcnNleSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxLjAsBgNVBAMTJVVTRVJUcnVzdCBSU0EgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQCAEmUXNg7D2wiz0KxXDXbtzSfTTK1Qg2HiqiBNCS1kCdzOiZ/MPans9s/B3PHTsdZ7NygRK0faOca8Ohm0X6a9fZ2jY0K2dvKpOyuR+OJv0OwWIJAJPuLodMkYtJHUYmTbf6MG8YgYapAiPLz+E/CHFHv25B+O1ORRxhFnRghRy4YUVD+8M/5+bJz/Fp0YvVGONaanZshyZ9shZrHUm3gDwFA66Mzw3LyeTP6vBZY1H1dat//O+T23LLb2VN3I5xI6Ta5MirdcmrS3ID3KfyI0rn47aGYBROcBTkZTmzNg95S+UzeQc0PzMsNT79uq/nROacdrjGCT3sTHDN/hMq7MkztReJVni+49Vv4M0GkPGw/zJSZrM233bkf6c0Plfg6lZrEpfDKEY1WJxA3Bk1QwGROs0303p+tdOmw1XNtB1xLaqUkL39iAigmTYo61Zs8liM2EuLE/pDkP2QKe6xJMlXzzawWpXhaDzLhn4ugTncxbgtNMs+1b/97lc6wjOy0AvzVVdAlJ2ElYGn+SNuZRkg7zJn0cTRe8yexDJtC/QV9AqURE9JnnV4eeUB9XVKg+/XRjL7FQZQnmWEIuQxpMtPAlR1n6BB6T1CZGSlCBst6+eLf8ZxXhyVeEHg9j1uliutZfVS7qXMYoCAQlObgOK6nyTJccBz8NUvXt7y+CDwIDAQABo0IwQDAdBgNVHQ4EFgQUU3m/WqorSs9UgOHYm8Cd8rIDZsswDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQFMAMBAf8wDQYJKoZIhvcNAQEMBQADggIBAFzUfA3P9wF9QZllDHPFUp/L+M+ZBn8b2kMVn54CVVeWFPFSPCeHlCjtHzoBN6J2/FNQwISbxmtOuowhT6KOVWKR82kV2LyI48SqC/3vqOlLVSoGIG1VeCkZ7l8wXEskEVX/JJpuXior7gtNn3/3ATiUFJVDBwn7YKnuHKsSjKCaXqeYalltiz8I+8jRRa8YFWSQEg9zKC7F4iRO/Fjs8PRF/iKz6y+O0tlFYQXBl2+odnKPi4w2r78NBc5xjeambx9spnFixdjQg3IM8WcRiQycE0xyNN+81XHfqnHd4blsjDwSXWXavVcStkNr/+XeTWYRUc+ZruwXtuhxkYzeSf7dNXGiFSeUHM9h4ya7b6NnJSFd5t0dCy5oGzuCr+yDZ4XUmFF0sbmZgIn/f3gZXHlKYC6SQK5MNyosycdiyA5d9zZbyuAlJQG03RoHnHcAP9Dc1ew91Pq7P8yF1m9/qS3fuQL39ZeatTXaw2ewh0qpKJ4jjv9cJ2vhsE/zB+4ALtRZh8tSQZXq9EfX7mRBVXyNWQKV3WKdwrnuWih0hKWbt5DHDAff9Yk2dDLWKMGwsAvgnEzDHNb842m1R0aBL6KCq9NjRHDEjf8tM7qtj3u1cIiuPhnPQCjY/MiQu12ZIvVS5ljFH4gxQ+6IHdfGjjxDah2nGN59PRbxYvnKkKj9-----END CERTIFICATE-----</pre>
===eduroam (preferred)===A sample configuration is available to the right, but as this configuration is currently lacking CA certificate validation, we do not at this time recommend connecting to the network.
A sample configuration is available The Identity needs to be modified to match your PID@vt.edu, and your Network Password needs to be entered in the rightPassword field. Steps:* Navigate to the list of Wi-Fi networks.* "Forget" any existing entries for eduroam.* From the "WiFi networks" listing, but click on eduroam.* Choose PEAP as the EAP method and MSCHAPv2 as this configuration is currently lacking the phase two authentication mechanism.* For the CA certificate validation, we 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 "anonymous@vt.edu" for the anonymous identity* Enter your Network Password for the password* Press "Connect". 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 this time recommend connecting to the networkyour own risk.
'''TODO==Frequently Asked Questions=====Is eduroam free?===eduroam at Virginia Tech is free for:''' Android certificate validation* VT affiliates with wireless entitlements (includes students) access and network passwords* Users at other participating institutions
* From the home screen, press the menu button and choose "Settings"→"Wireless & networks"→"Wi===Does eduroam support EAP-Fi settings".* Remove any existing entries for {{{networks|the network you'd like to add or any conflicting network}}}.TLS?===* From the "WiFi networks" listingCurrently, click on {{{network|the network you'd like to add}}}.* Choose PEAP as the Virginia Tech eduroam RADIUS servers are not configured for EAP method and MSCHAPv2 as the phase two authentication mechanism.* Enter your credentials for the identity and press "Connect"-TLS.
==General Connection informationInformation==
===eduroam===
The following settings are recommended for connecting to the Eduroam eduroam network:
* '''SSID: ''' eduroam* '''EAP: ''' PEAP* '''Phase 2: ''' MSCHAPv2* '''Root CA:''' "USERTrust RSA Certification Authority" or pin the certificate (see below)* '''Server Name:''' eduroam.nis.vt.edu* '''Identity: ''' pid@vt.edu (So if your PID was "hokiebird", hokiebird@vt.edu)* '''Anonymous Identity: ''' anonymous@vt.edu* '''Password: ''' [https://www.computing.vt.edu/kb/entry/3765 Your Network Password]
''Filename:'' USERTrust_RSA_Certification_Authority.pem ''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/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. ====InCommon RSA Server CA==== ''Filename:'' InCommonRSAServerCA_2.pem ''Subject:'' C = US, ST = MI, L = Ann Arbor, O = Internet2, OU = InCommon, CN = InCommon RSA Server CA This is an intermediate certificate issued to InCommon. You can get it directly from InCommon [http://crt.usertrust.com/InCommonRSAServerCA_2.crt here]. ====eduroam.nis.vt.edu==== ''Filename:'' eduroam.nis.vt.edu.pem ''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://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=== <ol><li> Obtain ''all'' certificates in the chain ''in PEM format'' </li><li> Concatenate the non-leaf certificates in to a single file: </li><pre>$ cat USERTrust_RSA_Certification_Authority.pem InCommonRSAServerCA_2.pem > ca.pem</pre><li> Verify the certificates are signed correctly </li><pre>$ openssl verify -verbose -purpose sslserver -CAfile ca.pem eduroam.nis.vt.edu.pemeduroam.nis.vt.edu.pem: OK</pre><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></ol> ===Certificate Pinning=== Due to vulnerabilities in the MSCHAPv2 protocol that allow the protocol to be cracked quickly with a 100% success rate<ref>[https://web.archive.org/web/20160316174007/https://www.cloudcracker.com/blog/2012/07/29/cracking-ms-chap-v2/]</ref>, it is ''absolutely critical'' that the RADIUS server certificate be validated properly before attempting authentication. Where possible, we opt for the highest level of verification of the certificate: manually pinning the hash of the certificate we expect to be presented. The canonical form of the hash used by many network managers is the SHA256 hash of the DER encoding of the certificate. Validate the certificate (see above) then generate the sha256 hash: $ openssl x509 -in VT-Wirelesseduroam.cnsnis.vt.edu.crt -outform der | sha256sum 216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a 9b5163a3360f07b2dce2fd1e958c541687cf4c5360bb8adc87fa821c1c969910 -
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 CNS NI&S rotates the certificates being used(at least every year), the configuration will need to be updated to match the new certificate.
====A word of caution=Getting your network password hash===Although 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 can verify connection may be able to store the Virginia Tech RADIUS servers you must keep hash in mind that you are connecting to a network that you do not controlyour config instead of the password. To reiterate, '''this hash is just as sensitive as your password'''. It The hash is possible that there are network monitors in place which can record less human memorable, though, and potentially modify trafficdoes act as a deterrent to shoulder-surfing.
===A word Word of caution on MSCHAPv2Caution===Warning: Use of PEAP-MSCHAPv2 to connect 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 strongly discouraged by the Linux and Unix Users Group due to attacks possible that there are network monitors in place which can allow all record and potentially modify traffic to be decrypted with a 100% success rate. Unfortunately, VT has deprecated its use so users will soon lose the choice to use certificates.
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].
==Set your remote access (network) passphraseNetworkManager Instructions==Regardless of what software you use to establish your connection, you must first set your remote passphrase by going to [https://my.vt.edu my.vt.edu]→Settings→Change Network Password.
[[File:Nm settings.png]] ==wpa_supplicantInstructions==
[http://w1.fi/wpa_supplicant/ wpa_supplicant] is a cross-platform supplicant which implements IEEE 802.1x/WPA and is used in many Linux/UNIX distributions.
ctrl_interface=DIR=/run/wpa_supplicant GROUP=wheel
update_config=1
fast_reauth=1
ap_scan=1
phase2="auth=MSCHAPV2"
anonymous_identity="anonymous@vt.edu"
# if you prefer to pin the certificate, follow the instructions above to generate a hash ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" # if you prefer to dynamically validate the certificate by its cryptographic attributes ca_cert="/path/to/USERTrust_RSA_Certification_Authority.pem" domain_match="eduroam.nis.vt.edu" identity="YourPidHerePID@vt.edu" password="YourNetworkPasswordHereYOUR_NETWORK_PASSWORD"
}
$ sudo dhcpcd wlan0
==netctlInstructions==
[https://wiki.archlinux.org/index.php/netctl netctl] is a network manager which is native to the ArchLinux distribution. netctl makes use of wpa_supplicant under the hood, and so the configuration is similar.
Put the following configuration in <code>/etc/netctl/eduroam</code> with your proper PID and Network Password. Further, this assumes that your wireless network device is wlan0, which you might have to change to match your system. The ca_cert line pins the server certificate and can be generated/validated using the mechanism described above.
'anonymous_identity="anonymous@vt.edu"'
'ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a"'
'identity="YourPidHere@vt.edu"'
'password="YourNetworkPasswordHere"'
)
The ConfigSection (as per the netctl.profile manpage) is just what you would put in a wpa_supplicant config. Again, note that the domain_match is ''less secure'' than ca_cert, but better than not checking at all.
Ensure that this file is owned by root and only readable by root:
$ sudo netctl start eduroam
===VT-Wireless (legacy)=connman Instructions ==Tested on This config should be useable with connman. Replace Passphrase and Identity with your Network password and PID@vt.edu, respectively. <pre>[[Arch Linuxglobal]] with netctl 0.8 (updated on 2013-04-12)Name = eduroamDescription = Optionally put something descriptive here.
==AndroidInstructions==
[[File:AndroidEduroamNoCert.png|170px|thumb|Sample Android configuration of eduroam, but crucially lacking certificate validation.]]
=== VT-Wireless (legacy)Why is eduroam the preferred SSID?==={{Version|2Using eduroam has several advantages:* The unencrypted portion of your authentication optionally identifies you as "anonymous@vt.2 (Froyo) of Android}}edu" rather than revealing your PID* 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
==References==
<references/>
===Network Information Sources===
* [http://www.cns.vt.edu/html/wireless/wlan/index.html Communications Network Services: Wireless LAN]
* [http://computing.vt.edu/internet_and_web/internet_access/ipaddresses.html Virginia Tech IP Addresses]
[[Category:Howtos]]
[[Category:Campus computing resources]]
[[Category:Needs restoration]]
