Public bug reported:
https://github.com/hercules-team/augeas/issues/191
Augaes 1.3 can't read certain ssl.conf files, such as one of the ones Let's
Encrypt uses: https://github.com/letsencrypt/letsencrypt/issues/981
versions 1.2 and 1.4 of augaes don't have this problem, but currently vivid and
I agree with Eric and cloudcontrol, for CNAMEs being the correct
solution.
In the meantime, there's a problem with using any debian package from
within ec2 instances - you can't contact the repository to install any
packages, so using a package to fix the problem presents something of a
putty (0.60-3) fails with the same error (too many authentication
errors).
putty is not configured at all on this machine so it should be in passwd
auth mode. However, ss soon as I put in my login name it comes up with
the error.
--
openssh public key auth broken if one has many keys but only
workaround/fix:
- move all keys into subdirectories and update config to reflect changes.
- even with multiple keys in subdirectories it does not try the wrong keys.
hypothesis:
- the ssh client looks in ~/.ssh and tries any files it deems to be keys, even
when 'config' is configured explicitly
Public bug reported:
Binary package hint: openssh-client
After upgrading from 8.04 to 8.10, I could not log into any machines via
ssh where I had already configured public-key auth. This happens with
both rsa and dsa keys.
The error given was:
Received disconnect from 10.0.0.1: 2: Too many
for more information.
/quote
Hm... I kind of like that, actually :)
Does anyone feel like forwarding this suggestion to Debian?
--
Noah Slater, http://bytesexual.org/nslater
--
Apache2 default site contains only the words It works!
https://bugs.launchpad.net/bugs/89364
You received
