From 3e319b1f93f75a3bab86425221f2bcbf5603f3f9 Mon Sep 17 00:00:00 2001 From: Ben Kaduk Date: Wed, 3 Aug 2016 10:23:56 -0500 Subject: [PATCH] Properly escape quotes for otp set_string example The libss parser will consume paired double quotes, but within a double-quoted region, repeated double quotes will be treated as an escape and passed through as a single double quote. (The new kadmin(1) parser in 1.14 that lets commands be specified on the command line without -q does not go through the libss parser, so standard shell methods for escaping quotes function as usual.) ticket: 8469 (new) target_version: 1.14-next tags: pullup --- doc/admin/admin_commands/kadmin_local.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/admin/admin_commands/kadmin_local.rst b/doc/admin/admin_commands/kadmin_local.rst index a91aa06ec9..50c3b99ea4 100644 --- a/doc/admin/admin_commands/kadmin_local.rst +++ b/doc/admin/admin_commands/kadmin_local.rst @@ -668,7 +668,7 @@ Alias: **setstr** Example:: set_string host/foo.mit.edu session_enctypes aes128-cts - set_string user@FOO.COM otp [{"type":"hotp","username":"custom"}] + set_string user@FOO.COM otp "[{""type"":""hotp"",""username"":""al""}]" .. _set_string_end: -- 2.47.2