Bug 1308683 - Password protected zips created with file-roller cannot be opened with Winzip.
Summary: Password protected zips created with file-roller cannot be opened with Winzip.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: file-roller
Version: 7.2
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David King
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-15 17:58 UTC by Guillaume Radde
Modified: 2019-09-23 18:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-23 18:29:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 739665 0 None None None 2016-05-04 10:07:01 UTC

Description Guillaume Radde 2016-02-15 17:58:02 UTC 
Description of problem:

Password protected zip files created with file-roller cannot be opened by Winzip.

This is a common way to securely email sensitive documents. Create a password protected zip file containing the documents, then email it. Unfortunately, the archive created by file-roller cannot be opened by Windows users using Winzip.

Version-Release number of selected component (if applicable):
file-roller-3.14.2-7.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a password protected zip archive using file-roller
2. Email it to a Windows user
3. Have the user open the password protected archive in Winzip.

Actual results:

Winzip will throw an error and won't open the zip.


Expected results:
Winzip should be able to open the zip.

Additional info:
This may be due to the encryption algorithm used by file-roller. 7zip offers 2 encryption methods (ZipCrypto and AES-256). ZipCrypto seems to be compatible with Winzip.
Note You need to log in before you can comment on or make changes to this bug.