From: Adolf Belka <adolf.belka@ipfire.org>
To: Nick Howitt <nick@howitts.co.uk>,
Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: [PATCH] core194: Fix cert name and change other check to ! -z
Date: Wed, 30 Apr 2025 18:29:47 +0200 [thread overview]
Message-ID: <54e23991-ca8b-463c-ae86-2379199596f0@ipfire.org> (raw)
In-Reply-To: <09f1b0d4-a0ad-43ae-b71a-4c1d53d95b6d@howitts.co.uk>
Hi Nick,
On 30/04/2025 16:53, Nick Howitt wrote:
> Can I ask what you are testing here with the "! -z"? Typically you would use "-n" rather than "! -z", but both are tests for strings and not files - https://tldp.org/LDP/abs/html/comparison-ops.html. "! -s" would test for a zero length file and if the file exists at all.
Thanks for the input. You are absolutely correct. I tested my script but only with index.txt empty. I just tried it with something in index.txt and it still detected it as empty because, as you point out -s is for the file test while -z is for the string test. So in my case it is checking if the string "/var/ipfire/certs/index.txt" is not empty, which of course it will never be empty.
Duuuh.
I just tried it with -z replaced by -s and that properly detects if the file is empty or not.
Hi Michael,
Could you please change the ! -z to ! -s in my last patch or should I send out a v2 patch?
Regards,
Adolf.
>
> Nick
>
> On 30/04/2025 15:17, Adolf Belka wrote:
>> - Error in hostcert extension
>> - -z gives true if not zero and we need true if it is zero so had to add not command.
>> - I thought I had tested the original patch of this change but obviously not because
>> there was missing whitespace and filenames not quoted plus the fixes I have added
>> in this patch.
>> - I definitely tested this out this time by copying it from the update.sh and applying
>> it to my vm system.
>>
>> Tested-by: Adolf Belka<adolf.belka@ipfire.org>
>> Signed-off-by: Adolf Belka<adolf.belka@ipfire.org>
>> ---
>> config/rootfiles/core/194/update.sh | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/config/rootfiles/core/194/update.sh b/config/rootfiles/core/194/update.sh
>> index b758c7bf6..8fbf22750 100644
>> --- a/config/rootfiles/core/194/update.sh
>> +++ b/config/rootfiles/core/194/update.sh
>> @@ -104,7 +104,7 @@ ldconfig
>> /usr/local/bin/filesystem-cleanup
>>
>> # Increment ipsec serial file if x509 certificates present and no content in index.txt
>> -if [ -e "/var/ipfire/certs/hostcert.pm" ] && [ -z "/var/ipfire/certs/index.txt" ]; then
>> +if [ -e "/var/ipfire/certs/hostcert.pem" ] && [ ! -z "/var/ipfire/certs/index.txt" ]; then
>> sed -i "s/01/02/" /var/ipfire/certs/serial
>> fi
>>
>
prev parent reply other threads:[~2025-04-30 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 14:17 Adolf Belka
2025-04-30 14:53 ` Nick Howitt
2025-04-30 16:29 ` Adolf Belka [this message]
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=54e23991-ca8b-463c-ae86-2379199596f0@ipfire.org \
--to=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=michael.tremer@ipfire.org \
--cc=nick@howitts.co.uk \
/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