Code Signing Hell, or Why VirtualGL 2.6.2 and TurboVNC 2.2.2 Haven't Been Released Yet
18 views
Skip to first unread message
DRC
May 22, 2019, 12:58:21 AM5/22/19
to virtual...@googlegroups.com, virtual...@googlegroups.com, turbovn...@googlegroups.com, turbovn...@googlegroups.com, libjpeg-t...@googlegroups.com, libjpeg-t...@googlegroups.com
Please read if you are an open source developer or are curious about why
the "pending" VirtualGL 2.6.2 and TurboVNC 2.2.2 releases are still pending.
https://virtualgl.org/DeveloperInfo/CodeSigningHell
In short, I've been hip-deep in attempting to obtain a code signing
certificate to replace the one that Thawte refused to renew (because
they no longer offer that product.) After a literal week's worth of
unpaid labor, investigating four different paths, and following two of
them for days until I ultimately reached impassable roadblocks, I had to
declare complete failure. Going forward, my only choice is to use a
self-signed root certificate for code signing JARs and Windows
installers. It will probably take another couple of days of unpaid
labor to set that up. Joy.
DRC
the "pending" VirtualGL 2.6.2 and TurboVNC 2.2.2 releases are still pending.
https://virtualgl.org/DeveloperInfo/CodeSigningHell
In short, I've been hip-deep in attempting to obtain a code signing
certificate to replace the one that Thawte refused to renew (because
they no longer offer that product.) After a literal week's worth of
unpaid labor, investigating four different paths, and following two of
them for days until I ultimately reached impassable roadblocks, I had to
declare complete failure. Going forward, my only choice is to use a
self-signed root certificate for code signing JARs and Windows
installers. It will probably take another couple of days of unpaid
labor to set that up. Joy.
DRC
Reply all
Reply to author
Forward
0 new messages