|
|
19.
|
|
|
The create-key command creates a cryptographic key pair that can be
used for signing assertions.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
Der Befehl »create-key« erstellt ein kryptografisches Schlüsselpaar, das zum
Unterschreiben von Zusicherungen verwendet wird.
|
|
|
Suggested by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_create_key.go:41
|
|
|
20.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
|
Translated by
schuko24
|
|
Reviewed by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_create_user.go:33
|
|
|
21.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
|
Translated by
schuko24
|
|
Reviewed by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_debug.go:29
|
|
|
22.
|
|
|
The delete-key command deletes the local cryptographic key pair with
the given name.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
Der Befehl »delete-key« löscht das lokale kryptografische Schlüsselpaar mit
dem angegebenen Namen.
|
|
|
Suggested by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_delete_key.go:41
|
|
|
23.
|
|
|
The disable command disables a snap. The binaries and services of the
snap will no longer be available, but all the data is still available
and the snap can easily be enabled again.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
Der Befehl »disable« deaktiviert einen Snap. Die Binärdateien und Dienste des
Snaps sind nicht mehr verfügbar, alle Daten sind aber noch vorhanden. Der Snap
kann daher einfach wieder aktiviert werden.
|
|
|
Suggested by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:119
|
|
|
24.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
|
Translated and reviewed by
Dennis Baudys
|
|
|
|
Located in
cmd/snap/cmd_disconnect.go:41
|
|
|
25.
|
|
|
The download command downloads the given snap and its supporting assertions
to the current directory with .snap and .assert file extensions, respectively.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
Der Befehl »download« lädt den gegebenen Snap und seine unterstützenden Zusicherungen
in das aktuelle Verzeichnis mit den Dateierweiterungen .snap bzw. .sert herunter.
|
|
|
Suggested by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_download.go:51
|
|
|
26.
|
|
|
The enable command enables a snap that was previously disabled.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
Der Befehl »enable« aktiviert einen Snap, der zuvor deaktiviert wurde.
|
|
Translated by
schuko24
|
|
Reviewed by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:115
|
|
|
27.
|
|
|
The export-key command exports a public key assertion body that may be
imported by other systems.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
| In Ubuntu: |
|
Der Befehl »export-key« exportiert einen Assertion Body des öffentlichen Schlüssels, der von
anderen Systemen importiert sein kann.
|
|
|
Suggested by
schuko24
|
|
|
|
Located in
cmd/snap/cmd_export_key.go:43
|
|
|
28.
|
|
|
The fde-setup-request command is used inside the fde-setup hook. It will
return information about what operation for full-disk encryption is
requested and auxiliary data to complete this operation.
The fde-setup hook should do what is requested and then call
"snapctl fde-setup-result" and pass the result data to stdin.
Here is an example for how the fde-setup hook is called initially:
$ snapctl fde-setup-request
{"op":"features"}
$ echo '{"features": []}' | snapctl fde-setup-result
Alternatively the hook could reply with:
$ echo '{"error":"hardware-unsupported"}' | snapctl fde-setup-result
And then it is called again with a request to do the initial key setup:
$ snapctl fde-setup-request
{"op":"initial-setup", "key": "key-to-seal"}
$ echo "{"sealed-key":"$base64_encoded_sealed_key"}" | snapctl fde-setup-result
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
Der Befehl fde-setup-request wird innerhalb des fde-setup-Hooks verwendet. Er wird
Informationen über die angeforderte Operation der Festplattenverschlüsselung,
sowie Hilfsdaten zur Vervollständigung dieser Operation anzeigen.
Der fde-setup-Hook sollte die angeforderte Operation ausführen und dann den Befehl
"snapctl fde-setup-result" aufrufen und die Ergebnisdaten an stdin übergeben.
Hier ist ein Beispiel dafür, wie der fde-setup-Hook anfänglich aufgerufen wird:
$ snapctl fde-setup-request
{"op": "features"}
$ echo '{"features": []}' | snapctl fde-setup-result
Alternativ könnte der Hook auch mit antworten:
$ echo '{"error": "hardware-unsupported"}' | snapctl fde-setup-result
Und dann wird er erneut mit der Aufforderung aufgerufen, die anfängliche Schlüsseleinrichtung vorzunehmen:
$ snapctl fde-setup-request
{"op": "initial-setup", "key": "key-to-seal"}
$ echo "{"sealed-key":"$base64_encoded_sealed_key"}" | snapctl fde-setup-re
|
|
Translated by
Christoph Gerlach
|
|
Reviewed by
Christoph Gerlach
|
|
|
|
Located in
overlord/hookstate/ctlcmd/fde_setup.go:36
|
