Zen

Source string Source string

By default, a privileged user named `core` is created on the Fedora CoreOS system, but it is not configured with a default password or SSH key. If you wish to use the `core` user, you must provide an Ignition config which includes a password and/or SSH key(s) for the `core` user. Alternatively you may create additional, new users via Ignition configs.
353/10000 · 353

The string is read-only.

English Actions
Configuring Users
Default User
By default, a privileged user named `core` is created on the Fedora CoreOS system, but it is not configured with a default password or SSH key. If you wish to use the `core` user, you must provide an Ignition config which includes a password and/or SSH key(s) for the `core` user. Alternatively you may create additional, new users via Ignition configs.
If you do not want to use Ignition to manage the default user's SSH key(s), you can make use of the https://coreos.github.io/afterburn/platforms/[Afterburn support] and provide an SSH key via your cloud provider.
Creating a New User
To create a new user (or users), add it to the `users` list of your Butane config. In the following example, the config creates two new usernames, but doesn't configure them to be especially useful.
variant: fcos
version: {butane-latest-stable-spec}
passwd:
users:
- name: jlebon
- name: miabbott
You will typically want to configure SSH keys or a password, in order to be able to log in as those users.
Using an SSH Key
To configure an SSH key for a local user, you can use a Butane config:
variant: fcos
version: {butane-latest-stable-spec}
passwd:
users:
- name: core
ssh_authorized_keys:
- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHn2eh...
- name: jlebon
ssh_authorized_keys:
- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDC5QFS...
- ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIveEaMRW...
- name: miabbott
ssh_authorized_keys:
- ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDTey7R...
Using File References to SSH Keys
Depending on the configuration variant and version you use, you can use local file references to SSH public keys instead of inlining them. The example from the xref:#_using_an_ssh_key[previous section] can thus be rewritten as follows:
variant: fcos
version: {butane-latest-stable-spec}
passwd:
users:
- name: core
ssh_authorized_keys_local:
- users/core/id_rsa.pub
- name: jlebon
ssh_authorized_keys_local:
- users/jlebon/id_rsa.pub
- users/jlebon/id_ed25519.pub
- name: miabbott
ssh_authorized_keys_local:
- users/miabbott/id_rsa.pub
You have to use `butane` with the `--files-dir` parameter to allow loading files from disk when converting to Ignition configurations for this to work.
Check the https://coreos.github.io/butane/specs/[Configuration specifications] for more details and which versions of your selected variant support it. Generally, each file may contain multiple SSH keys, one per line, and you may additionally specify inline `ssh_authorized_keys` as well as long as the SSH keys are unique.
SSH Key Locations
https://man.openbsd.org/sshd_config[sshd] uses a https://github.com/coreos/ssh-key-dir[helper program], specified via the `AuthorizedKeysCommand` directive, to read public keys from files in a user's `~/.ssh/authorized_keys.d` directory. The `AuthorizedKeysCommand` is tried after the usual `AuthorizedKeysFile` files (defaulting to `~/.ssh/authorized_keys`) and will not be executed if a matching key is found there. Key files in `~/.ssh/authorized_keys.d` are read in alphabetical order, ignoring dotfiles.

Loading…

No matching activity found.
Browse all string changes

Things to check

Unpluralised 1

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

9704889 String information

Source string description
type: Plain text
Flags
placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`", read-only
Source string location
./pages/authentication.adoc:6
String age
3 years ago
Last updated
a year ago
Source string age
3 years ago
Translation file
pot/master/pages/authentication.pot, string 3