Bug 1041 - Allow the admin to specify PAM service name
Summary: Allow the admin to specify PAM service name
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: PAM support (show other bugs)
Version: -current
Hardware: All Linux
: P2 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-17 01:52 AEST by Fabio Gomes de Souza
Modified: 2006-10-07 11:40 AEST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Fabio Gomes de Souza 2005-05-17 01:52:53 AEST 
It would be really nice if we could set the pam service name used instead of
'ssh' throuhg some PAMService parameter. 

This would allow for more flexible configurations, for example, using different
authentication backends for concurrent OpenSSH server instances on the same
machine with various IP address or different listening ports.

Thanks in advance and keep the great work. You guys rock.
Comment 1 Darren Tucker 2005-05-17 08:14:16 AEST 
The main distribution already allows this, the PAM service is argv[0].  This
means that if you do "ln -s sshd testsshd" then run "/path/to/testsshd", it will
use the PAM service "testsshd".

Some vendors (eg Debian) hard-code SSHD_PAM_SERVICE during their build process.
 If this is the case for your system then you need to take it up with them.
Comment 2 Fabio Gomes de Souza 2005-05-17 10:38:04 AEST 
Hmm, thank you, Darren. Sorry for the bogus bug report. Maybe I should have
asked on the mailing list first. 

Thanks again. :)
Comment 3 Darren Tucker 2005-05-17 10:42:50 AEST 
OK, closing.
Comment 4 Darren Tucker 2006-10-07 11:40:20 AEST 
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.