With both Windows and MacOS both putting scary warnings and hard to bypass blocking methods on improperly signed software this could eventually lead to developers being ransomed, “pay us big money or we will revoke your certificate”. This is not the only incident like this.
>this could eventually lead to developers being ransomed, “pay us big money or we will revoke your certificate” by whom? the platform makers (apple/microsoft) or malicious third parties?
Information on the revocation of WinRAR 5.91 digital certificate
31–40 of 156 posts
Re: Information on the revocation of WinRAR 5.91 digital certificate
#32Earlier quoted context omitted.
Yes. People who don't know any better alternatives continue to use it, and continue to recommend it to other people. So the cycle continues. Heck, WinZip still makes new releases so I'm sure people still use that too.
Or maybe their customers just like the product, as in the GUI and feature and don’t care that another compression algorithm can shave off a few extra megabytes. If I recall correctly WinRAR can make self extracting archives pretty easily. If you use that feature it might be easier/better to just continue using WinRAR. I love the fact that small software companies like RARLAB can still exist.
Re: Information on the revocation of WinRAR 5.91 digital certificate
#33> We think that revoking certificates based on questionable data discredits the certification system. It's hard to dispute this imo. There are many good reasons certificates should be revoked, but the reasoning should be 100% public information, for both the vendor and users who may have trusted the original certificate. I'm building a desktop app, and the process to even get a certificate is absurd. Each CA has thei…
Re: Information on the revocation of WinRAR 5.91 digital certificate
#34Anyone know which CA did this? I'd like to add it to my list of 'entities to avoid doing business with'.
Re: Information on the revocation of WinRAR 5.91 digital certificate
#35Earlier quoted context omitted.
Peazip: https://peazip.github.io/ I used to use 7zip, but switched when I discovered that Peazip doesn't extract to a temporary directory when extracting (thus, saving extra I/O work). It directly extracts into the target directory.
Is a file move that big of an IO operation?
Re: Information on the revocation of WinRAR 5.91 digital certificate
#36Earlier quoted context omitted.
> People who don't know any better alternatives continue to use it Genuine question: what are the better alternatives?
Peazip: https://peazip.github.io/ I used to use 7zip, but switched when I discovered that Peazip doesn't extract to a temporary directory when extracting (thus, saving extra I/O work). It directly extracts into the target directory.
I thought the creation of the files in the temp directory was an unavoidable artifact of how drag-and-drop worked in Windows. If peazip can get around this, I might check it out.
Re: Information on the revocation of WinRAR 5.91 digital certificate
#37Re: Information on the revocation of WinRAR 5.91 digital certificate
#38Earlier quoted context omitted.
Peazip: https://peazip.github.io/ I used to use 7zip, but switched when I discovered that Peazip doesn't extract to a temporary directory when extracting (thus, saving extra I/O work). It directly extracts into the target directory.
Is a file move that big of an IO operation?
Re: Information on the revocation of WinRAR 5.91 digital certificate
#39Re: Information on the revocation of WinRAR 5.91 digital certificate
#40Earlier quoted context omitted.
Peazip: https://peazip.github.io/ I used to use 7zip, but switched when I discovered that Peazip doesn't extract to a temporary directory when extracting (thus, saving extra I/O work). It directly extracts into the target directory.
Is a file move that big of an IO operation?
Moving many (small) files can also be quite slow