[From nobody Sun Mar 22 08:21:06 2026
Received: (at 861285-done) by bugs.debian.org; 22 Mar 2026 08:20:28 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-7.0 required=4.0 tests=BAYES_00,DKIM_SIGNED,
 DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,HAS_BUG_NUMBER,
 RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 41; hammy, 89; neutral, 22; spammy, 4.
 spammytokens:0.987-1--CLEAR, 0.948-+--loud,
 0.942-+--H*r:bugs.debian.org, 0.911-+--Read
 hammytokens:0.000-+--sk:pkgope, 0.000-+--sk:pkg-ope,
 0.000-+--H*F:U*sebastian, 0.000-+--H*F:D*breakpoint.cc,
 0.000-+--H*RU:sk:chamill
Return-path: <sebastian@breakpoint.cc>
Received: from chamillionaire.breakpoint.cc ([91.216.245.30]:37506)
 by buxtehude.debian.org with esmtps
 (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
 (Exim 4.96) (envelope-from <sebastian@breakpoint.cc>)
 id 1w4E2u-009lsN-2H for 861285-done@bugs.debian.org;
 Sun, 22 Mar 2026 08:20:28 +0000
Date: Sun, 22 Mar 2026 09:20:17 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=breakpoint.cc;
 s=2025; t=1774167619;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
 content-transfer-encoding:content-transfer-encoding:
 in-reply-to:in-reply-to:references:references;
 bh=D+7bJfod2S1BF/Cs+LyIaBGNQuXDk/IZvOVYfIfen/o=;
 b=c5U9Ndqjyzj1pRjSkCKp1UD+lhGpRl5Av0Mt8ZzGM3h6F5maDKt/tlO3LhyiwubgDfXwUo
 hJKvnO+9lNwihvOCuconQNfShBvJIiPx5VlEVHI5oDTDdyKt/axaHkLdgXvvgWGVihM8KM
 RqWPBwgvFX8XF3VcDo3cjjRgT/+3QGLBNO/EGxImhGO01WevzdqUXlRFHf4+Z6u2ghuD+V
 +3PQpCUGCzs7iLcC3YOPeK9MaDH6vcSOa9JYAb6fboyHHwc6dzAxA1M7xW+87R+4/Gm/vx
 NAHEfQaBejxiIxaJE50efsGUljUdXjpbgkY2Lwez8xCg3RVSnGLKmZZXlRQWYQ==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=breakpoint.cc;
 s=2025e; t=1774167619;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
 content-transfer-encoding:content-transfer-encoding:
 in-reply-to:in-reply-to:references:references;
 bh=D+7bJfod2S1BF/Cs+LyIaBGNQuXDk/IZvOVYfIfen/o=;
 b=fMLjm9nwNo8O+idY64UxZQXK4Nq25c2sb1C6kGmg946OulU3ZHx+5eGYRq5HgdM7afJuWB
 /WFBdG4fl1nCmJDQ==
From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: 861285-done@bugs.debian.org
Cc: "ISHIKAWA, chiaki" <ishikawa@yk.rim.or.jp>
Subject: Re: Bug#861285: [Pkg-openssl-devel] Bug#861285: openssl enc -k
 path-for-keyphrase-file ...c does not fail if the keyphrase-file is missing.
Message-ID: <20260322082017._QjVWEAt@breakpoint.cc>
References: <48557c6b-4894-8ace-8d8f-9a30cf3d125a@yk.rim.or.jp>
 <20170427120807.qqctenlvn22mg4fj@breakpoint.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <20170427120807.qqctenlvn22mg4fj@breakpoint.cc>

On 2017-04-27 14:08:08 [+0200], To ISHIKAWA, chiaki wrote:
> On 2017-04-27 08:46:10 [+0900], ISHIKAWA,chiaki wrote:
> > KFILE=3Dpath-for-passphrase-file      (say, ~/mypass)
> > BNAME=3Dfile-to-be-encrypted
> >=20
> > openssl enc -k ${KFILE} -in  ${BNAME} -out ${BNAME}.enc -aes-256-cbc
> >=20
> > To my surprise if ${KFILE} is missing, openssl does not complain
> > and seems to encrypt the input file anyway: but with what passphrase?!
> =E2=80=A6
> > I would rather see openssl complain that the passphrase file is
> > missing LOUD and CLEAR (and returns an error code. I checked that the
> > following does not print "fail".
>=20
> $ openssl enc --help 2>&1|grep -- -k
> -k val         Passphrase
> -kfile infile  Read passphrase from file
>=20
> I think you mixed up -k with -kfile.

Old me should have closed this.

Sebastian]