Commit 69c75587 authored by Leigh Stoller's avatar Leigh Stoller

Fix the empty password on the user account we create on the dell

switches, I must have forgot to deal with it.

Basically, the FTOS manual says you can give it an MD5 or sha256 hash of
the password. Well, FTOS must come from another dimension, cause the MD5
and sha256 it generates, is different then what boss generates, for the
same input string. So that makes it hard to set up an account with a
password, unless I send over the cleartext. Which is okay, it stores it
internally as the hash (I cannot seem to generate). So we send over the
cleartext per-node root password that is regenerated for each time it is
allocated to an experiment. Not a big deal, we load the user's ssh keys,
they should not need to use passwords.
parent 1c2d994c
#!/usr/bin/perl -w
#
# Copyright (c) 2000-2018 University of Utah and the Flux Group.
# Copyright (c) 2000-2019 University of Utah and the Flux Group.
#
# {{{EMULAB-LICENSE
#
......@@ -444,8 +444,16 @@ sub DeviceReconfigure($$)
# is different (see above).
#
if ($nonlocal) {
#
# FTOS does not accept modular crypt strings. So just send it the
# cleartext password, it will not be visible. I should clarify; I
# cannot figure out how to give it an encrypted string. :-)
#
my $cleartext = $nodeobject->root_password();
@config = ("configure",
"username $uid nopassword privilege 15 role sysadmin",
"username $uid password 0 $cleartext ".
"privilege 15 role sysadmin",
"exit");
}
push(@config,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment