I will be out of the office starting 06/15/2005 and will not return until 07/04/2005.
I will respond to your message when I return. If this is an urgent request please re-direct to [EMAIL PROTECTED]
**
Participation and subscription information for this EDUCAUSE Constituent Group
Chris Hart wrote:
At Northwestern University we are looking to move away from using VPN
for Authentication and Encryption for our wireless users.
We do not want to have to use 3rd party supplicants because of end
user support issues.
We are currently using Funk Steel Belted Radius and have
(This issue was enough for our campus security people to tell
us that we can't use PEAP.)
Wow... Are you guys not allowed to use Active Directory either? :) Do
you have to encrypt all of your Social Security Numbers stored on your
systems? The point being that storing insecure data can be
Hi Chris,
At UBC, we have rolled out PEAP (MS PEAP). We looked at TTLS but since
we already have MSChap support cooked into our single sign-on system to
support VPN PPTP, PEAP support was relatively easy.
TTLS was considered but it wasn't well supported when we made the
decision and
Michael Griego wrote:
(This issue was enough for our campus security people to tell us that
we can't use PEAP.)
Wow... Are you guys not allowed to use Active Directory either? :)
Do you have to encrypt all of your Social Security Numbers stored on
your systems? The point being that
Chris Hessing wrote:
Assume for a second that you decide the right way to go is to
purchase server certificates from Verisign. The client is probably
going to already have a copy of their public root CA on their
machine. During the TLS phase of the authentication, the client will
verify
