Call for testing: OpenSSH 7.7

[Tom G. Christensen]

On 25/03/18 01:29, Damien Miller wrote:
> On Sat, 24 Mar 2018, Tom G. Christensen wrote:
> >> Solaris does not ship with a printenv command.
> 
> sigh, it's printenv because:
> 
>> date: 2017/10/25 20:08:36;  author: millert;  state: Exp;  lines: +2 -2;  commitid: WvDhLxb5IsB9EQQZ;
>> Use printenv to test whether an SSH_USER_AUTH is set instead of
>> using $SSH_USER_AUTH.  The latter won't work with csh which treats
>> unknown variables as an error when expanding them.  OK markus@
> 
> Does replacing printenv with "env | grep SSH_AUTH_USER" work?
> 

Yes.

run test authinfo.sh ...
ExposeAuthInfo=no
ExposeAuthInfo=yes
ok authinfo

diff --git a/regress/authinfo.sh b/regress/authinfo.sh
index 9bd0a4d8..3caf8947 100644
--- a/regress/authinfo.sh
+++ b/regress/authinfo.sh
@@ -6,7 +6,7 @@ tid="authinfo"
  # Ensure the environment variable doesn't leak when ExposeAuthInfo=no.
  verbose "ExposeAuthInfo=no"
  env SSH_USER_AUTH=blah ${SSH} -F $OBJ/ssh_proxy x \
-       'printenv SSH_USER_AUTH >/dev/null' && fail "SSH_USER_AUTH present"
+       'env | grep SSH_USER_AUTH >/dev/null' && fail "SSH_USER_AUTH 
present"

  verbose "ExposeAuthInfo=yes"
  echo ExposeAuthInfo=yes >> $OBJ/sshd_proxy


However I need to correct myself since upon closer inspection I see that 
Solaris does have a printenv command but it's tucked away in /usr/ucb 
which is where the (deprecated) SunOS 4 compatible versions of various 
tools are put. I don't usually have this in my $PATH which is why I 
missed it.

-tgc