| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: jkh
|
|
|
|
|
|
|
|
|
|
| |
I'm not quite sure about this, I think it should be using -lssh_pic since
it's being linked into a .so, but nothing seems to complain ahd it does
work. (well, it works for using the authorized_keys file, but I have not
figured out how to get it to start a ssh-agent and cache the key for me)
PR: 17191
Submitted by: Adrian Pavlykevych <pam@polynet.lviv.ua>
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
| |
|
| |
|
| |
|
|
|
|
| |
Found by: sos
|
|
|
|
| |
__PREFIX__ markers.
|
|
|
|
| |
Also - OpenSSH blesses us with a module for PAM.
|
|
|
|
|
|
|
|
| |
might it confuse people, but it causes a warning message with
nroff, and no version history mentions a 1.2 version of FreeBSD.
If anything, a ``HISTORY'' section should show which version this
appeared in.
|
|
|
|
|
|
|
|
|
|
| |
(From the author:)
Primarily, I have added built-in functions for manipulating the
environment, so putenv() is no longer used. XDM and its variants
should now work without modification. Note that the new code uses
the macros in <sys/queue.h>.
Submitted by: Andrew J. Korty <ajk@iu.edu>
|
|
|
|
|
|
|
|
|
| |
"login auth sufficient pam_ssh.so" to your /etc/pam.conf, and
users with a ~/.ssh/identity can login(1) with their SSH key :)
PR: 15158
Submitted by: Andrew J. Korty <ajk@waterspout.com>
Reviewed by: obrien
|
|
|
|
|
| |
if NOCRYPT is defined. Likewise, don't include DES if NOSECURE is
defined.
|
|
|
|
|
| |
because login was already linked against it, but others have a
problem.
|
| |
|
| |
|
| |
|
|
|
|
| |
Noticed by: bde,jdp
|
|
|
|
| |
Reviewed by: jdp
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
|
|
|
|
|
|
|
|
|
| |
simple enough to be trusted.
Add account management functionality to the pam_unix module.
These changes should make it possible to use PAM in some ports.
Submitted by: Max Khon <fjoe@iclub.nsu.ru>
|
|
|
|
|
|
| |
in.
Submitted by: Paul Traina <pst@juniper.net>
|
|
|
|
|
|
|
|
| |
consider a linker set definition to be sufficient reason to pull an
object module from an archive library. This caused undefined
symbols when linking with libpam.a using a.out. I solved it by
linking in the object that references the linker set in the "ld -r"
step.
|
|
|
|
|
| |
pollution." Unfortunately, some of these globals are used by ftpd,
and I broke make world. Pointy hat, please.
|
| |
|
| |
|
|
|
|
| |
Submitted by: asami
|
|
|
|
|
| |
Add a reference to pam(8) in the login(1) and login.access(5) manual
pages.
|
|
|
|
| |
Noticed by: bde
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
modules for FreeBSD's standard authentication methods. Although
the Linux-PAM modules are present in the contrib tree, we don't
use any of them.
The main library "libpam" is composed of sources taken from three
places. First are the standard Linux-PAM libpam sources from the
contrib tree. Second are the Linux-PAM "libpam_misc" sources, also
from the contrib tree. In Linux these form a separate library.
But as Mike Smith pointed out to me, that seems pointless, so I
have combined them into the libpam library. Third are some additional
sources from the "src/lib/libpam" tree with some common functions
that make it easier to write modules. Those I wrote myself.
This work has been donated to FreeBSD by Juniper Networks, Inc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
modules for FreeBSD's standard authentication methods. Although
the Linux-PAM modules are present in the contrib tree, we don't
use any of them.
The main library "libpam" is composed of sources taken from three
places. First are the standard Linux-PAM libpam sources from the
contrib tree. Second are the Linux-PAM "libpam_misc" sources, also
from the contrib tree. In Linux these form a separate library.
But as Mike Smith pointed out to me, that seems pointless, so I
have combined them into the libpam library. Third are some additional
sources from the "src/lib/libpam" tree with some common functions
that make it easier to write modules. Those I wrote myself.
This work has been donated to FreeBSD by Juniper Networks, Inc.
|
| |
|
|
|
|
| |
Also quieten -Wall a bit.
|
|
|
|
|
| |
update man page. Add usage().
Obtained from: OpenBSD
|
|
|
|
| |
(It has been ``SKEY.ACCESS''.)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
doesn't complain.
|
|
|
|
|
|
|
|
|
|
| |
1) Don't spit out an error message if Kerberos is installed but not yet
set up.
2) Don't attempt to verify the ticket you got back, as workstations
are not intended to have srvtab files of their own.
Both behaviors can be re-enabled with KLOGIN_PARANOID.
|
|
|
|
|
| |
Reviewed by:
Submitted by: guido
|
|
|