Bug 25633 - veracrypt requires the sudo package and adding user in wheel group
Summary: veracrypt requires the sudo package and adding user in wheel group
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-10-29 17:25 CET by Sébastien Bore
Modified: 2019-10-30 21:35 CET (History)
2 users (show)

See Also:
Source RPM: veracrypt-1.23-1.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Sébastien Bore 2019-10-29 17:25:57 CET
Description of problem:Hello whitout sudo package,  Veracrypt does not work properly, and when editing a disk, and after filling in the password area a "sudo" elevation error appears.
https://fsociety-drive.mycozy.cloud/public?sharecode=jRQlRm76OLqC
After installing the package sudo, and adding the user in wheel group, Veracrypt running smoothly.

Version-Release number of selected component (if applicable):


How reproducible:
Install Veracrypt, mount a disk, after the password, the error message appear.

Steps to Reproduce:
1.install veracrypt
2.mount a disk
3.typing the password
Comment 1 Lewis Smith 2019-10-29 20:46:39 CET
Thank you for reporting this.
Certainly veracrypt does not currently require sudo. Looks like a packaging issue.

Assigning to its registered maintainer neoclust.

Assignee: bugsquad => mageia

Comment 2 David GEIGER 2019-10-29 20:47:39 CET
Why adding the user in the wheel group?

CC: (none) => geiger.david68210

Comment 3 Sébastien Bore 2019-10-29 22:21:13 CET
(In reply to David GEIGER from comment #2)
> Why adding the user in the wheel group?

Hello David,

I am at the origin of this package under Mageia. Nicolas had the kindness to integrate it to the distribution.
However, Veracrypt has always needed either an entry in the sudoers file (which I believe is deprecated?), So the way around was to register the user in the group wheel.
I admit to doing it more by reflex / habit.
Comment 4 David GEIGER 2019-10-30 06:48:54 CET
So you can test upcoming veracrypt-1.23-1.1.mga7 in Core/Updates_testing!

Make sure veracrypt and sudo are uninstalled and see when you install this new update if it pulls "sudo" and also if a note is showed to tell users to add themselves to the wheel group on new installs.
Comment 5 Sébastien Bore 2019-10-30 07:58:56 CET
Hello David,
Thank you very much for your investment in distribution, as well as to all other contributors.
I try this tonight as soon as I have access to my machine.
Comment 6 Sébastien Bore 2019-10-30 17:26:37 CET
(In reply to David GEIGER from comment #4)
> So you can test upcoming veracrypt-1.23-1.1.mga7 in Core/Updates_testing!
> 
> Make sure veracrypt and sudo are uninstalled and see when you install this
> new update if it pulls "sudo" and also if a note is showed to tell users to
> add themselves to the wheel group on new installs.

Hello,
After testing under a virtual machine created for the occasion, the notification to add to the user group appears correctly.
After restarting the Veracrypt system works perfectly.
However, is it possible to change the text of the notification, indicating that a restart / disconnection re-connection, will be necessary to take into account the addition of the user in the group Wheel?
because a new user, when first using Veracrypt before rebooting, may end up in front of this message without knowing what to do.

https://fsociety-drive.mycozy.cloud/public?sharecode=BY9SwgtaJFw0

 Simple assumption, otherwise the package no longer requires the installation of sudo.

Thank you all again for your availability.
Comment 7 David GEIGER 2019-10-30 18:11:19 CET
hmmm! adding my user to the wheel group switched my polkit password from the root one to the user's one, so this is not a good fix for veracrypt!
Comment 8 Sébastien Bore 2019-10-30 18:17:28 CET
I understand that leaving the keys of the house can cause problems.
What workaround to use in this case?
I believe the sudoers file is no longer using?
Comment 9 David GEIGER 2019-10-30 18:29:30 CET
Can you ask upstream, please? to see what they think about

https://github.com/veracrypt/VeraCrypt/issues
Comment 10 r howard 2019-10-30 21:28:27 CET
You might want to add to the discussion of this at https://github.com/veracrypt/VeraCrypt/issues/496

CC: (none) => rihoward1

Comment 11 Sébastien Bore 2019-10-30 21:34:20 CET
(In reply to David GEIGER from comment #9)
> Can you ask upstream, please? to see what they think about
> 
> https://github.com/veracrypt/VeraCrypt/issues

The question is asked ... :)

https://github.com/veracrypt/VeraCrypt/issues/533
Comment 12 Sébastien Bore 2019-10-30 21:35:58 CET
(In reply to r howard from comment #10)
> You might want to add to the discussion of this at
> https://github.com/veracrypt/VeraCrypt/issues/496

Sorry our messages are crossed.
I did not see this thread, so I created a new one.

Note You need to log in before you can comment on or make changes to this bug.