Re: IPFire 2.27 - Core Update 177 is available for testing

Re: IPFire 2.27 - Core Update 177 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

Hi All,
When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.

Bug raised for this.
https://bugzilla.ipfire.org/show_bug.cgi?id=13195

Regards,
Adolf.

On 27/07/2023 15:00, IPFire Project wrote:
> IPFire Logo
> 
> there is a new post from Michael Tremer on the IPFire Blog:
> 
> *IPFire 2.27 - Core Update 177 is available for testing*
> 
>     The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
> 
> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
> 
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

Re: IPFire 2.27 - Core Update 177 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Hi All,

I have found another bug.

When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file

Surprised as I did not have rng-tools installed as an addon.

After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.


I have raised a bug report for this.

https://bugzilla.ipfire.org/show_bug.cgi?id=13197


Regards,

Adolf


On 27/07/2023 22:13, Adolf Belka wrote:
> Hi All,
> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>
> Bug raised for this.
> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>
> Regards,
> Adolf.
>
> On 27/07/2023 15:00, IPFire Project wrote:
>> IPFire Logo
>>
>> there is a new post from Michael Tremer on the IPFire Blog:
>>
>> *IPFire 2.27 - Core Update 177 is available for testing*
>>
>>     The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>

Re: IPFire 2.27 - Core Update 177 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 2140 bytes --]

Hello Adolf,

Thanks for raising this. Literally a minute ago someone else opened the same ticket (with less detail tho).

It looks like rngd was never removed in the Core Update. I will take care of this and push a commit today.

The mount problem seems to be a bigger issue. Please see my comments on your bug report.

-Michael

> On 28 Jul 2023, at 11:37, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> I have found another bug.
> 
> When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file
> 
> Surprised as I did not have rng-tools installed as an addon.
> 
> After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.
> 
> 
> I have raised a bug report for this.
> 
> https://bugzilla.ipfire.org/show_bug.cgi?id=13197
> 
> 
> Regards,
> 
> Adolf
> 
> 
> On 27/07/2023 22:13, Adolf Belka wrote:
>> Hi All,
>> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>> 
>> Bug raised for this.
>> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>> 
>> Regards,
>> Adolf.
>> 
>> On 27/07/2023 15:00, IPFire Project wrote:
>>> IPFire Logo
>>> 
>>> there is a new post from Michael Tremer on the IPFire Blog:
>>> 
>>> *IPFire 2.27 - Core Update 177 is available for testing*
>>> 
>>>     The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>> 
>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>> 
>>> The IPFire Project
>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>> 

Re: IPFire 2.27 - Core Update 177 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 3160 bytes --]

Hi All,

General feedback on CU177 Testing so far.

Apart from bugs 13195 & 19137, which have fixes submitted, the rest of the testing has gone without any problems.

The removal of the 5 min delay from the cups install means that I no longer end up with those fail messages about cups not running when I do the reboot after the upgrade.

The updated samba is working to the extent that my testing just has a basic share connected to a vm machine on my vm green network.

OpenVPN Road Warrior and Net2Net are both working without any problems.

Also tested a fresh install and it went without any problems. (Using iso with fix for bug 13195).

All the graphs and Logs I have checked are all working and my ssh connection is fully functioning.

Web proxy is working as before but I don't have URL Filter or Update Accelerator set up on my vm testbed (also not on my production system).

Regards,

Adolf.


On 28/07/2023 12:47, Michael Tremer wrote:
> Hello Adolf,
> 
> Thanks for raising this. Literally a minute ago someone else opened the same ticket (with less detail tho).
> 
> It looks like rngd was never removed in the Core Update. I will take care of this and push a commit today.
> 
> The mount problem seems to be a bigger issue. Please see my comments on your bug report.
> 
> -Michael
> 
>> On 28 Jul 2023, at 11:37, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi All,
>>
>> I have found another bug.
>>
>> When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file
>>
>> Surprised as I did not have rng-tools installed as an addon.
>>
>> After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.
>>
>>
>> I have raised a bug report for this.
>>
>> https://bugzilla.ipfire.org/show_bug.cgi?id=13197
>>
>>
>> Regards,
>>
>> Adolf
>>
>>
>> On 27/07/2023 22:13, Adolf Belka wrote:
>>> Hi All,
>>> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>>>
>>> Bug raised for this.
>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>>>
>>> Regards,
>>> Adolf.
>>>
>>> On 27/07/2023 15:00, IPFire Project wrote:
>>>> IPFire Logo
>>>>
>>>> there is a new post from Michael Tremer on the IPFire Blog:
>>>>
>>>> *IPFire 2.27 - Core Update 177 is available for testing*
>>>>
>>>>      The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>>>
>>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>>>
>>>> The IPFire Project
>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>>>
> 

Re: IPFire 2.27 - Core Update 177 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 4091 bytes --]

Hello everyone,

I just pushed another change regarding #13203 which fixed the snort Community rules download URL.

I regard this as the last change that I have on my list for this update and hope that we caught any known new regressions in the testing period so far. I am now aware of any outstanding issues in this update. Please let me know if I forgot/overlooked something.

I would like to release this update within the next couple of days as it contains so many security issues and then focus on the following update.

Is there anything for Core Update 178 that has not been submitted to the list, yet? Otherwise I would like to close it in the next calendar week and submit it for testing to our community.

All the best,
-Michael

> On 29 Jul 2023, at 11:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> General feedback on CU177 Testing so far.
> 
> Apart from bugs 13195 & 19137, which have fixes submitted, the rest of the testing has gone without any problems.
> 
> The removal of the 5 min delay from the cups install means that I no longer end up with those fail messages about cups not running when I do the reboot after the upgrade.
> 
> The updated samba is working to the extent that my testing just has a basic share connected to a vm machine on my vm green network.
> 
> OpenVPN Road Warrior and Net2Net are both working without any problems.
> 
> Also tested a fresh install and it went without any problems. (Using iso with fix for bug 13195).
> 
> All the graphs and Logs I have checked are all working and my ssh connection is fully functioning.
> 
> Web proxy is working as before but I don't have URL Filter or Update Accelerator set up on my vm testbed (also not on my production system).
> 
> Regards,
> 
> Adolf.
> 
> 
> On 28/07/2023 12:47, Michael Tremer wrote:
>> Hello Adolf,
>> Thanks for raising this. Literally a minute ago someone else opened the same ticket (with less detail tho).
>> It looks like rngd was never removed in the Core Update. I will take care of this and push a commit today.
>> The mount problem seems to be a bigger issue. Please see my comments on your bug report.
>> -Michael
>>> On 28 Jul 2023, at 11:37, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> Hi All,
>>> 
>>> I have found another bug.
>>> 
>>> When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file
>>> 
>>> Surprised as I did not have rng-tools installed as an addon.
>>> 
>>> After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.
>>> 
>>> 
>>> I have raised a bug report for this.
>>> 
>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13197
>>> 
>>> 
>>> Regards,
>>> 
>>> Adolf
>>> 
>>> 
>>> On 27/07/2023 22:13, Adolf Belka wrote:
>>>> Hi All,
>>>> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>>>> 
>>>> Bug raised for this.
>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>>>> 
>>>> Regards,
>>>> Adolf.
>>>> 
>>>> On 27/07/2023 15:00, IPFire Project wrote:
>>>>> IPFire Logo
>>>>> 
>>>>> there is a new post from Michael Tremer on the IPFire Blog:
>>>>> 
>>>>> *IPFire 2.27 - Core Update 177 is available for testing*
>>>>> 
>>>>>     The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>>>> 
>>>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>>>> 
>>>>> The IPFire Project
>>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>>>> 

Re: IPFire 2.27 - Core Update 177 is available for testing

[Adolf Belka]

[-- Attachment #1: Type: text/plain, Size: 4413 bytes --]

Hi All,

On 02/08/2023 11:59, Michael Tremer wrote:
> Hello everyone,
> 
> I just pushed another change regarding #13203 which fixed the snort Community rules download URL.
> 
> I regard this as the last change that I have on my list for this update and hope that we caught any known new regressions in the testing period so far. I am now aware of any outstanding issues in this update. Please let me know if I forgot/overlooked something.
I don't have anything extra for CU177
> 
> I would like to release this update within the next couple of days as it contains so many security issues and then focus on the following update.
> 
> Is there anything for Core Update 178 that has not been submitted to the list, yet? Otherwise I would like to close it in the next calendar week and submit it for testing to our community.
I don't have anything that needs CU178 to wait for. Anything else I 
am/will work on can wait for CU179

Regards,
Adolf.

> 
> All the best,
> -Michael
> 
>> On 29 Jul 2023, at 11:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi All,
>>
>> General feedback on CU177 Testing so far.
>>
>> Apart from bugs 13195 & 19137, which have fixes submitted, the rest of the testing has gone without any problems.
>>
>> The removal of the 5 min delay from the cups install means that I no longer end up with those fail messages about cups not running when I do the reboot after the upgrade.
>>
>> The updated samba is working to the extent that my testing just has a basic share connected to a vm machine on my vm green network.
>>
>> OpenVPN Road Warrior and Net2Net are both working without any problems.
>>
>> Also tested a fresh install and it went without any problems. (Using iso with fix for bug 13195).
>>
>> All the graphs and Logs I have checked are all working and my ssh connection is fully functioning.
>>
>> Web proxy is working as before but I don't have URL Filter or Update Accelerator set up on my vm testbed (also not on my production system).
>>
>> Regards,
>>
>> Adolf.
>>
>>
>> On 28/07/2023 12:47, Michael Tremer wrote:
>>> Hello Adolf,
>>> Thanks for raising this. Literally a minute ago someone else opened the same ticket (with less detail tho).
>>> It looks like rngd was never removed in the Core Update. I will take care of this and push a commit today.
>>> The mount problem seems to be a bigger issue. Please see my comments on your bug report.
>>> -Michael
>>>> On 28 Jul 2023, at 11:37, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> I have found another bug.
>>>>
>>>> When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file
>>>>
>>>> Surprised as I did not have rng-tools installed as an addon.
>>>>
>>>> After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.
>>>>
>>>>
>>>> I have raised a bug report for this.
>>>>
>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13197
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Adolf
>>>>
>>>>
>>>> On 27/07/2023 22:13, Adolf Belka wrote:
>>>>> Hi All,
>>>>> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>>>>>
>>>>> Bug raised for this.
>>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>>>>>
>>>>> Regards,
>>>>> Adolf.
>>>>>
>>>>> On 27/07/2023 15:00, IPFire Project wrote:
>>>>>> IPFire Logo
>>>>>>
>>>>>> there is a new post from Michael Tremer on the IPFire Blog:
>>>>>>
>>>>>> *IPFire 2.27 - Core Update 177 is available for testing*
>>>>>>
>>>>>>      The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>>>>>
>>>>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>>>>>
>>>>>> The IPFire Project
>>>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>>>>>
> 

-- 
Sent from my laptop

Re: IPFire 2.27 - Core Update 177 is available for testing

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 5174 bytes --]

Hello everyone,

I just had a phone call with Arne and we decided to add an extra update between 177 and 178 with the latest kernel updates regarding the new processor vulnerabilities in AMD/Intel processors. The update will also include any microcode updates that are available at this time.

The next branch that currently is on c178 will be changed to c179.

As soon as the new c178 update with the kernel fixes is available, please help us testing that we can release it as soon as possible aiming for the next calendar week.

All the best,
-Michael

> On 2 Aug 2023, at 13:25, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi All,
> 
> On 02/08/2023 11:59, Michael Tremer wrote:
>> Hello everyone,
>> I just pushed another change regarding #13203 which fixed the snort Community rules download URL.
>> I regard this as the last change that I have on my list for this update and hope that we caught any known new regressions in the testing period so far. I am now aware of any outstanding issues in this update. Please let me know if I forgot/overlooked something.
> I don't have anything extra for CU177
>> I would like to release this update within the next couple of days as it contains so many security issues and then focus on the following update.
>> Is there anything for Core Update 178 that has not been submitted to the list, yet? Otherwise I would like to close it in the next calendar week and submit it for testing to our community.
> I don't have anything that needs CU178 to wait for. Anything else I am/will work on can wait for CU179
> 
> Regards,
> Adolf.
> 
>> All the best,
>> -Michael
>>> On 29 Jul 2023, at 11:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> Hi All,
>>> 
>>> General feedback on CU177 Testing so far.
>>> 
>>> Apart from bugs 13195 & 19137, which have fixes submitted, the rest of the testing has gone without any problems.
>>> 
>>> The removal of the 5 min delay from the cups install means that I no longer end up with those fail messages about cups not running when I do the reboot after the upgrade.
>>> 
>>> The updated samba is working to the extent that my testing just has a basic share connected to a vm machine on my vm green network.
>>> 
>>> OpenVPN Road Warrior and Net2Net are both working without any problems.
>>> 
>>> Also tested a fresh install and it went without any problems. (Using iso with fix for bug 13195).
>>> 
>>> All the graphs and Logs I have checked are all working and my ssh connection is fully functioning.
>>> 
>>> Web proxy is working as before but I don't have URL Filter or Update Accelerator set up on my vm testbed (also not on my production system).
>>> 
>>> Regards,
>>> 
>>> Adolf.
>>> 
>>> 
>>> On 28/07/2023 12:47, Michael Tremer wrote:
>>>> Hello Adolf,
>>>> Thanks for raising this. Literally a minute ago someone else opened the same ticket (with less detail tho).
>>>> It looks like rngd was never removed in the Core Update. I will take care of this and push a commit today.
>>>> The mount problem seems to be a bigger issue. Please see my comments on your bug report.
>>>> -Michael
>>>>> On 28 Jul 2023, at 11:37, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>> 
>>>>> Hi All,
>>>>> 
>>>>> I have found another bug.
>>>>> 
>>>>> When I did the Core Update 177 Testing update I was surprised to find that I got a failure message that /usr/sbin/rngd failed to find the libssl.so.1.1 file
>>>>> 
>>>>> Surprised as I did not have rng-tools installed as an addon.
>>>>> 
>>>>> After investigating I realised that when rng-tools was moved to an addon the existing rootfile files were not removed from users IPFire systems. So /usr/sbin/rngd and /usr/bin/rngtest still exist on the old systems.
>>>>> 
>>>>> 
>>>>> I have raised a bug report for this.
>>>>> 
>>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13197
>>>>> 
>>>>> 
>>>>> Regards,
>>>>> 
>>>>> Adolf
>>>>> 
>>>>> 
>>>>> On 27/07/2023 22:13, Adolf Belka wrote:
>>>>>> Hi All,
>>>>>> When doing a reboot I get a fail message at the stage of remount root readonly. The reboot seems to occur okay in that IPFire works as expected after the reboot. Problem occurs at each reboot and has been shown on two vm machines that were upgraded to CU177 Testing.
>>>>>> 
>>>>>> Bug raised for this.
>>>>>> https://bugzilla.ipfire.org/show_bug.cgi?id=13195
>>>>>> 
>>>>>> Regards,
>>>>>> Adolf.
>>>>>> 
>>>>>> On 27/07/2023 15:00, IPFire Project wrote:
>>>>>>> IPFire Logo
>>>>>>> 
>>>>>>> there is a new post from Michael Tremer on the IPFire Blog:
>>>>>>> 
>>>>>>> *IPFire 2.27 - Core Update 177 is available for testing*
>>>>>>> 
>>>>>>>     The next update for IPFire is available for testing! It contains more hardening features for modern processors and a large number of security fixes in third-party packages.
>>>>>>> 
>>>>>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-177-is-available-for-testing>
>>>>>>> 
>>>>>>> The IPFire Project
>>>>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>>>>>> 
> 
> -- 
> Sent from my laptop