7.10.10 not available via releases.rocket.chat

[abelbabel]

Hi,

when I try to download 7.10.10 release and signature asc (via https://releases.rocket.chat/7.10.10/download , https://releases.rocket.chat/7.10.10/asc ), I get "Access Denied". Is this service not available anymore?

Had similar issue with 7.10.5, 7.10.7, 7.10.8 and 7.10.9: #37587 (fixed), #38361 (fixed), #39467 / #39466 (unfixed so far), #39685 (fixed)

As with 7.10.8 and 7.10.9 the new release 7.10.10 contains a security fix. So updating is generally considered important - unless there is detailled report on the security issue and how it can be exploited and users can decide on their own.

I tried to get checksums on another way without success so far. Is there another way to verify that rocketchat-archives were transmitted unmodified from creator to user?

Regards
abelbabel

[reetp]

Yup. Borked again.

[+] Running 1/1
 ✘ rocketchat Error manifest for registry.rocket.chat/rocketchat/rocket.chat:7.10.10 not found: manifest unknown: manifest unknown                                   1.5s 
Error response from daemon: manifest for registry.rocket.chat/rocketchat/rocket.chat:7.10.10 not found: manifest unknown: manifest unknown

Please note in your own situation that, though this won't fix it as it is borked in docker too, these are the only supported deployment methods now:

Docker/Kubernetes/Podman

You should migrate to one ASAP.

https://docs.rocket.chat/docs/deploy-rocketchat

Rocket.Chat provides no support for these additional deployment methods. Using them may lead to unexpected challenges or compatibility issues.

https://docs.rocket.chat/docs/additional-deployment-methods

Rocket.Chat provides no support for these alternative deployment methods. Using them may lead to unexpected challenges or compatibility issues. The recommended deployment methods are Docker and Kubernetes.

(Don't shoot the messenger)

[reetp]

Yup @casalsgh someone needs firing.

This is just unacceptable on a supposed 'Secure' system.

Absolute joke.

[scuciatto]

Checking it.

[reetp]

Checking it.

Same longstanding issue that has had a fix promised since doomsday.

Just unacceptable for security fixes to be missed like this.

If it happened in my biz there would be a lot of black bags available for ex staff.

Where's Q&A to check the pushed fix worked across the 6/7 supported versions actually worked? In a training meeting, or a long lunch?

Apart from our wasted time, it is just plain embarassing for a supposedly "Secure" app.

This should never, ever, EVER, happen again.

[scuciatto]

Fixed. The image is now available.