I can at least share one of our primary motivations - what I refer to as the
"girlfriend" problem.
We all know that despite any warnings we can come up with, there are
circumstances where students will share their passwords with others for
network access, whether it's a boyfriend/girlfriend, family, or just a weekend
guest. We've had it happen in our greek houses a few times, where the house
itself is renting out a room to a guest completely unaffiliated with the
university.
Moving to EAP-TLS obviously doesn't stop this from happening, but it means
that when they do share out their wireless credentials, they're at least not
sharing their password to email, LMS, and everything else along with it.
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
Manager of Network Operations | is simple, elegant, and wrong.
Worcester Polytechnic Institute | - HL Mencken
On 9/21/2015 7:44 PM, David R. Morton wrote:
Ryan,
I too would like to hear about your lessons learned across all the areas you
listed in your message.
David
David Morton
Director, Mobile Communications
Service Owner: Wi-Fi, Mobile & HuskyTV
University of Washington
[email protected] <mailto:[email protected]>
tel 206.221.7814
On Sep 21, 2015, at 4:40 AM, Osborne, Bruce W (Network Services)
<[email protected] <mailto:[email protected]>> wrote:
Will you be able to share at least part of this presentation on this list?
I am sure some of us cannot attend but are looking to implement EAP-TLS.
*Bruce Osborne*
/Wireless Engineer/
*IT Infrastructure & Media Solutions*
*(434) 592-4229*
*LIBERTY UNIVERSITY*
/Training Champions for Christ since 1971/
*From:*Turner, Ryan H [mailto:[email protected]]
*Sent:*Friday, September 18, 2015 9:55 AM
*Subject:*Help on a conference presentation on EAP-TLS
All:
I am doing a presentation on lessons learned on converting to TLS for a UNC
Cause next month. We have plenty of mistakes along the way to share with
the people that will be listening, but I thought it might be fun for others
to ‘fess up’ to their TLS screw-ups… For example, maybe missing on a
technical point that would cause grief down the road, to adopting a policy
change that in hind sight wasn’t the best. We will also cover how we have
pivoted our onboarding platform from Cloudpath to SecureW2 and redesigned
the method of onboarding to significantly reduce helpdesk calls.
No one likes to admit mistakes, but that is why I like working in
education… everyone can share.
However, please feel free to share DIRECTLY with me. You don’t need to copy
the list. Please give me permission to share in the email, and let me know
if you want it anonymous, or if you want your screw-up properly creditedJ
[email protected] <mailto:[email protected]>
Ryan H Turner
Senior Network Engineer
The University of North Carolina at Chapel Hill
CB 1150 Chapel Hill, NC 27599
+1 919 445 0113 Office
+1 919 274 7926 Mobile
********** Participation and subscription information for this EDUCAUSE
Constituent Group discussion list can be found
athttp://www.educause.edu/groups/.
********** Participation and subscription information for this EDUCAUSE
Constituent Group discussion list can be found
athttp://www.educause.edu/groups/.
********** Participation and subscription information for this EDUCAUSE
Constituent Group discussion list can be found at
http://www.educause.edu/groups/.
**********
Participation and subscription information for this EDUCAUSE Constituent Group
discussion list can be found at http://www.educause.edu/groups/.
