|
|
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)
|
|
|
|
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.
|
|
|
|
|
(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 "[]" | 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.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
overlord/hookstate/ctlcmd/fde_setup.go:101
|
|
|
30.
|
|
|
The file-access command returns information about a snap's file system access.
This command is used by the xdg-document-portal service to identify
files that do not need to be proxied to provide access within
confinement.
File paths are interpreted as host file system paths. The tool may
return false negatives (e.g. report that a file path is unreadable,
despite being readable under a different path). It also does not
check if file system permissions would render a file unreadable.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_routine_file_access.go:43
|
|
|
31.
|
|
|
The find command queries the store for available packages.
With the --private flag, which requires the user to be logged-in to the store
(see 'snap help login'), it instead searches for private snaps that the user
has developer access to, either directly or through the store's collaboration
feature.
A green check mark (given color and unicode support) after a publisher name
indicates that the publisher has been verified.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_find.go:40
|
|
|
36.
|
|
|
The info command shows detailed information about snaps.
The snaps can be specified by name or by path; names are looked for both in the
store and in the installed snaps; paths can refer to a .snap file, or to a
directory that contains an unpacked snap suitable for 'snap try' (an example
of this would be the 'prime' directory snapcraft produces).
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_info.go:59
|
|
|
37.
|
|
|
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
cmd/snap/cmd_snap_op.go:52
|
|
|
39.
|
|
|
|
|
|
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_interfaces.go:40
|
|
|
40.
|
|
|
The is-connected command returns success if the given plug or slot of the
calling snap is connected, and failure otherwise.
$ snapctl is-connected plug
$ echo $?
1
Snaps can only query their own plugs and slots - snap name is implicit and
implied by the snapctl execution context.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
overlord/hookstate/ctlcmd/is_connected.go:40
|
|
|
41.
|
|
|
The keys command lists cryptographic keys 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)
|
|
|
|
Located in
cmd/snap/cmd_keys.go:39
|
