SCION VM Password
68 views
Skip to first unread message
Khlaid.dg
Mar 1, 2018, 3:02:00 AM3/1/18
to SCION community
Hello,
I have installed the SCION VM using the steps mentioned on the SCION tutorial website (https://netsec-ethz.github.io/scion-tutorials/virtual_machine_setup/dynamic_ip/)
After installation the VM asks for a password when trying to login through ssh, what is this password?
Thanks,
Khalid
David Hausheer
Mar 1, 2018, 6:49:53 AM3/1/18
to SCION community
Hi Khalid
thank you for your interest in SCION!
After installation of your VM with "vagrant up" you should be able to login with "vagrant ssh" (without a password). Once you are inside the VM you can set or change the password with "passwd". This will then allow you to login to the VM with a regular ssh client.
P.S. Please note that this week we are upgrading SCIONLab to a new release. Depending on when you created your account, you may or may not have received the respective information. We expect the new release to be available in a few days. You will then have to download a new VM configuration again. My apologies for the troubles as you are catching us right in the middle of the migration phase.
Kind regards
David
thank you for your interest in SCION!
After installation of your VM with "vagrant up" you should be able to login with "vagrant ssh" (without a password). Once you are inside the VM you can set or change the password with "passwd". This will then allow you to login to the VM with a regular ssh client.
P.S. Please note that this week we are upgrading SCIONLab to a new release. Depending on when you created your account, you may or may not have received the respective information. We expect the new release to be available in a few days. You will then have to download a new VM configuration again. My apologies for the troubles as you are catching us right in the middle of the migration phase.
Kind regards
David
Khlaid.dg
Mar 1, 2018, 7:47:27 AM3/1/18
to SCION community
Hi David,
Thank you for the reply,
The VM asks for a password when I issue the "vagrant ssh" command for the first time. I have created my account a week ago and downloaded the files last Thursday (22/2) could it be because of the updates happening at the moment?
David Hausheer
Mar 1, 2018, 9:54:14 AM3/1/18
to SCION community
Hi Khalid
I am afraid the SCIONLab VM is configured to allow only private key authentication. What does "vagrant ssh-config" and "vagrant ssh --debug" show?
Best,
David
I am afraid the SCIONLab VM is configured to allow only private key authentication. What does "vagrant ssh-config" and "vagrant ssh --debug" show?
Best,
David
Khlaid.dg
Mar 7, 2018, 5:03:27 PM3/7/18
to SCION community
Hi David,
And please find the output of "vagrant ssh --debug" is attached in the text file.
Here is the output of vagrant ssh-config
D:\SCION\kaldughayem@gmail.com>vagrant
ssh-configHost default
HostName 127.0.0.1
User ubuntu
Port 2222
UserKnownHostsFile /dev/null
StrictHostKeyChecking no
PasswordAuthentication no
IdentityFile D:/SCION/kaldughayem@gmail.com/.vagrant/machines/default/virtualbox/private_key
IdentitiesOnly yes
LogLevel FATAL
I think I should mention that I am running VirtualBox and Vagrant on a machine running the latest version of Windows 10.
Thank you for your help.
David Hausheer
Mar 7, 2018, 6:28:08 PM3/7/18
to SCION community
Hi Khalid
it checked it and compared it with my configuration. I can't see anything unusual. It looks like something went wrong during the setup of the vagrant box. We have now the beta version of the new release up, so you can create and download a new SCIONLab VM: https://scion-ad6.inf.ethz.ch/ Hopefully this will fix the problem.
Best regards
David
it checked it and compared it with my configuration. I can't see anything unusual. It looks like something went wrong during the setup of the vagrant box. We have now the beta version of the new release up, so you can create and download a new SCIONLab VM: https://scion-ad6.inf.ethz.ch/ Hopefully this will fix the problem.
Best regards
David
Khlaid.dg
Mar 8, 2018, 8:04:56 AM3/8/18
to SCION community
Hi David,
I downloaded the new version, removed the old box and installed the new one, but I am still being asked for the password to ssh to the VM.
I noticed the output in the screenshot attached when running the "vagrant up" command, the part where it says: " default: SSH auth method: password"
I am trying to find a way to change that, but I cannot find a solution online which works for my case.
David Hausheer
Mar 8, 2018, 12:40:46 PM3/8/18
to SCION community
Hi Khalid,
Is this the output of the very first boot of the VM with "vagrant up" or a subsequent boot? It looks like a subsequent boot, as your output says "Machine already provisioned."
During the first boot, the public key should have been inserted, showing the following output:
In your case it appears that this was not done and hence the login fails. At this stage, I suggest to destroy your VM again with "vagrant destroy" and then to create it again with "vagrant up" and observe if the public key is inserted during the first boot. You may also run "vagrant up --debug" during the first boot to observe in detail what is happening.
Best regards
David
Is this the output of the very first boot of the VM with "vagrant up" or a subsequent boot? It looks like a subsequent boot, as your output says "Machine already provisioned."
During the first boot, the public key should have been inserted, showing the following output:
default: SSH username: ubuntu
default: SSH auth method: password
default: Warning: Connection aborted. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Connection aborted. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Connection aborted. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Authentication failure. Retrying...
default:
default: Inserting generated public key within guest...
default: Removing insecure key from the guest if it's present...
default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!In your case it appears that this was not done and hence the login fails. At this stage, I suggest to destroy your VM again with "vagrant destroy" and then to create it again with "vagrant up" and observe if the public key is inserted during the first boot. You may also run "vagrant up --debug" during the first boot to observe in detail what is happening.
Best regards
David
Khlaid.dg
Mar 10, 2018, 8:51:10 AM3/10/18
to SCION community
Hi David,
This is the output of the the first "vagrant up" (attached in the txt file), and it shows that it inserted the key into the machine:
After that the command "vagrant ssh" asks for a password.
Thanks and regards,
Khalid
Khlaid.dg
Mar 11, 2018, 9:54:19 AM3/11/18
to SCION community
Hello,
The problem is fixed, I think it was because the VM files were in the D:\ drive, I destroyed and deleted the VM and moved the files to the C:\ drive after that I was able to ssh into the VM with the private key authentication.
Thank you for all the help I really appreciate it,
Khalid
On Thursday, March 1, 2018 at 9:02:00 AM UTC+1, Khlaid.dg wrote:
David Hausheer
Mar 12, 2018, 6:10:05 PM3/12/18
to SCION community
Hi Khalid
I am glad that it works now. Although in my case I have had VMs in the D:\ drive too, and that was working for me as well.
Best regards
David
I am glad that it works now. Although in my case I have had VMs in the D:\ drive too, and that was working for me as well.
Best regards
David
Khalid.dg
Mar 14, 2018, 10:38:10 AM3/14/18
to SCION community
Oh sorry, what was going on is that I had my Vagrant files in the D:\ drive and the VM files (VirtualBox files) in the C:\ drive, when I re-downloaded the Vagrant configurations files from the SCIONLab website and placed them in the C:\drive. I rebuilt the VM using the "vagrant up" command and I was able to access the VM using public key authentication
Reply all
Reply to author
Forward
0 new messages