Kerberos for Windows 3.2 is released

2007-05-03 Thread Tom Yu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The MIT Kerberos Development Team and Secure Endpoints Inc. are proud to announce the release of MIT's Kerberos for Windows product, Version 3.2. Supported Versions of Microsoft Windows === This release requires

Re: Cross Realm MIT - Windows Close But No Cigar

2007-05-03 Thread Markus Moeller
What does sshd -ddde show when you connect ? Do you use a .k5login or auth_to_local ? Markus Michael B Allen [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello, I struggling with cross realm auth and I'd appreciate it if someone can give me pointers. The problem seems to be

Re: Cross Realm MIT - Windows Close But No Cigar

2007-05-03 Thread Michael B Allen
On Thu, 3 May 2007 23:33:29 +0100 Markus Moeller [EMAIL PROTECTED] wrote: What does sshd -ddde show when you connect ? Do you use a .k5login or auth_to_local ? Hi Markus, I'm not familiar with .k5login or auth_to_local. The only thing I changed in sshd_config was I turned of UsePAM. I

Re: Cross Realm MIT - Windows Close But No Cigar

2007-05-03 Thread Christopher D. Clausen
Michael B Allen [EMAIL PROTECTED] wrote: On Thu, 3 May 2007 23:33:29 +0100 Markus Moeller [EMAIL PROTECTED] wrote: What does sshd -ddde show when you connect ? Do you use a .k5login or auth_to_local ? Hi Markus, I'm not familiar with .k5login or auth_to_local. The only thing I changed

Re: Cross Realm MIT - Windows Close But No Cigar

2007-05-03 Thread Michael B Allen
On Thu, 3 May 2007 20:31:55 -0500 Christopher D. Clausen [EMAIL PROTECTED] wrote: Try creating a ~/.k5login file in the home directory of the user you are logging in as listing authorized Kerberos principals, one per line. That was it! SSH now works cross realm. I was clueless about

Re: Cross Realm MIT - Windows Close But No Cigar

2007-05-03 Thread Christopher D. Clausen
Michael B Allen [EMAIL PROTECTED] wrote: On Thu, 3 May 2007 20:31:55 -0500 Christopher D. Clausen [EMAIL PROTECTED] wrote: Try creating a ~/.k5login file in the home directory of the user you are logging in as listing authorized Kerberos principals, one per line. That was it! SSH now works