It is basically the same vulnerability exploited with a different socket call. The initial fix in 2.6.1 only prevented a specific case, the fix in 2.8.1 should cover all cases.
You can either upgrade to 2.8.1 or only get the changes from the specific commit.
Any release date planned for 1.1.3?
-
hi, I need a new feature that was merged in master branch. As we know, master branch is always unstable and so I am hoping to work on a stable tag. So two questions below:
- Is there any release date planned for v1.1.3?
- What is v1.1.3-auto.x? Is it stable, i.e. pass the unit tests?
Thanks, please advise me.
-
-
@baris said in Any release date planned for 1.1.3?:
Next release is going to be 1.2.0 and it will be available
Thanks @baris. While waiting, may I ask what about 1.1.3-auto.x? Is it stable?
-
@Bruce-Lee those are just weekly snapshots of master branch. Those are most likely less stable than master.
I don't understand why they are even created and what purpose they serve.
-
@pichalite said in Any release date planned for 1.1.3?:
@Bruce-Lee those are just weekly snapshots of master branch. Those are most likely less stable than master.
I don't understand why they are even created and what purpose they serve.
Thanks @pichalite, i guess i have to wait for the release then.
