similar to: [Bug 655] sshd_config.5: 'GSSAPICleanupCredentials' -> '...Creds'

Displaying 20 results from an estimated 4000 matches similar to: "[Bug 655] sshd_config.5: 'GSSAPICleanupCredentials' -> '...Creds'"

2003 Dec 10
1
GSSAPICleanupCredentials vs GSSAPICleanupCreds
In 3.7.1p2, the sshd_config manpage talks about GSSAPICleanupCredentials, while servconf.c uses GSSAPICleanupCreds. Here is a patch: --- openssh-3.7.1p2/servconf.c.orig 2003-12-10 10:43:52.000000000 -0200 +++ openssh-3.7.1p2/servconf.c 2003-12-10 10:44:13.000000000 -0200 @@ -310,10 +310,10 @@ { "afstokenpassing", sUnsupported }, #ifdef GSSAPI {
2006 Oct 12
0
GSSAPICleanupCredentials and UsePrivilegeSeperation
It looks to me like GSSAPICleanupCredentials doesn't work if UsePrivilegeSeparation is set to "no". Is this a bug, or am I doing something wrong? On a related note, is there a SERVER way to disable GSSAPIDelegateCredentials?
2000 Aug 28
1
ANNOUNCE: x11-ssh-askpass v1.0.1
x11-ssh-askpass version 1.0.1 is now available from the following locations: http://www.jmknoble.cx/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH (www.openssh.com) under the X Window System. The important changes since version 1.0 are as follows: - Bugfixes: - If the keyboard or
2001 Sep 17
2
ANNOUNCE: x11-ssh-askpass v1.2.4
x11-ssh-askpass version 1.2.4 (code name: Boudin) is now available from the following locations: http://www.poboxc.com/~jmknoble/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH <http://www.openssh.com/> under the X Window System. Significant changes since version 1.2.2 include: - Minor
2001 Sep 17
2
ANNOUNCE: x11-ssh-askpass v1.2.4
x11-ssh-askpass version 1.2.4 (code name: Boudin) is now available from the following locations: http://www.poboxc.com/~jmknoble/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH <http://www.openssh.com/> under the X Window System. Significant changes since version 1.2.2 include: - Minor
2001 Apr 02
1
ANNOUNCE: x11-ssh-askpass v1.2.1
x11-ssh-askpass version 1.2.1 (code name: Fatoomsh) is now available from the following locations: http://www.jmknoble.cx/software/x11-ssh-askpass/ http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/ x11-ssh-askpass is a passphrase dialog for use with OpenSSH (www.openssh.com) under the X Window System. The important changes since version 1.2.1 are as follows: - Added a
2001 Mar 31
1
libexecdir changed again?
[See my comments below.] ----- Forwarded message from an x11-ssh-askpass customer ----- Date: Fri, 30 Mar 2001 16:34:28 -0800 Subject: x11-ssh-askpass 1.2.0 To: jmknoble at jmknoble.cx I just installed x11-ssh-askpass 1.2.0 on some systems, and ran into a couple of minor problems: OpenSSH 2.5.2p2 by default is looking for ssh-askpass in /usr/local/libexec, not /usr/local/libexec/openssh. It
1999 Dec 06
1
New x11-ssh-askpass release available
http://www.pobox.com/~jmknoble/jmk/x11-ssh-askpass-1999.12.04.tar.gz Changes: 1999-12-05 04:21 jmknoble * Imakefile: Added patch from Markus Friedl to change use of awk (with GNU-specific extensions?) to sed, more likely to be available on various platforms. X11-ssh-askpass is drop-in passphrase dialog for OpenSSH, based solely on the regular X11 libraries (libX11,
2003 Oct 01
2
documentation update?
The INSTALL file in the current distribution has the passphrase request at http://www.ntrnet.net/~jmknoble/software/x11-ssh-askpass/index.html maybe this should be changed to http://www.liquidmeme.net/software/x11-ssh-askpass ?? -- Antonino Iannella Santos Ltd 91 King William St ADELAIDE SA 5000 Ph +618 8224 7712 Fax +618 8224 7577 Mobile +61408 800007 Email antonino.iannella at
2001 Feb 16
3
PATCH: make contrib/redhat/sshd.init work with older RH releases
Damien-- Attached is a patch to contrib/redhat/sshd.init which eliminates the dependency on the success() and failure() functions from initscripts>=4.16. This allows sshd.init to be used for both early and recent releases of Red Hat Linux (i've confirmed it works on both 4.2 and 5.2 as well as 6.2). The patch also removes the 'Requires: initscripts >= 4.16' line from
2001 Jan 22
3
CVS source tree from 22 Jan 2001
Makefile.in is not fixed ! in old ssh.h # define SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" in new pathnames.h #define _PATH_SSH_ASKPASS_DEFAULT "/usr/X11R6/bin/ssh-askpass" but in Makefile.in PATHS=...-DSSH_ASKPASS_DEFAULT=\"$(ASKPASS_PROGRAM)\" ----------------------------------------------------------- about patch: - remove unused defines:
2003 Mar 26
1
Changing PAM service name in sshd_config, or running sshd as non-root
Currently, openssh's PAM service name is a compile-time choice. That's fine when one uses one sshd to serve normal shell logins and the like. But this will not work IF sshd is nor run as root (which I don't want it to do), because pam_open_session usually requires access to one's shadow information (for account expiration perhaps?), and there is no way (and need: this sshd is
2017 May 01
2
SSH1 deleted
-- jim knoble | jmknoble at pobox.com > On Apr 30, 2017, at 19:40, Darren Tucker <dtucker at zip.com.au> wrote: > >> On Mon, May 1, 2017 at 12:09 PM, Damien Miller <djm at mindrot.org> wrote: >> >> Hi, >> >> I just deleted SSHv1 support in OpenBSD and portable OpenSSH. There's >> probably a little dead code still to be expunged, but
2001 Feb 18
3
PATCH: Round 2: RH initscripts backward compatibility
I've cleaned up Pekka Savola's newly revised sshd.init and additional sshd-functions and modified them to work they way i've been arguing they should work. Compatibility functions are defined in ./contrib/redhat/sshd-functions, which should get installed no matter what release of Red Hat Linux OpenSSH is getting built for, to be consistent across releases. Specific changes from
2009 Jan 22
8
[Bug 1550] New: Move from 3DES to AES-256 for private key encryption
https://bugzilla.mindrot.org/show_bug.cgi?id=1550 Summary: Move from 3DES to AES-256 for private key encryption Product: Portable OpenSSH Version: 5.1p1 Platform: All OS/Version: All Status: NEW Keywords: patch Severity: enhancement Priority: P2 Component: ssh-keygen AssignedTo:
2003 Aug 10
9
updated gssapi diff
this is the proposed gssapi diff against OpenSSH-current (non-portable). note: if this goes in, the old krb5 auth (ssh.com compatible) will be removed. please comment. jakob Index: auth.h =================================================================== RCS file: /home/hack/jakob/mycvs/sshgss/auth.h,v retrieving revision 1.1.1.2 retrieving revision 1.3 diff -u -r1.1.1.2 -r1.3 --- auth.h
2023 Apr 03
13
[Bug 3558] New: Spelling "yes" as "Yes" in sshd_config has a fatal result
https://bugzilla.mindrot.org/show_bug.cgi?id=3558 Bug ID: 3558 Summary: Spelling "yes" as "Yes" in sshd_config has a fatal result Product: Portable OpenSSH Version: 7.2p2 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component:
2004 Aug 23
2
[Bug 919] --disable-etc-default-login has no visible feedback
http://bugzilla.mindrot.org/show_bug.cgi?id=919 Summary: --disable-etc-default-login has no visible feedback Product: Portable OpenSSH Version: -current Platform: All OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-bugs at mindrot.org
2000 Mar 29
1
OpenSSH-1.2.3: return of ulimit problem
The ulimit problem appears to have reared its head again with openssh-1.2.3, under Red Hat Linux 6.1 (kernel-2.2.12, glibc-2.1.2, egcs-1.1.2, openssl-0.9.5, pam-0.68, pwdb-0.60): $ telnet localhost 22 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-1.5-OpenSSH-1.2.3 ^] telnet> quit Connection closed. $ ssh localhost Last login: Wed Mar 29
2002 Jul 01
5
[Bug 327] monitor_fdpass.c: Expected 1 got 1075033556 - Privilege Separation
http://bugzilla.mindrot.org/show_bug.cgi?id=327 ------- Additional Comments From jmknoble at pobox.com 2002-07-02 04:11 ------- Could you please check the error message again? Is it: mm_receive_fd: recvmsg: expected received 1 got nnnnnnnn or is it this: mm_receive_fd: expected type 1 got nnnnnnnn ? Those are two different problems, within a few lines of each other. The exact text