Posts in 2019

And it is finally the time of the year again, when we look back at 2019, thinking about all the good and bad things it brought us.

Hello everyone,

the last Core Update for this decade is finally available for testing! If you have a couple of hours free over the holidays, please help us out by installing it and sending us your feedback!

Hello,

we have recently launched our new IPFire Community Portal with that, we also launched our new account system at people.ipfire.org.

Just days after the last one, we are releasing IPFire 2.23 - Core Update 138. It addresses and mitigates recently announced vulnerabilities in Intel processors.

Just with the release of IPFire 2.23 - Core Update 137, we are making the next update available to address and mitigate recently announced vulnerabilities in Intel processors.

We are happy to announce the release of IPFire 2.23 - Core Update 137. It comes with an updated kernel, a reworked Quality of Service and various bug and security fixes.

Finally, the moment is here. We are launching our new Community Portal based on Discourse!

Hello community,

I would like to announce that we have made IPFire available on Hetzner Cloud, a large hosting provider from Germany.

A little bit behind schedule, we are happy to announce the upcoming release of IPFire 2.23 - Core Update 137. It comes with an updated kernel, a reworked Quality of Service and various bug and security fixes.

There have been improvements to our Quality of Service (or QoS) which have made me very excited.

This is the official release announcement for IPFire 2.23 - Core Update 136. A new update packed with loads of security fixes, bug fixes and a couple of important new features.

Dear community,

the summer has been a quiet time for us with a little relaxation, but also some shifted focus on our infrastructure and other things. But now we are back with a large update which is packed with important new features and fixes.

This is a post to the developers and other people who contribute to the IPFire project and have an account on our infrastructure.

This is the official release announcement for IPFire 2.23 - Core Update 135, which is packed with a new kernel, various bug fixes and we recommend to install it as soon as possible.

Hello,

after a little break with many things to fight, we are back with a brand new Core Update which is packed with various bug fixes and cleanup of a lot of code.

About two weeks ago we had some planned maintenance to move our servers from one rack to another. Let's just say that this did not go as planned. At all. And here is the story...

Something that I cannot highlight often enough, but never did in writing is, that the IPFire Project is entirely self-hosted. We host all services for our developers and users ourselves. We do not use any big services from any third-parties and never share any user-data.

This is a downtime notification for all IPFire services. We are going to move our servers from one data center to another one and will take the whole project offline during that time.

This is the official release announcement for IPFire 2.23 - Core Update 134. This update ships security fixes in the Linux kernel for the "SACK Panic" attack as well as some other smaller fixes.

This is a different kind of announcement today. Unfortunately our service provider for credit card payments has disabled our account without any further notification. That means we can no longer collect donations via credit card or direct debit. If you have a bank transfer set up, you are fine.

the kernel maintainers have added an additional patch for the TCP SACK fixes so we had to update the kernel again to 4.14.131

Just one day after we have released IPFire 2.23 - Core Update 133, we are testing the next one which contains fixes for the famous SACK vulnerability.

It is time for the next Core Update. Number 133! Another bug-fix release with many changes under the hood. As always, we recommend to install this update as soon as possible to benefit from the fixes and to help us keeping those coming and to support our developers, please donate now!

Hello,

it is time for the next Core Update. Number 133!

This is another follow-up post on the Intel processor vulnerabilities. Yay. With more bad news. Yay!

The next version of IPFire is ready: IPFire 2.23 - Core Update 132. This update contains various security fixes and improvements to secure systems that are vulnerable to recently-published problems in Intel processors.

Hi,

less than a week after the release of the new Intrusion Prevention System was released, and here we are with a packed new update: It contains security fixes for the latest vulnerabilities in Intel processors and ...

This is an important announcement with an upcoming change in the next Core Update of IPFire.

Finally, we are releasing another big release of IPFire. In IPFire 2.23 - Core Update 131, we are rolling out our new Intrusion Prevention System. On top of that, this update also contains a number of other bug fixes and enhancements.

Hello fellow testers,

I would like to let you know that we have updated the latest Core Update in the testing branch. Some bugs have been found and fixed because of the help of you, but now you need to make sure that they are also fixed on your systems.

Finally, the next major version of IPFire is ready to testing. We consider our new Intrusion Prevention System such an important change, that we are calling it "IPFire 2.23" from now on. This update also contains a number of other bug fixes and enhancements.

Just a couple of days after the release of IPFire 2.21 - Core Update 130, the next release is available. This is an emergency update with various bug fixes and a large number of security fixes.

Just a couple of days after the release of IPFire 2.21 - Core Update 130, the next release is available for testing. This is an emergency update with various bug fixes and a large number of security fixes.

This is the official release announcement for IPFire 2.21 - Core Update 129 - an update that introduces routed IPsec VPNs and comes with various other changes that update the core system and fix several bugs.

With the next IPFire release, we are going to release huge changes to our Intrusion Detection System. Those bring packet analysis that IPFire does to a new level and we are very excited to tell you more about it in this announcement!

The next release is available for testing - presumably going to be last release in the 2.21 series before we bring some bigger changes. This update has a huge number and significant changes for IPsec as well as many updates to the core system and various smaller bug fixes.

The forthcoming Core Update will have some brilliant changes to our IPsec stack.

This is the official release announcement for IPFire 2.21 - Core Update 128; another maintenance update with a brand new kernel, introducing TLS 1.3 throughout the whole system and of course a whole package of bug fixes and other improvements.

Hello community,

we have a great bunch of updates lined up for you with some great features that will improve IPFire's IPsec VPN capabilities and a huge make-over for our Intrusion Prevention System. But before that, we have another maintenance update with a new kernel, introducing TLS 1.3 throughout the whole system and of course a whole package of bug fixes and other improvements.

The first update of the year and it is packed with loads of new features, many many performance improvements as well as some security fixes. This is quite a long change log, but please read through it. It is worth it!

New year, new update ready for testing! We have been busy over the holidays and are bringing you an update that is packed with new features and many many performance improvements.

The number of security vulnerabilities is rising. 2018 is another record year. There is a couple of theories why that is: Some say it is only more vulnerabilities being reported. Others are saying more money is being spent on finding vulnerabilities. What ever it is, it is a positive thing. Every vulnerability that is found can be fixed and not be used as a zero-day vulnerability.