Can't upgrade cackey

[bengooch7]

Currently a hold is placed on the cackey package so that it isn't upgraded past version 0.7.5-1. Upgrading cackey breaks the functionality of this automation script.

Issues with this:

• Annoying warning from apt reminding you that a package is being held back
• Users can't upgrade their OS with packages held back and would need to either upgrade the package manually or remove it in order to upgrade OS versions. This breaks the functionality of CAC support across browsers.

NOTE: this can be fixed by removing cackey and rerunning this script, whch will reinstall the currently supported version and place the cackey package on hold again.

This method was the fastest way to provide a consistent solution. In the future, this will be remedied.

[Robaire]

Is there any reason that the location of the library must be in /usr/lib/libcackey.so/? Can the automation script simply be changed? Or a simlink to the new location placed in /usr/lib?

[bengooch7]

Hey Robaire,

I'm still looking into this. We recognize that holding back a package is not idea and it is high on our list of things to address.
I've poked this bear a little. I did try symlinks as well as setting different locations for the installation of the updated Cackey package.

Once this is addressed, we'll merge the change to the main branch.

[jdjaxon]

In all the testing that Ben mentioned, the browser either wouldn't identify the CAC middleware or it would cause the browser to freeze/crash. As mentioned, fixing this is on our todo list, but our primary focus is creating a stable script that accomodates both Firefox and Chrome. The fixes for Firefox on 22.04 will be merged soon, and we will then shift our focus to this issue.

[Robaire]

Ah okay. So there is a breaking change in the newer version itself, not just the fact that it has moved.

[bengooch7]

That does appear to be the case, yes. Ben Gooch - Sent from my Pixel 6 Pro

…

On Tue, Jun 14, 2022, 16:28 Robaire Galliath ***@***.***> wrote: Ah okay. So there is a breaking change in the newer version itself, not just the fact that it has moved. — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGLSFW34FR5S4HMCF75BRFTVPDTORANCNFSM5WFVNKVA> . You are receiving this because you were assigned.Message ID: ***@***.***>

[rquarry]

or it would cause the browser to freeze/crash

I believe you'll find that the Firefox crashing with versions > 7.5 issue is that the library isn't compiled with zlib support. Use ldd libcackey.so to check whether zlib support is included. Compiling from source with zlib-dev files fixes this issue. I'm currently running the library out of /lib64 with no issues.

[jdjaxon]

or it would cause the browser to freeze/crash

I believe you'll find that the Firefox crashing with versions > 7.5 issue is that the library isn't compiled with zlib support. Use ldd libcackey.so to check whether zlib support is included. Compiling from source with zlib-dev files fixes this issue. I'm currently running the library out of /lib64 with no issues.

Thank you! I'll look into a way to integrate this once I have time.