veritysetup: do some superficial checking on volume name

cryptsetup does this too, so let's better be safe here, too.

diff --git a/src/veritysetup/veritysetup.c b/src/veritysetup/veritysetup.c
index 3551ed4f3a6dd63fe65b7f72b4a1c9c14bbe10f3..a81e93cb756529ac317856a4e903ed405c7231d3 100644 (file)
--- a/src/veritysetup/veritysetup.c
+++ b/src/veritysetup/veritysetup.c
@@ -146,6 +146,9 @@ static int run(int argc, char *argv[]) {
                 root_hash = argv[5];
                 options = mangle_none(argc > 6 ? argv[6] : NULL);
 
+                if (!filename_is_valid(volume))
+                        return log_error_errno(SYNTHETIC_ERRNO(EINVAL), "Volume name '%s' is not valid.", volume);
+
                 r = unhexmem(root_hash, SIZE_MAX, &m, &l);
                 if (r < 0)
                         return log_error_errno(r, "Failed to parse root hash: %m");
@@ -210,6 +213,9 @@ static int run(int argc, char *argv[]) {
 
                 volume = argv[2];
 
+                if (!filename_is_valid(volume))
+                        return log_error_errno(SYNTHETIC_ERRNO(EINVAL), "Volume name '%s' is not valid.", volume);
+
                 r = crypt_init_by_name(&cd, volume);
                 if (r == -ENODEV) {
                         log_info("Volume %s already inactive.", volume);