From 12726dc20202424933b3f60f7c7e33614368f12c Mon Sep 17 00:00:00 2001 From: Felix Geller Date: Wed, 13 Sep 2023 07:58:01 +0200 Subject: [PATCH] update readme. --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 6715cdc..364469a 100644 --- a/README.md +++ b/README.md @@ -278,10 +278,10 @@ Example for an authorization configuration that is used for the system tests: "ca-certificate": "test-secrets/snakeoil-ca-1.crt" } -Relative paths are interpreted with respect to the auth file, e.g. if the -example above is stored in /some/dir/kt-auth.json, `kt` will expect to find the -client certificate in /some/dir/test-secrets/kt-test.crt. You can disable this -behavior by using absolute paths in the configuration file. +If any certificate or key path is simply the name of the file, it is assumed to +be in the same directory as the auth file itself. For example if the path to the +auth file is `/some/dir/kt-auth.json` then a `"client-certificate": +"kt-test.crt"` will be qualified to `/some/dir/kt-test.crt`. ### TLS one-way