Just to be clear here: The security fix affects dev only, installations
that are on the stable branch are not affected? Or would we need to upgrade
our production server to bleeding edge now to get this fixed? Sorry if the
answer to this may seem obvious, but I really need to make sure that this
doesn’t affect us right now, especially as I couldn’t find any specifics on
the severity of this issue.
last night I had to remove .019 to see.020 - applied (new) .019 and .020
.021 is showing up for me nowOn 25 June 2015 at 04:24, Lutz Lesener <@lutz> wrote:
Thanks!
FYI: I had to remove 4.5.1.020 in order to get the new version displayed.
rgds
Lutz
On Wednesday, 24 June 2015 21:53:06 UTC+2, info wrote:
There is a new patch release (4.5.1.021) available to install on the
“dev” update provider that also fixes a security issue.
You are right, you need to install the BER to get it fixed for the moment,
the same release is also available on the preview update provider, means it
is a candidate for the next stable release, that is scheduled this week, if
there are any reports of problems with that version.
MichaOn Thu, Jun 25, 2015 at 7:12 PM, Markus Wollny <@Markus_Wollny> wrote:
Hi,
Just to be clear here: The security fix affects dev only, installations
that are on the stable branch are not affected? Or would we need to upgrade
our production server to bleeding edge now to get this fixed? Sorry if the
answer to this may seem obvious, but I really need to make sure that this
doesn’t affect us right now, especially as I couldn’t find any specifics on
the severity of this issue.