Closed
Bug 922355
Opened 11 years ago
Closed 11 years ago
need public key on app1
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bcolloran, Assigned: rbryce)
Details
Attachments
(2 files)
need to publish some protected content on app1, so i need my public key on there.
Comment 1•11 years ago
|
||
Brendan,
What's the FQDN of the machine? app1.?
Comment 3•11 years ago
|
||
(In reply to brendan c from comment #2)
> sorry, it's app1.metrics.scl3.mozilla.com
Cool.
Pedro, ack?
Flags: needinfo?(palves)
Assignee | ||
Comment 5•11 years ago
|
||
(In reply to brendan c from comment #0)
> Created attachment 812280 [details]
> SSH-2-DSA-public
>
> need to publish some protected content on app1, so i need my public key on
> there.
We can not add your DSA ssh_key. Opsec requires RSA keys.
Opsec recommends the following settings when generating a new key:
ssh-keygen -t rsa -b 2048
Flags: needinfo?(bcolloran)
(In reply to brendan c from comment #6)
> Created attachment 812734 [details]
> id_rsa.pub
lmk if this doesn't work for some reason. thanks!!
Assignee | ||
Comment 8•11 years ago
|
||
I added you new key to ldap and realized it on app1.metrics.scl3.m.c. I noticed you have another ssh_key applied to your account that is not the key you posted in Comment 0. You can certainly have multiple ssh_keys, just wanted you to be aware there are now 2 ssh_keys on your ldap account. If one can be removed please let me know.
Info: Applying configuration version '76023'
Notice: /Stage[main]/Ldap_users::Com/Ssh_authorized_key[bcolloran_gen_1]/ensure: created
Notice: /Stage[main]/Ldap_users::Com/Ssh_authorized_key[bcolloran_gen_2]/ensure: created
Assignee: server-ops → rbryce
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•