[Bug 1356739] Review Request: zulucrypt - Qt GUI front end to cryptsetup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=1356739

Raphael Groner <projects.rg@xxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Whiteboard|                            |NotReady



--- Comment #15 from Raphael Groner <projects.rg@xxxxxxxx> ---
(In reply to gil cattaneo from comment #14)
…
> > https://github.com/mhogomchungu/zuluCrypt/issues/41
> 
> perhaps, it would not be enough to add Provides: bundled(glibc) or what is
> ...
> also for this and should update license field

There's a patch now to use external glibc function. I'll apply it.

(In reply to Raphael Groner from comment #12)
> Created attachment 1180782 [details]
> unbundle lxqtwallet
> 
> Unbundle lxqt-wallet.
> 
> Patch got from upstream.

This patch is incomplete. I wrote an e-mail to upstream to get it working with
'rm -r zuluCrypt-gui/lxqt_wallet'.

(In reply to Raphael Groner from comment #11)
…
> 1. It is currently not possible to use upstream version of tcplay with
> zuluCrypt. Upstream seems to have lost interest in the project and i
> have extended my "personal" copy of the library in incompatible ways.
> For example,upstream version does not have this[2] pull request but my
> copy has it.My copy extended this pull request to add unlocking
> VeraCrypt volumes that uses a PIM value.A bunch of APIs like this[3]
> one are also not in the upstream version. Upstream seems uninterested
> in the project and i have not attempted to offer them upstream because
> of it.

We've to discuss that with the maintainer of the tcplay package. Maybe we can
add the patches and fully unbundle from the zuluCrypt package.

> 2. It should be possible to cleanly unbundle "lxqt_wallet" since
> zuluCrypt only uses lxqt_wallet documented API.Will add a config
> option shortly to build using an external version.

See above.

> 3. If you dont want to have zulu*-cli CLI components as suid-root
> binaries(offers best user experience in my opinion),look at what
> debian[4] is doing to have the second best user experience. With the
> "debian way",a user clicks an icon and they get a polkit prompt to
> root authenticate before they start the application with root's
> privileges but they still wont be able to do everything since the user
> that
> invokes the application is remembered and the application will do only
> what that user is allowed to do.This is done through pkexec[5].

IMHO that should be handled in another package review for zulucrypt-pkexec (or
the like) because it's a new upstream.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]