From: Tony Finch <dot@dotat.at>
To: wireguard@lists.zx2c4.com
Subject: [PATCH] wg: include filename in error messages
Date: Tue, 30 Apr 2024 13:25:34 +0100 [thread overview]
Message-ID: <a0fe98b4-15a5-a60b-9eb2-2c721e60dd6d@dotat.at> (raw)
When wg(8) is invoked from a script, it can be hard to tell what
caused an error message if the message does not contain enough
context.
Signed-off-by: Tony Finch <dot@dotat.at>
---
src/config.c | 8 ++++----
src/setconf.c | 11 +++++++----
2 files changed, 11 insertions(+), 8 deletions(-)
diff --git src/config.c src/config.c
index 81ccb47..9f15477 100644
--- src/config.c
+++ src/config.c
@@ -123,7 +123,7 @@ static bool parse_keyfile(uint8_t key[static WG_KEY_LEN], const char *path)
f = fopen(path, "r");
if (!f) {
- perror("fopen");
+ fprintf(stderr, "open %s: %s", path, strerror(errno));
return false;
}
@@ -135,19 +135,19 @@ static bool parse_keyfile(uint8_t key[static WG_KEY_LEN], const char *path)
goto out;
}
- fprintf(stderr, "Invalid length key in key file\n");
+ fprintf(stderr, "Invalid length key in %s\n", path);
goto out;
}
dst[WG_KEY_LEN_BASE64 - 1] = '\0';
while ((c = getc(f)) != EOF) {
if (!char_is_space(c)) {
- fprintf(stderr, "Found trailing character in key file: `%c'\n", c);
+ fprintf(stderr, "Found trailing character `%c' in %s\n", c, path);
goto out;
}
}
if (ferror(f) && errno) {
- perror("getc");
+ fprintf(stderr, "read %s: %s", path, strerror(errno));
goto out;
}
ret = parse_key(key, dst);
diff --git src/setconf.c src/setconf.c
index 1c5b138..414785d 100644
--- src/setconf.c
+++ src/setconf.c
@@ -3,6 +3,7 @@
* Copyright (C) 2015-2020 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
*/
+#include <errno.h>
#include <stddef.h>
#include <stdio.h>
#include <stdlib.h>
@@ -102,6 +103,7 @@ int setconf_main(int argc, const char *argv[])
{
struct wgdevice *device = NULL;
struct config_ctx ctx;
+ const char *path = NULL;
FILE *config_input = NULL;
char *config_buffer = NULL;
size_t config_buffer_len = 0;
@@ -112,9 +114,10 @@ int setconf_main(int argc, const char *argv[])
return 1;
}
- config_input = fopen(argv[2], "r");
+ path = argv[2];
+ config_input = fopen(path, "r");
if (!config_input) {
- perror("fopen");
+ fprintf(stderr, "open %s: %s", path, strerror(errno));
return 1;
}
if (!config_read_init(&ctx, !strcmp(argv[0], "addconf"))) {
@@ -123,13 +126,13 @@ int setconf_main(int argc, const char *argv[])
}
while (getline(&config_buffer, &config_buffer_len, config_input) >= 0) {
if (!config_read_line(&ctx, config_buffer)) {
- fprintf(stderr, "Configuration parsing error\n");
+ fprintf(stderr, "Configuration parsing error in %s\n", path);
goto cleanup;
}
}
device = config_read_finish(&ctx);
if (!device) {
- fprintf(stderr, "Invalid configuration\n");
+ fprintf(stderr, "Invalid configuration in %s\n", path);
goto cleanup;
}
strncpy(device->name, argv[1], IFNAMSIZ - 1);
--
2.39.2
next reply other threads:[~2024-11-18 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 12:25 Tony Finch [this message]
2024-04-30 12:36 ` Tony Finch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0fe98b4-15a5-a60b-9eb2-2c721e60dd6d@dotat.at \
--to=dot@dotat.at \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).