Yes, glad to hear the solution was found. It *sounds* like this may be
directly related to the fact that vagrant-dspace is now using Ubuntu
16.04LTS, which uses OpenSSH 7.0. For those who haven't yet discovered,
OpenSSH 7 *disallows* DSA keys by default:
http://viryagroup.com/what-we-do/our-blog-posts/hosting-and-linux-server-managment-blog/ssh-keys-failing-in-ubuntu-16-04-xenial-with-permission-denied-publickey
So, if others are hitting this issue, you should make sure you are using
an *RSA* SSH Key
BTW, Hardy or Andrea, could you post an updated note to the
vagrant-dspace setup/installation instructions about this? It sounds
like it may be something worth noting in the README at
https://github.com/DSpace/vagrant-dspace
- Tim
On 11/20/2016 5:02 PM, Andrea Schweer wrote:
Hi Hardy, all,
On 11/19/2016 06:49 AM, Hardy Pottinger wrote:
OK, here's a shot in the dark, and it will require you taking a leap
back as it were, if in addition to destroying your vagrant
environment you also delete the box image Vagrant has cached away for
you:
in your Vagrant-DSpace folder, run:
vagrant box remove box-cutter/ubuntu1604
vagrant destroy -f
Same behaviour as before :( Vagrant 1.8.5, vagrant-vbguest installed,
running on Ubuntu 16.04 with ssh agent that has a key in it that lets
it pull from DSpace/DSpace via git.
When I vagrant ssh to the box, I see the ssh key (via ssh-add -L).
ssh -T -oStrictHostKeyChecking=no [email protected]
still gets
Permission denied (publickey).
Same command on the host gets
Hi [username]! You've successfully authenticated, but GitHub does not
provide shell access.
Aha -- I may have solved the mystery? My key is an old one (dsa). On
the host, my ssh config has
Host github.com
PubkeyAcceptedKeyTypes +ssh-dss
When I add that on the vagrant box, I get the successful auth message
just like on the host.
So, I then generated an rsa key and added that to my github profile +
the ssh agent on the host. This does indeed get me past the ssh
problem, and through to a successful vagrant up - yay! I guess the
alternative to generating a new key would be to make sure the ssh
config option ends up on the vagrant box.
[I still need to work out how to build the 5.x branch but I'm guessing
the problems I ran into there are from the build.properties ->
local.cfg change.]
cheers,
Andrea
--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
You received this message because you are subscribed to the Google Groups "DSpace
Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
