HomeSort by: relevance | last modified time | path
    Searched refs:SSH (Results 1 - 5 of 5) sorted by relevancy

  /src/external/bsd/am-utils/dist/
cvs-server.txt 4 (1) Get an SSH Public key installed on cvs.am-utils.org. You can generate a
5 public/private key pair using ssh-keygen(1). Then copy the key into
6 your ~/.ssh/authorized_keys file on cvs.am-utils.org. If you don't have
12 $ export CVS_RSH=ssh
25 setting CVS_RSH=ssh in your environment (or put it in your
  /src/external/gpl3/gcc/dist/maintainer-scripts/
gcc_release 400 ${SSH} -l ${GCC_USERNAME} ${GCC_HOSTNAME} \
618 SSH="${SSH:-ssh}"
732 GITROOT="git+ssh://${GIT_USERNAME}@${GIT_SERVER}${GIT_REPOSITORY}"
  /src/external/gpl3/gcc.old/dist/maintainer-scripts/
gcc_release 400 ${SSH} -l ${GCC_USERNAME} ${GCC_HOSTNAME} \
618 SSH="${SSH:-ssh}"
732 GITROOT="git+ssh://${GIT_USERNAME}@${GIT_SERVER}${GIT_REPOSITORY}"
  /src/external/gpl2/xcvs/dist/contrib/
cvs_acls.in 191 Tested these restrictions with concurrent use of pserver and SSH
207 Need to deal with pserver/SSH transition with conflicting umasks?
280 planning to move from pserver to SSH access at some later point in time.
282 CVSROOT=:ext:<userId>..., users can switch over to SSH access without
284 SSH, the inherently insecure xinetd cvspserver process can be disabled.
287 :TODO: The only potential glitch with the SSH approach is the possibility
289 another, especially during a transition from pserver to SSH. As noted
  /src/crypto/external/apache2/openssl/dist/providers/fips/
self_test_data.inc 615 * According to FIPS 140-3 10.3.A Note18: SSH KDF is not required, since it is

Completed in 26 milliseconds