fedora-docs-l10n/fedora-coreos/master/pages/authentication — French @ Fedora Weblate: variant: fcos version: {butane-latest-stable-spec} passwd: users: - name: jlebon

Translation

Source change

English type: delimited block -

French

Needs editing

Skip

	English	French	Actions
	Configuring Users	Configuration des utilisateurs
	Default User	Utilisateur par défaut
	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.	Par défaut, un utilisateur privilégié nommé `core` est créé sur un système Fedora CoreOS, mais aucun mot de passe ou clé SSH ne lui est associé. Si vous souhaitez utiliser l'utilisateur `core`, vous devez créer une configuration Ignition qui inclue un mot de passe ou une (ou plusieurs) clés SSH pour cet utilisateur. Vous pouvez aussi créer d'autres utilisateurs à l'aide de la configuration Ignition.
	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	Création d'un nouvel utilisateur
	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.	Pour créer un ou plusieurs nouveaux utilisateurs, ajoutez les à la liste `users` dans votre fichier de configuration Butane. Dans l'exemple suivant, la configuration crée deux nouveaux utilisateurs sans ajouter d'autre configuration ou d'usage défini.
	variant: fcos version: {butane-latest-stable-spec} passwd: users: - name: jlebon - name: miabbott	variant: fcos version: 1.4.0 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.	Il est généralement souhaitable de configurer une clé SSH ou un mot de passe pour pouvoir se connecter avec ces utilisateurs.
	Using an SSH Key	Utilisation d'une clé SSH
	To configure an SSH key for a local user, you can use a Butane config:	La configuration d'une clé SSH pour un utilisateur local peut être réalisé avec la configuration Butane suivante :
	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...	variant: fcos version: 1.4.0 passwd: users: - name: core ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHn2eh... - name: jlebon ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDC5QFS... - sh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIveEaMRW... - name: miabbott ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDTey7R...
	Using File References to SSH Keys	Utilisation d'une clé SSH
	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	variant: fcos version: 1.4.0 passwd: users: - name: core ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHn2eh... - name: jlebon ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDC5QFS... - sh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIIveEaMRW... - name: miabbott ssh_authorized_keys: - ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAACAQDTey7R...
	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	Emplacement des clés SSH
	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.	sshd utilise l'outil https://github.com/coreos/ssh-key-dir[ssh-key-dir] pour lire les clés publiques contenues dans le dossier utilisateur `~/.ssh/authorized_keys.d`. Les fichiers de clés sont lus dans l'ordre alphabétique, en ignorant ceux commençant par un point. Le fichier classique `~/.ssh/authorized_keys` est lu en dernier. Pour débuguer la lecture du `~/.ssh/authorized_keys.d`, exécutez manuellement l'outil `ssh-key-dir` et observez la sortie standard :
	Ignition writes configured SSH keys to `~/.ssh/authorized_keys.d/ignition`. On platforms where SSH keys can be configured at the platform level, such as AWS, Afterburn writes those keys to `~/.ssh/authorized_keys.d/afterburn`.	Ignition enregistre les clés SSH dans `~/.ssh/authorized_keys.d/ignition`. Pour les plateformes sur lequel les clés SSH peuvent être directement configurées, comme AWS, Afterburn enregistrera ces clés dans `~/.ssh/authorized_keys.d/afterburn`.
	To debug the reading of `~/.ssh/authorized_keys.d`, manually run the helper program and inspect its output:
	/usr/libexec/ssh-key-dir	/usr/libexec/ssh-key-dir
	To view and validate the effective configuration for sshd, two test modes (`-t`, `-T`) are available as documented on the https://man.openbsd.org/sshd[manual pages].

Loading…

None

String updated in the repository

English

French 86 characters edited Current translation Needs editing

2 months ago

None

Source string changed

English 27 characters edited

2 months ago

Browse all string changes

Things to check

Punctuation spacing

Missing non breakable space before double punctuation sign

Fix string

Reset

Glossary

English	French
Butane		fedora-docs-l10n/fedora-coreos

String information

Source string description

type: delimited block -

Flags

no-wrap, placeholders:r"`[\w.\/\-_=@&*:$●+~()\] ]*`"

Source string location

pages/authentication.adoc:21

String age

2 months ago

Last updated

2 months ago

Source string age

2 months ago

Translation file

po/fr/master/pages/authentication.po, string 7