[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#365884: openssh-client: please offer the possibility to execute a shell command before initiating the connection



Package: openssh-client
Version: 1:4.2p1-8
Severity: wishlist
Tags: upstream

Hi,

in port knocking setups, it would be great to have the possibility to
execute a shell command before the ssh connection is actually
initiated. That way, one could configure ssh like

host foo
hostname foo.bar.example
user baz
pre-connect knock foo.bar.example 1234 5678

and transparently initiate the connection by saying ssh foo. ssh would
then first invoke the knock process and then initiate the actual ssh
connection.

If this is already possible without wrapping the ssh client, the
documentation is too well hidden.

Greetings
Marc

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16.13-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages openssh-client depends on:
ii  adduser       3.87                       Add and remove users and groups
ii  debconf [debc 1.5.0                      Debian configuration management sy
ii  dpkg          1.13.18                    package maintenance system for Deb
ii  libc6         2.3.6-7                    GNU C Library: Shared libraries
ii  libcomerr2    1.38+1.39-WIP-2006.04.09-1 common error description library
ii  libedit2      2.9.cvs.20050518-2.2       BSD editline and history libraries
ii  libkrb53      1.4.3-7                    MIT Kerberos runtime libraries
ii  libncurses5   5.5-2                      Shared libraries for terminal hand
ii  libselinux1   1.30-1                     SELinux shared libraries
ii  libssl0.9.8   0.9.8a-8                   SSL shared libraries
ii  zlib1g        1:1.2.3-11                 compression library - runtime

openssh-client recommends no packages.

-- no debconf information




Reply to: