Re: Bug#655230: ITP: pushkey -- ITP: pushkey - Pushes your ssh key to a remote location. It tries to create a .ssh folder remotley then it adds your ssh key to authorized_keys.
jI have uploaded the correct package now including the debian source. They are located here:
This might seem trivial but it helped enough people I work with that I thought I should contribute the code. Instead of running "ssh-copy-id -i identityName IPADDR" , all you had to do was "pushkey IPADDR". The difference between my package and ssh-copy-id is that my package sets the permission on the folder and file and it also gives you the option to create new ssh key keys if it doesn't find it. ssh-copy-id does not have the ability to create the .ssh folder remotely nor does it change the permissions. And you had to explicitly specify which key to use in ssh-copy-id. I use pushkey on many other distro's too so I thought it might be something beneficial that can be ported over easily.
As for the gentlemen in the previous email 'Arno Töll' the packaged you looked at was the old one I accidentally added wrong one. The new one does not prompt for password twice
Again sorry guys for dropping the ball on this one. It is my first attempt and I screwed that up..
On Mon, Jan 9, 2012 at 11:08 AM, Al <email@example.com>
I'm sorry you guys feel like I am wasting your time as I had no intention of doing that. As your probably aware this is my first time I am submitting an ITP so I am new to the whole process.
I did not know I submitted the ITP twice. The reportbug application crashed with a segfault warning so I assumed it did not go through. To make things worse I noticed I have uploaded the wrong deb package as this is an old one (sigh). I realize that there is ssh-copy-id but I thought to include my package b/c it had extra abilities to create keys and also fix permissions on folder and files. I hope you all will allow me the opportunity to submit the correct deb package (including the source). I would like to know where I can submit it as I am assuming not on this email thread.
On Mon, Jan 9, 2012 at 10:15 AM, Ansgar Burchardt <firstname.lastname@example.org>
On 01/09/2012 03:43 PM, Al Biheiri wrote:
Description : Pushes your ssh key to a remote location. It tries to
create a .ssh folder remotley then it adds your ssh key to authorized_keys.
What does pushkey do that ssh-copy-id cannot?
I also don't think we need yet another package for a tiny script that (in short) only does
ssh $REM_HOST "umask 077; test -d .ssh || mkdir .ssh; chmod 700 .ssh ; echo $VAL >> .ssh/authorized_keys; chmod 600 .ssh/*" || exit 1