Review Request 129365: add encryption methods

[Burkhard Lück]

> On Nov. 11, 2016, 10:29 vorm., Elvis Angelaccio wrote:
> > File Attachment: create-protected-archive.png - create-protected-archive.png
> > <https://git.reviewboard.kde.org/r/129365/#fcomment607>
> >
> >     What about splitting this screenshot into 3 different ones? Each one would have only one section expanded (Compression, Password Protection and Multi-volume Archive)

I am unsure if it makes sense to have 3 screenshots here, all possible options are shown in the uploaded screenshot. But I am open for your suggestion.

@ Documentation team: please comment on this issue.


> On Nov. 11, 2016, 10:29 vorm., Elvis Angelaccio wrote:
> > doc/index.docbook, line 340
> > <https://git.reviewboard.kde.org/r/129365/diff/1/?file=484492#file484492line340>
> >
> >     Technically only zip and *only with the p7zip backend*, but I supposed this can be omitted since p7zip is supposed to be the default. Btw we should also add a warning messagewidget in the dialog, since a zip with AES256 encryption cannot be unpacked by infozip's unzip.
> >     
> >     Not sure if this should be in the docbook...

> Technically only zip and only with the p7zip backend, but I supposed this can be omitted since p7zip is supposed to be the default. 

Too technical for Joe User, and if p7zip is the default, we do not need to add this info here.

> Btw we should also add a warning messagewidget in the dialog, since a zip with AES256 encryption cannot be unpacked by infozip's unzip.

In recent ark master build from sources AES256 encryption as default for zip archives with password protection, 
but if a zip with this encryption cannot be unpacked by infozip's unzip, ark should offer another default encryption method for interoperability.
If the user selects an uncommon option here, he should get a warning about possible problems opening this archive in other programms than ark. 
> Not sure if this should be in the docbook...

We should add a warning about encryption methods which cannot be processed by common archive programms.
AES128, AES192, AES256 and ZipCrypto are the available options, which are safe for interoperability, which are not?


- Burkhard


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/129365/#review100773
-----------------------------------------------------------


On Nov. 9, 2016, 8:46 nachm., Burkhard Lück wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/129365/
> -----------------------------------------------------------
> 
> (Updated Nov. 9, 2016, 8:46 nachm.)
> 
> 
> Review request for Documentation, KDE Utils, Elvis Angelaccio, and Ragnar Thomsen.
> 
> 
> Repository: ark
> 
> 
> Description
> -------
> 
> see summary
> update screenshot
> remove obsolete menuitem "Add Folder"
> 
> 
> Diffs
> -----
> 
>   doc/create-protected-archive.png abdec5d 
>   doc/index.docbook 0b9516e 
> 
> Diff: https://git.reviewboard.kde.org/r/129365/diff/
> 
> 
> Testing
> -------
> 
> passes checkXML5
> 
> 
> File Attachments
> ----------------
> 
> create-protected-archive.png
>   https://git.reviewboard.kde.org/media/uploaded/files/2016/11/09/45cda3df-d54d-4f66-a470-378763393c80__create-protected-archive.png
> 
> 
> Thanks,
> 
> Burkhard Lück
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-utils-devel/attachments/20161111/c31ac21e/attachment.html>