|
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)
|
|
|
|
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.
|
|
|
|
"create-user" komutu verilen email adresiyle ilişkilendirilmiş mağaza hesabında kayıtlı olan
kullanıcı adı ve SSH anahtarı bilgileri ile yerel(local) bir sistem kullanıcısı oluşturur.
|
|
Translated and reviewed by
Efe Mert
|
|
|
|
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
Efe Mert
|
|
|
|
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.
|
|
|
|
delete-key komutu, verilen ada sahip yerel kriptografik anahtar
çiftini siler.
|
|
Translated and reviewed by
Celestine Prower
|
|
|
|
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)
|
|
Translated by
Sabri Ünal
|
|
Reviewed by
Sabri Ünal
|
|
|
|
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.
|
|
|
|
(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)
|
|
|
|
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.
|
|
|
|
(no translation yet)
|
|
|
|
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)
|
|
|
|
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
|