Virginia Tech Wifi: Difference between revisions

Waldrep (talk | contribs)
m s/Eduroam/eduroam/g
Waldrep (talk | contribs)
Change root CA from GlobalSign to USERTrust
Line 10: Line 10:
* '''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 22: Line 22:
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 page seems to not be loading correctly at the moment. [https://support.globalsign.com/customer/en/portal/articles/1426602-globalsign-root-certificates Here] is the parent page.)
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 expires 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====
====USERTrust RSA Certification Authority====


''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 by 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 66: Line 57:
<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 102: Line 93:
* Anonymous identity: anonymous@vt.edu
* Anonymous identity: anonymous@vt.edu
* Domain: nis.vt.edu
* Domain: nis.vt.edu
* CA certificate: Select <code>/path/to/GlobalSign_Root_CA_-_R3.pem</code> via the file picker
* CA certificate: Select <code>/path/to/USERTrust_RSA_Certification_Authority.pem</code> via the file picker
* PEAP version: Automatic
* PEAP version: Automatic
* Inner authentication: MSCHAPv2
* Inner authentication: MSCHAPv2
Line 132: Line 123:
     ca_cert="hash://server/sha256/216c5f2568c6e84860b12535efe93500623ccee999306b84260f951bcbd57b1a"
     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="YourPidHere@vt.edu"
Line 206: Line 197:
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 238: Line 229:
# Do not validate: you will get online, but consider your connection to be as secure as a public hotspot
# Do not validate: you will get online, but consider your connection to be as secure as a public hotspot
# (Android 7.1+ only) Use system certificates: This will check to make sure the certificate chains back to some CA in the system cert store. This is significantly better than no validation, but still not very good. You may also need to specify a domain. If so, use "vt.edu"
# (Android 7.1+ only) Use system certificates: This will check to make sure the certificate chains back to some CA in the system cert store. This is significantly better than no validation, but still not very good. You may also need to specify a domain. If so, use "vt.edu"
# Download and import the GlobalSign Root CA: detailed instructions to come. Since you are still not checking the CN, it is only marginally better than using system certificates.
# Download and import the USERTrust Root CA: detailed instructions to come. Since you are still not checking the CN, it is only marginally better than using system certificates.
# Use the [https://play.google.com/store/apps/details?id=uk.ac.swansea.eduroamcat eduroam CAT] tool: this will setup the whole wireless profile and use the correct CA and verify the CN. As such, it is the preferred method. Warning, it is ugly. If you have an existing "eduroam" profile, you will need to remove it. When it prompts for the username and password, use <YOUR-PID>@vt.edu and your network password. It relies on geolocation to prompt for the profile for the right school. You may need to go outside to get a good GPS signal. If it is able to do geo-ip (e.g., you are connected to the "VirginiaTech" SSID), it gets you close enough.
# Use the [https://play.google.com/store/apps/details?id=uk.ac.swansea.eduroamcat eduroam CAT] tool: this will setup the whole wireless profile and use the correct CA and verify the CN. As such, it is the preferred method. Warning, it is ugly. If you have an existing "eduroam" profile, you will need to remove it. When it prompts for the username and password, use <YOUR-PID>@vt.edu and your network password. It relies on geolocation to prompt for the profile for the right school. You may need to go outside to get a good GPS signal. If it is able to do geo-ip (e.g., you are connected to the "VirginiaTech" SSID), it gets you close enough.