Re: pam_sshauth update - status update, ready for hacking?

Vagrant Cascadian <[email protected]> Mon, 4 Apr 2011 16:56:56 -0700
Newsgroups gmane.linux.terminal-server.devel
Message-ID <[email protected]>
On Mon, Apr 04, 2011 at 09:36:44AM -0500, Scott Balneaves wrote:
> On Wed, Mar 30, 2011 at 08:55:01AM -0500, Scott Balneaves wrote:
> > On Tue, Mar 22, 2011 at 09:52:37AM -0500, Scott Balneaves wrote:
> > 
> > By way of an update, I've progressed reasonably well along getting things to
> > work.

very exciting!

 
> I didn't get a chance to update this before I went away to my son's Basketball
> tourney on the weekend, but I'm happy to report that I actually got a
> successful login, and desktop start using pam_sshauth on the weekend.  In
> keeping with using retro XDM, and for nostalgia purposes, I started TWM
> remotely. :)

go scotty "retro nostalgia" balneaves!

 
> I simply had to create a custom script for the x-window-manager binary, and xdm
> picked it up automatically.
> 
> At this point, tonight I'll spend some time cleaning things up, and trying to
> get manual pages written, and blow away my chroot and "do it properly".
> Specifically:
> 
> 1) Use "pam-auth-update" to manipulate the actual pam configs, as opposed to 
>    diddling with the pam configs using vi.  My understanding is that this is
>    shipped as part of the pam packages, and so *should* be a good bet that
>    it'll be available on all Linuxes.

it uses debconf, so my guess is it's debian and derivatives only...

 
> 2) Use update-alternatives to set the x-window-manager link.

this should happen automatically with most window managers and/or desktop 
environments when installing the package.

 
> I know dynamic host selection at login time is something we need, so I'll also
> code up a "gethost=" parameter for the pam_sshauth module.  It'll point to an
> executable, of which I'll expect to read one line containing a newline
> terminated host ip or name that will be used as the basis to select a host to
> log in on.
> 
> Finally, I know we have the ability, within LDM, of selecting from a menu which
> host to log in on.  Most greeters don't have this ability, however, my
> understanding is that we can code up greeters for LightDM using HTML, as it
> used webkit to render the greeter page.  I'm imagining we can somehow populate,
> and then return the host from that page.  In that case, simply pre-setting the
> PAM_SSHAUTH_HOST environment variable should have the intended result, so I
> think we can handle that use-case.
> 
> Once I get all this done in the next day or so, I'd wonder if any interested
> LTSP hackers would have time to get together for an evening online, and see if
> we can somehow bolt this into the ltsp-build-client command?

so, you're thinking of an ltsp-build-client hook to use this as an alternate 
method for fatclients?


live well,
  vagrant

------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net