noVNC Snap needs regular rebuild for updates

[tkedwards]

I got this notification from Ubuntu's Snap store. Does noVNC use libssl at all? if so the Snap package might need a rebuild

A scan of this snap shows that it was built with packages from the Ubuntu
archive that have since received security updates. The following lists new
USNs for affected binary packages in each snap revision:

Revision r22 (amd64; channels: edge)

• libssl1.1: 5328-1

Revision r8 (amd64; channels: stable, candidate)

• libssl1.1: 5328-1

Simply rebuilding the snap will pull in the new security updates and
resolve this. If your snap also contains vendored code, now might be a
good time to review it for any needed updates.

Thank you for your snap and for attending to this matter.

References:

• https://ubuntu.com/security/notices/USN-5328-1/

[CendioOssman]

This has been a concern of mine ever since container solutions like snap started getting popular. The security issues will multiply enormously as every container needs to be constantly updated and rebuilt.

I've triggered a re-run of the latest snap publishing action, which should update edge.

But other than that I'm afraid I'll consider these things to be a fundamental design bug of snap and working around this would be a feature on our part. So I'm marking this as a feature request for finding some way to automatically update snaps.

[tkedwards]

Thanks

I think this is the first time since I made the Snap (2 years ago maybe?) that you've needed to manually trigger a rebuild. And Canonical does notify when a rebuild is needed for security updates. Hopefully it doesn't become too much of a regular thing