On 04/13/2016 05:39 PM, Rick Stevens wrote:
> On 04/13/2016 01:04 PM, Tom Horsley wrote:
>> On Wed, 13 Apr 2016 15:51:31 -0400
>> Richard Heck wrote:
>>
>>> Any suggestions?
>>
>> Yep. The security geeks decided dsa keys weren't secure,
>> but none of the errors messages you get give you a hint
>>
On 04/13/2016 01:04 PM, Tom Horsley wrote:
On Wed, 13 Apr 2016 15:51:31 -0400
Richard Heck wrote:
Any suggestions?
Yep. The security geeks decided dsa keys weren't secure,
but none of the errors messages you get give you a hint
that dsa keys no longer work.
You can change a lot of obscure pa
On 04/13/2016 01:04 PM, Tom Horsley wrote:
The security geeks decided dsa keys weren't secure
Do you mean "the security experts who maintain OpenSSH and OpenBSD?"
http://www.openssh.com/txt/release-7.0
But, yeah, the release notes are light on details.
I recommend this document to SSH users:
On Wed, 13 Apr 2016 15:51:31 -0400
Richard Heck wrote:
> Any suggestions?
Yep. The security geeks decided dsa keys weren't secure,
but none of the errors messages you get give you a hint
that dsa keys no longer work.
You can change a lot of obscure parameters in /etc/sshd.config
(and maybe /etc/
I've googled around for this and found some similar complaints, but none
of the solutions mentioned in these threads works for me. So I'm asking
here.
With F22 on the same machine, my normal routine would be:
> ssh-add
Enter passphrase for /home/me/.ssh/id_dsa:
Identity added: /home/me/.ssh/id_d
