|
|
17.
|
|
|
The console-conf-start command starts synchronization with console-conf
This command is used by console-conf when it starts up. It delays refreshes if
there are none currently ongoing, and exits with a specific error code if there
are ongoing refreshes which console-conf should wait for before prompting the
user to begin configuring the device.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_routine_console_conf.go:40
|
|
|
18.
|
|
|
The create-cohort command creates a set of cohort keys for a given set of snaps.
A cohort is a view or snapshot of a snap's "channel map" at a given point in
time that fixes the set of revisions for the snap given other constraints
(e.g. channel or architecture). The cohort is then identified by an opaque
per-snap key that works across systems. Installations or refreshes of the snap
using a given cohort key would use a fixed revision for up to 90 days, after
which a new set of revisions would be fixed under that same cohort key and a
new 90 days window started.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_create_cohort.go:30
|
|
|
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: |
|
A orde «create-key» crea un par de chaves de cifrado que se poden usar
para asinar asercións.
|
|
|
Suggested by
Marcos Lans
|
|
|
|
Located in
cmd/snap/cmd_create_key.go:41
|
|
|
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: |
|
A orde «delete-key» elimina o par de chaves de cifrado co
nome dado.
|
|
|
Suggested by
Marcos Lans
|
|
|
|
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: |
|
A orde «disable» desactiva un snap. Os binarios e servizos do snap
xa non estarán dispoñíbeis pero todos os datos seguirán
accesíbeis e o snap poderá ser activado de novo facilmente.
|
|
|
Suggested by
Marcos Lans
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:125
|
|
|
24.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
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: |
|
A orde «download» descarga o snap indicado e as súas asercións de apoio
ao cartafol actual coas extensións .snap e .assert respectivamente.
|
|
|
Suggested by
Marcos Lans
|
|
|
|
Located in
cmd/snap/cmd_download.go:51
|
|
|
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: |
|
A orde «export-key» exporta un corpo da aserción da chave pública
que pode ser importado por outros sistemas.
|
|
|
Suggested by
Marcos Lans
|
|
|
|
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.
|
|
|
|
|
(no translation yet)
|
|
|
|
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 '{"features": []}' | snapctl fde-setup-result
When the fde-setup hook is called with "op":"initial-setup":
$ 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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
overlord/hookstate/ctlcmd/fde_setup.go:101
|
