|
22.
|
|
|
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.
|
|
|
|
L'ordre create-key crea un parell de claus criptogràfiques que es poden
usar per signar assercions.
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_create_key.go:41
|
|
23.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_create_user.go:33
|
|
24.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_debug.go:29
|
|
25.
|
|
|
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.
|
|
|
|
L'ordre delete-key esborrra el parell de claus criptogràfiques locals amb
el nom donat.
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_delete_key.go:41
|
|
26.
|
|
|
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.
|
|
|
|
L'ordre disable desactiva un snap. Els binaris i serveis del snap ja no estaran
disponibles, però totes les dades encara estan disponibles i l'snap pot
activar-se un altre cop fàcilment.
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:125
|
|
27.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_disconnect.go:41
|
|
28.
|
|
|
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.
|
|
|
|
L'ordre download descarrega el snap donat i les seves assercions de suport al
directori actual amb extensions de fitxer .snap i .assert, respectivament.
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_download.go:51
|
|
29.
|
|
|
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.
|
|
|
|
L'ordre enable activa un snap que havia estat desactivat prèviament.
|
|
Translated by
Jaume Villalba
|
|
Reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:121
|
|
30.
|
|
|
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.
|
|
|
|
L'ordre export-key exporta una afirmació de clau pública que es pot importar a
d'altres sistemes.
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
cmd/snap/cmd_export_key.go:43
|
|
31.
|
|
|
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.
|
|
|
|
L'ordre fde-setup-request s'usa dins del ganxo fde-setup. Retornarà
informació sobre quina operació per a l'encriptat total de disc es
requereix i dades auxiliars per completar l'operació.
El ganxo fde-setup hauria de fer el que es requereix i després hauria
de cridar "snapctl fde-setup-result" i passar el resultat a stdin.
Aquí hi ha un exemple per a la crida inicial del ganxo fde-setup:
$ snapctl fde-setup-request
{"op":"features"}
$ echo '{"features": []}' | snapctl fde-setup-result
Alternativament, el ganxo podria respondre amb:
$ echo '{"error":"hardware-unsupported"}' | snapctl fde-setup-result
I després es crida un altre cop amb una demana per fer la configuració inicial de la clau:
$ snapctl fde-setup-request
{"op":"initial-setup", "key": "key-to-seal"}
$ echo "{"sealed-key":"$base64_encoded_sealed_key"}" | snapctl fde-setup-result
|
|
Translated and reviewed by
Walter Garcia-Fontes
|
|
|
|
Located in
overlord/hookstate/ctlcmd/fde_setup.go:36
|