Displaying 4 results from an estimated 4 matches for "sshd_proxy_bak".
2024 May 21
2
[Bug 3692] New: rekey.sh doesn't actually test different algorithms
...is a function ssh_data_rekeying(). It sets the first
parameter as _kexopt but then 2 lines later tests _kexopts - note the
trailing "s":
ssh_data_rekeying()
{
_kexopt=$1 ; shift
_opts="$@"
if ! test -z "$_kexopts" ; then
cp $OBJ/sshd_proxy_bak $OBJ/sshd_proxy
echo "$_kexopt" >> $OBJ/sshd_proxy
_opts="$_opts -o$_kexopt"
fi
This means that the various algorithms never are set and so it tests
the same default algorithm over and over.
--
You are receiving this mail because:...
2011 Jan 05
0
[PATCH] fix %n expansion in LocalCommand
...e \
cert-hostkey \
- cert-userkey
+ cert-userkey \
+ host-expand
INTEROP_TESTS= putty-transfer putty-ciphers putty-kex conch-ciphers
#INTEROP_TESTS+=ssh-com ssh-com-client ssh-com-keygen ssh-com-sftp
@@ -75,7 +76,8 @@ CLEANFILES= t2.out t6.out1 t6.out2 t7.out t7.out.pub copy.1 copy.2 \
sshd_proxy_bak rsa_ssh2_cr.prv rsa_ssh2_crnl.prv \
known_hosts-cert host_ca_key* cert_host_key* \
putty.rsa2 sshd_proxy_orig \
- authorized_principals_${USER}
+ authorized_principals_${USER} \
+ expect actual
# Enable all malloc(3) randomisations and checks
TEST_ENV= "MALLOC_OPTIONS=AFGJPRX...
2011 Jan 07
1
[RFC/PATCH] ssh: config directive to modify the local environment
...a5..b5724f8 100644
--- a/regress/Makefile
+++ b/regress/Makefile
@@ -51,6 +51,7 @@ LTESTS= connect \
cfgmatch \
addrmatch \
localcommand \
+ localenvmod \
forcecommand \
portnum \
keytype \
@@ -76,7 +77,8 @@ CLEANFILES= t2.out t6.out1 t6.out2 t7.out t7.out.pub copy.1 copy.2 \
sshd_proxy_bak rsa_ssh2_cr.prv rsa_ssh2_crnl.prv \
known_hosts-cert host_ca_key* cert_host_key* \
putty.rsa2 sshd_proxy_orig \
- authorized_principals_${USER} expect actual
+ authorized_principals_${USER} expect actual \
+ localenvmods.in localenvmods.expect localenvmods.out ssh_proxy.tmpl
# Enable al...
2020 Jul 21
11
[RFC PATCH 0/4] PAM module for ssh-agent user authentication
Hi,
The main (and probably the only) use case of this PAM module is to let
sudo authenticate users via their ssh-agent, therefore without having
to type any password and without being tempted to use the NOPASSWD sudo
option for such convenience.
The principle is originally implemented by an existing module [0][1]
and many pages that explain how to use it for such purpose can be
found online.