[Starlingx-discuss] Re-branding wrsroot proposal
shuicheng.lin at intel.com
Sat May 11 01:56:22 UTC 2019
The initial password "wrsroot" is defined in file: stx-integ/config-files/sudo-config/centos/sudo-config.spec
%define WRSROOT_P N8LRObqPlSGUc
And it is generated by cmd: openssl passwd wrsroot
In case you want to change this password to "sysadmin", you just need run "openssl passwd sysadmin", and update "WRSROOT_P" with the new value.
From: Saul Wold [mailto:sgw at linux.intel.com]
Sent: Friday, May 10, 2019 12:20 PM
To: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Re-branding wrsroot proposal
I did my first pass and rebuild my ISO today, and I realized another item that needs tobe addressed, the sysadmin password! I vaugely remember seeing the encoded entry someplace and now of course I can't find it again.
If someone can point me to the location, I will apply a change there as well.
Good news is so far, I can boot and login to the C-0 node with sysadmin/old password.
Thanks in advance!
On 5/8/19 10:16 AM, Saul Wold wrote:
> We seem to be landing on "sysadmin" and I started to look at the
> changes, I forgot to point out we also needed to change the
> wrs_protected group name.
> I suggest that we go with 'sys_protected' as the groupname unless
> there are other suggestions.
> I will bring this up in tomorrow's TSC meeting so we can get it
> changed soon.
> Thanks for all of your input.
> On 5/3/19 3:28 PM, Saul Wold wrote:
>> We talked about some of the branding changes at the PTG just now and
>> one item to try and tackle now for this release would be changing
>> wrsroot to some alternative.
>> This will be a pretty mechanical change, it will touch the integ,
>> config, metal, and update repos. There might be a couple places where
>> this can be placed in a variable or parameter. There is currently a
>> storyboard titled "Change wrsroot to stxuser" . There was some
>> initial discussion at the PTG regarding the new user name. We want to
>> avoid stx, or starlingx and "root", in the name it should remain more
>> One obvious choice is:
>> Please reply with additional suggestions before next week's TSC (5/9).
>> Ultimately, this change will require changes to tests, test
>> frameworks, scripts (such as deployment tools) and documentation.
>>  https://storyboard.openstack.org/#!/story/2004716
>> Thanks for your input.
>> Starlingx-discuss mailing list
>> Starlingx-discuss at lists.starlingx.io
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
More information about the Starlingx-discuss