cvs commit: ports/security Makefile ports/security/ssh-copy-id Makefile pkg-descr ports/security/ssh-copy-id/files ssh-copy-id ssh-copy-id.1

[Doug Barton]

On 01/21/2011 04:04, Alexey Dokuchaev wrote:
> On Fri, Jan 21, 2011 at 12:10:04PM +0100, Emanuel Haupt wrote:
>> Max Khon<fjoe at samodelkin.net>  wrote:
>>> Alexey,
>>> 2011/1/20 Alexey Dokuchaev<danfe at freebsd.org>
>>> On Fri, Jan 14, 2011 at 05:32:37PM +0000, Emanuel Haupt wrote:
>>>>> ehaupt      2011-01-14 17:32:37 UTC
>>>>>
>>>>>    Modified files:
>>>>>      security             Makefile
>>>>>    Added files:
>>>>>      security/ssh-copy-id Makefile pkg-descr
>>>>>      security/ssh-copy-id/files ssh-copy-id ssh-copy-id.1
>>>>
>>>> What special functionality does this tool offer that goes beyond
>>>> simple copying/appending the key bu hand to ratify having it in the
>>>> ports?
>>>
>>> You need to enter password at least twice in order to place it to
>>> remote host manually: for copying the public key (or do it via
>>> clipboard) and for logging in in order to create .ssh directory (if
>>> it is missing) and append the key.
>>>
>>> I ended up with having similar script.
>>
>> ssh-copy-id is part of many linux distros and various documentations.
>> It's probably the best known script for that particular task (google
>> for ssh-copy-id).
>>
>> It's simplicity is by no means a reason for not adding it to the tree.
>
> This is very good explanation which answers all my questions.  :-)

Ahhhhhhhh .... peace and harmony breaking out all over the ports tree. 
It's a lovely thing to see. :)

> Thanks Emanuel.  Perhaps it should be mentioned in the the commit log
> so people like me would remain silent.

IMO pkg-descr might be a better choice. That way the information is 
easily available to everyone.


hth,

Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/