From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Testing core update 123
Date: Wed, 29 Aug 2018 07:53:05 +0200 [thread overview]
Message-ID: <97a22c05d743a01cb3ed02360575d459a02c08ce.camel@ipfire.org> (raw)
In-Reply-To: <866vg4r1p6qm64uevcf2o7j7.1535490441019@email.android.com>
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
Thanks for reporting back,
Am Dienstag, den 28.08.2018, 22:29 +0100 schrieb Paul Titjen:
> Hi,
>
> Thanks for the feedback. That certainly sorted the issue and the
> crypto warning has now gone. The root cause was that my original
> clean install of 2.21 core120 was then amended by an old 2.19 backup
> .ipf file. This has then put back an old version of
> /var/ipfire/ovpn/openssl/oven.cnf so adding those extended key usage
> lines back in and making new certs did the trick.
This behavior has been fixed https://cgit.ipfire.org/ipfire-2.x.git/commit/?id=291bfda71eb40a20dd4db77bacef84717ad69e82
since we excluded ovpn.cnf from the backup but that´s only one part
since a backup do includes the old certificates with the old key usage
of the digitalSignature in it so they need to be renewed in that case.
>
> I have been caught out before by this restore of an old backup on a
> newer version of ipfire. My old restore had an include of a php
> extension in the Web server conf. After the restore Web interface
> disappeared on reboot due to apache failing the startup. Using
> command line soon fixed it once having worked out the cause.
>
> This brings me to the backup ISO not working. Looking at the script
> it seems that it is downloading the ISO from ipfire download website
> with the core update number used in the source URL - the 123 iso is
> not yet available to download there and only the stable versions
> hence the fail. I am sure it works with 122. If all it does is get
> a clean iso then that still leaves the issue of breaking a clean
> install by restoring an old backup .ipf or does it build a new
> distribution based on the iso and the existing configuration files as
> a unique ISO for instant recreate of a system.
I think the core number problem in the URL should be fixed too
https://cgit.ipfire.org/ipfire-2.x.git/commit/?id=f32cbd89d9990b2a1017b7ad19ba98f8d38a5c11
Best,
Erik
next parent reply other threads:[~2018-08-29 5:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <866vg4r1p6qm64uevcf2o7j7.1535490441019@email.android.com>
2018-08-29 5:53 ` ummeegge [this message]
[not found] <002e01d43ef2$2baea2e0$830be8a0$@ministc.com>
2018-08-28 19:00 ` ummeegge
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=97a22c05d743a01cb3ed02360575d459a02c08ce.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/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