Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64431 - [veracrypt] New hotfix1 version requires root permissions

Attached to Project: Community Packages
Opened by Musikolo (Musikolo) - Saturday, 09 November 2019, 03:56 GMT
Last edited by freswa (frederik) - Thursday, 19 March 2020, 12:36 GMT
Task Type Support Request
Category Packages
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I've noticed that the new hotfix1 version requires root permission to mount and unmount volumes. In my case, I'm mounting as a regular user a volume in my home directory, and I don't understand why root permission is now required for this. Same applies to the unmount operation. Reverting to the previous package version solves the issue.

In keeping with another thing, I found there is a new patch file (veracrypt-fix-u64-gcc.patch) which is not available in at https://git.archlinux.org/svntogit/community.git/tree/trunk?h=packages/veracrypt . When can we get it?

Thank you.
This task depends upon

Closed by  freswa (frederik)
Thursday, 19 March 2020, 12:36 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.24.update4
Comment by Levente Polyak (anthraxx) - Saturday, 09 November 2019, 10:33 GMT
that patch file it sownloaded on build.
If you have a non packaging related issue, its best to contact upstream instead
Comment by Musikolo (Musikolo) - Saturday, 09 November 2019, 15:16 GMT
Yes, you're right, I just saw it is at https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/veracrypt#n19 I don't know how I overlooked it, but thanks for the clarification!

In keeping with the root permissions issue, is there any reason for this new behavior?

Thank you!
Comment by Musikolo (Musikolo) - Saturday, 16 November 2019, 04:42 GMT
Same issue reported at https://sourceforge.net/p/veracrypt/discussion/general/thread/604d12bba8/

I hope a solution is found soon!
Comment by Musikolo (Musikolo) - Wednesday, 20 November 2019, 04:05 GMT
Same issue reported at https://sourceforge.net/p/veracrypt/discussion/general/thread/604d12bba8/

I hope a solution is found soon!
Comment by Levente Polyak (anthraxx) - Friday, 10 January 2020, 11:12 GMT
Is this still happening with 1.24.update3-1 ?
Comment by Musikolo (Musikolo) - Saturday, 11 January 2020, 02:34 GMT
Yes,

unfortunately, veracrypt-1.24.update3 still requires root password. :-(

EDIT:

I decided to give it another try I found a solution (https://sourceforge.net/p/veracrypt/discussion/general/thread/604d12bba8/#61f8).

Long story short, I had to change my `/etc/sudoers` configuration from:
`%users ALL=(root) NOPASSWD: /usr/bin/veracrypt`

to:
`users ALL=(root) NOPASSWD: /usr/bin/veracrypt, /usr/bin/uptime`

It's weird, but it solves the issue. I tried multiple times removing the the `uptime` command, and as soon as it do it, the root password is prompted again.

Thank you! :-)


Loading...