Re: Proposed new blocking criterion for Fedora Server: GSSAPI SSO via SSH

2015-10-06 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/06/2015 12:59 PM, Adam Williamson wrote: > I'm OK with this so long as it comes along with a matching test > case. > Yes, assuming this is agreed-upon to be a blocking criterion, I will write up a test-case. -BEGIN PGP SIGNATURE- Versio

Re: Proposed new blocking criterion for Fedora Server: GSSAPI SSO via SSH

2015-10-06 Thread Adam Williamson
On Mon, 2015-10-05 at 15:05 -0400, Stephen Gallagher wrote: > Currently, we have a number of blocking criterion in Fedora Server > around domain membership that the machine must be able to join a > domain and that a user must be able to log into the machine using > standard login mechanisms (consol

Re: Proposed new blocking criterion for Fedora Server: GSSAPI SSO via SSH

2015-10-05 Thread Sudhir D
On 10/06/2015 12:35 AM, Stephen Gallagher wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Currently, we have a number of blocking criterion in Fedora Server around domain membership that the machine must be able to join a domain and that a user must be able to log into the machine using s

Re: Proposed new blocking criterion for Fedora Server: GSSAPI SSO via SSH

2015-10-05 Thread Mike Ruckman
On Mon, Oct 05, 2015 at 03:05:42PM -0400, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Currently, we have a number of blocking criterion in Fedora Server > around domain membership that the machine must be able to join a > domain and that a user must be able to lo

Proposed new blocking criterion for Fedora Server: GSSAPI SSO via SSH

2015-10-05 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Currently, we have a number of blocking criterion in Fedora Server around domain membership that the machine must be able to join a domain and that a user must be able to log into the machine using standard login mechanisms (console, GDM, etc.). What