|
20.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
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 and reviewed by
Salvatore Cocuzza
|
|
|
|
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.
|
|
|
|
Il comando delete-key elimina la coppia di chiavi crittografiche locale con
il nome dato.
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
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.
|
|
|
|
Il comando disable disabilita in un attimo. I binari ei servizi del
snap non sarà più disponibile, ma tutti i dati sono ancora disponibili
e lo snap può essere facilmente riattivato.
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
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
Salvatore Cocuzza
|
|
|
|
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.
|
|
|
|
Il comando download scarica lo snap dato e le sue asserzioni di supporto
nella directory corrente rispettivamente con le estensioni di file .snap e .assert.
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
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.
|
|
|
|
Il comando enable abilita uno snap precedentemente disabilitato.
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
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.
|
|
|
|
Il comando export-key esporta un corpo di asserzione di chiave pubblica che potrebbe essere
importato da altri sistemi.
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
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 '[]' | 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", "key-name":"key-for-ubuntu-data"}
$ echo "$sealed_key" | snapctl fde-setup-result
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
Il comando fde-setup-request viene utilizzato all'interno dell'hook fde-setup. Lo farà
restituire informazioni su quale sia l'operazione per la crittografia dell'intero disco
dati richiesti e ausiliari per completare questa operazione.
L'hook fde-setup dovrebbe fare ciò che è richiesto e quindi chiamare
"snapctl fde-setup-result" e passa i dati del risultato a stdin.
Ecco un esempio di come viene chiamato inizialmente l'hook fde-setup:
$ snapctl fde-setup-request
{"op":"features"}
$ eco '[]' | snapctl fde-setup-result
In alternativa l'hook potrebbe rispondere con:
$ echo '{"error":"hardware-unsupported"}' | snapctl fde-setup-result
E quindi viene chiamato di nuovo con una richiesta per eseguire l'impostazione iniziale della chiave:
$ snapctl fde-setup-request
{"op":"initial-setup", "key": "key-to-seal", "key-name":"key-for-ubuntu-data"}
$ eco "$chiave_sigillata" | snapctl fde-setup-result
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
Located in
overlord/hookstate/ctlcmd/fde_setup.go:36
|
|
29.
|
|
|
The fde-setup-result command sets the result data for a fde-setup hook
reading it from stdin.
For example:
When the fde-setup hook is called with "op":"features:
$ echo "[]" | snapctl fde-setup-result
When the fde-setup hook is called with "op":"initial-setup":
$ echo "sealed-key" | snapctl fde-setup-result
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
Il comando fde-setup-result imposta i dati del risultato per un hook fde-setup
leggendolo da stdin.
Per esempio:
Quando l'hook fde-setup viene chiamato con "op":"features:
$ eco "[]" | snapctl fde-setup-result
Quando l'hook fde-setup viene chiamato con "op":"initial-setup":
$ echo "sealed-key" | snapctl fde-setup-result
|
|
Translated and reviewed by
Salvatore Cocuzza
|
|
|
|
Located in
overlord/hookstate/ctlcmd/fde_setup.go:101
|