You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suggest swapping e to x as it extract with full paths. Sometimes there are nested directories within a ZIP and it can be cumbersome if those are just flattened upon extracting.
I think it would also be great to extract the archive into a directory with its same name similar to how when you right click an archive it says extract to [Archive Name]\
The text was updated successfully, but these errors were encountered:
@nadrojisk thanks your sharing your improvement ideas!
I suggest swapping e to x as it extract with full paths. Sometimes there are nested directories within a ZIP and it can be cumbersome if those are just flattened upon extracting.
I agree with this one!
I think it would also be great to extract the archive into a directory with its same name similar to how when you right click an archive it says extract to [Archive Name]\
How do you propose to implement this? The -o option allows to provide a directory name, but I am not sure how to get the zip name in the registry command. At the moment we use the argument %1.
Most of the zips with infected password I use are just a single malware binary zipped or a folder inside a zip. In both cases, I would personally find the extra directory annoying. @mandiant/flare-vm what do others think?
Details
Details
I suggest:
e
tox
as it extract with full paths. Sometimes there are nested directories within a ZIP and it can be cumbersome if those are just flattened upon extracting.[Archive Name]\
The text was updated successfully, but these errors were encountered: