openpkg
/
openpkg-packages
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2081 Commits
1 Branch
2 Tags
594 MiB
 
 
 
 
 
 
Tree: e2524a1568
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e2524a1568'
${ noResults }
openpkg-packages/openssh
Dr. Ralf S. Engelschall bd832a4bd0
add quaterly brain-dead chroot support (dedicated to Thomas Rohde) 		24 years ago
..
fakesyslog.tar.gz enhance fakesyslog for Tru64 compatibility 24 years ago
openssh.spec add quaterly brain-dead chroot support (dedicated to Thomas Rohde) 24 years ago
rc.openssh Switch to l_{s,m,r,n}{usr,grp}. 24 years ago
ssh-askpass
…
ssh-keyman overhaul ssh-keyman by addressing recently popped up issues 24 years ago
ssh-keyman.1 include my ssh-keyman utility 24 years ago
ssh-keyman.pod include my ssh-keyman utility 24 years ago
ssh_config - create SSHv2 RSA in addition to SSHv1 RSA server key - generate server keys with 2048 bits instead of 1024 - create ~/.ssh/agent file with mode 600 instead of mode 700 - cleanup ssh_config and sshd_config files - default to "Protocol 2,1" in server and "Protocol 1,2" in client 24 years ago
sshd_config After longer thinking and comparing what FreeBSD and NetBSD did, finally revert to the old state by kicking out the UsePrivilegeSeparation and Compression default value guessing because: 1. we are predestined to fail in general because we cannot do it correctly by just looking at the platform id. 2. UsePrivilegeSeparation is nice from a paranoid security point of view but OTOH really is too brand-new and internally limits or even breaks the OpenSSH functionality too dramatically. People who are paranoid enough and can live with this can feel free to change the "no" to a "yes" in their sshd_config easily. 3. it is nasty to have a package "openssh" shipping with totally different default configuration (using "UsePrivilegeSeparation yes" makes a large difference under run-time!) on different platforms. This is nasty and we really want a single default config independent of a platform. So, unless "UsePrivilegeSeparation yes" works equally on all our plaforms and without such dramatical restrictions (Compression, PAM, etc) and internal brokeness we will stay with the _default_ config of "UsePrivilegeSeparation no". Once Privilege Separation is really ready for a global deployment, we are happy to enable it by default again. 24 years ago