Re: using cocoon 2.1 in the long-term, security concerns

--000000000000c3673705c778c2fb
Content-Type: text/plain; charset="UTF-8"

The Tomcat version must be updated to address these concerns.

That should do it

On Mon, 19 Jul 2021, 13:03 Vincent Neyt, <[email protected]> wrote:

> Hi Cocoon users,
>
> I'd like to ask your opinion on the long-term security risks of running
> Cocoon on a server. The colleague responsible for the servers at my
> university is inquiring if the software I'm using for my website is up to
> date and is concerned that I'm using outdated software that could in the
> future pose a security risk.
>
> I'm using cocoon 2.1.11, which I could probably upgrade to 2.1.13 without
> many problems. But I'm concerned about the long-term, and wondering if it
> would perhaps be better to reprogram the website I've been working on for
> 10 years into eXist DB (which would be a huge time investment). I like
> cocoon very much and would love to continue using it if it's possible.
>
> I'm curious to hear your thoughts about using Cocoon 2.1 for the long
> term: will it still work well inside future versions of servlet containers
> like Tomcat? What about the java dependencies? And will cocoon 2.1 continue
> to put out updates when security risks are identified?
>
> thanks very much,
> Vincent
>

--000000000000c3673705c778c2fb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">The Tomcat version must be updated to address these conce=
rns.=C2=A0<div dir=3D"auto"><br></div><div dir=3D"auto">That should do it</=
div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Mon, 19 Jul 2021, 13:03 Vincent Neyt, &lt;<a href=3D"mailto:vincent.=
[email protected]">[email protected]</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex"><div dir=3D"ltr">Hi Cocoon users,<div><br></div><div>I&#=
39;d like to ask your opinion on the long-term security risks of running Co=
coon on a server. The colleague responsible for the servers at my universit=
y is inquiring if the software I&#39;m using for my website is up to date a=
nd is concerned that I&#39;m using outdated software that could in the futu=
re pose a security risk.<br><div><br></div><div>I&#39;m using cocoon 2.1.11=
, which I could probably upgrade to 2.1.13 without many problems. But I&#39=
;m concerned about the long-term, and wondering if it would perhaps be bett=
er to reprogram the website I&#39;ve been working on for 10 years into eXis=
t DB (which would be a huge time investment). I like cocoon very=C2=A0much =
and would love to continue using it if it&#39;s possible.</div></div><div><=
br></div><div>I&#39;m curious to hear your thoughts about using Cocoon 2.1 =
for the long term: will it still work well inside future versions of servle=
t containers like Tomcat? What about the java dependencies? And will cocoon=
 2.1 continue to put out updates when security risks are identified?</div><=
div><br></div><div>thanks very much,</div><div>Vincent=C2=A0</div></div>
</blockquote></div>

--000000000000c3673705c778c2fb--