Bit tired of openssh's bugs i did this ebuild... It probably needs some tweeks and i have no idea how it works on non x86 machines (will try on ppc tomorow) Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 18225 [details] tar.gz with the ebuild and some other files
This is just great! I was concerned when I found out gentoo hadnt any ebuild already for ssh.com's ssh (like FreeBSD ports has). I would be nice to have the option to install ssh1 too from ssh.com. Thanks!
Created attachment 18265 [details] new ebuild that uses PROVIDE
Created attachment 18266 [details] openssh-3.7.1_p2-r1.ebuild with provide
These two new ebuilds come with PROVIDE="virtual/ssh" this way they dont end up erasing each others files. For this two work virtual/ssh needs to be added to the virtuals list.
At my university i have a QOS system that gives very low priority when accessing "untrested" remote ports, and ssh is marked as trusted. So i was looking at a way to connect to my home/office machine and have net from there. First i tought of a socks5 server at home/office and and do a ssh -L 1080:127.0.0.1:1080 -C humpback@home . But the machines are already have alot of services and having a socks5 server running all the time to use once or twice (or less) a day did not appeal much to me.... Then i found that ssh from ssh.com already did this, from the manpage: [copy] -L [protocol/][localhost:]port:host:hostport or -L socks/[localhost:]port ...... With socks, the ssh2 client will act as a SOCKS server for other applications, creating forwards as requested by the SOCKS transaction. This supports both SOCKS4 and SOCKS5. [copy] And this was just what i needed. That and having upgraded openssh some two or three times in the last week made me change imediatly.
*** Bug 4959 has been marked as a duplicate of this bug. ***
ok, i've added net-misc/ssh to portage ... heres the summation of the changes i added: removed all the warning's about openssh overwriting: ssh now has a blocker against virtual/ssh unless the user puts 'openssh' into their USE ... and if they have 'openssh' in their USE i delete all the symlinks generated by the install phase ... that way users can have both packages if they really want it while still being able to do a 1 virtual thing removed all the warning's about regenerating keys: in the install phase i check to see whether the keys already exist on the host system, and if they do, i install them into ${D}. the make file does a check on the existence of the keys and will skip the generation phase if they already exist ... plus this way the keys will stay static from the first emerge i already updated the openssh ebuild to provide virtual/ssh and i setup the virtuals in x86 profiles. that leaves me to go through and update ebuilds that DEPEND on net-misc/openssh and to update the other arch's
I had to re-emerge openssh now to prevent commercial ssh from installing in a world upgrade (TOGETHER with keeping openssh).
your bug is related to a typo i made and fixed in cvs
alright, i added the virtuals and updated some packages i could verify ... i guess in the future if you find a package is forcing you to use openssh but you can verify it works just fine with this ssh i'll switch it over to the virtual ;)
Found this yesterday when I was about to create my own ebuild for ssh.com. I quickly switched my five Gentoo boxes over to it, including my Sparc Ultra 1. The steps I used are as follows: 1. emerge unmerge openssh 2. ACCEPT_KEYWORDS="~x86" emerge -vp net-misc/ssh (I had to use this command on my Sparc as well. The ebuild only has "~x86" for keywords.) 3. rc-update del sshd default 4. rc-update add sshd2 default 5. /etc/init.d/sshd stop 6. /etc/init.d/sshd2 start I then had to recreate all my ssh keys and known_hosts files. A pain, but it is worth it! Great work guys.
