Changed login behavior of version 1.26.20 compared to older versions under Linux

[ulip]

@idrassi: There is a change in the login behavior of version 1.26.20 under Linux compared to older versions:

As before, the password for unlocking the container must be entered first, but then - and this is new - the user's login password for mounting the container must be entered, too. It took me a while to realize this. Perhaps the change should be described in a prominent place in the documentation.

Am I the only one experiencing this change in behavior?
Please let me know if anyone else is experiencing this.

Greetings

System:
Kernel: 6.8.0-52-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc
Desktop: Cinnamon v: 6.4.6 tk: GTK v: 3.24.41 wm: Muffin v: 6.4.1 vt: 7 dm: LightDM v: 1.30.0
Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble

[ulip]

Addition: using --use-dummy-sudo-password I have the old behaviour before 1.26.20.
Is this intentional at least for Mint Version 22.1 ?

[Enigma2Illusion]

When searching the forum using the switch you posted, I discovered the developers explanation regarding Mint. See the developers post at the link below.

https://sourceforge.net/p/veracrypt/discussion/technical/thread/eeed16d53a/?limit=25#784a

In the same thread, another solution:

https://sourceforge.net/p/veracrypt/discussion/technical/thread/eeed16d53a/?limit=25#d909

[Mounir IDRASSI]

@ulip: are you using a NOPASSWD settings in your sudoers file to bypass user authentication?

For example, do you have the following:

user ALL=(root) NOPASSWD: /usr/bin/veracrypt, /usr/bin/uptime

If yes, then the issue is that version 1.26.20 don't use uptime anymore and instead uses true command in order to check for active sudo session.

This means you have to replace uptime by true in sudoers:

user ALL=(root) NOPASSWD: /usr/bin/veracrypt, /usr/bin/true

A user on Github already shared this issue and he was using this trick to bypass user authentication in VeraCrypt, so I shared with him the solution and he confirmed that it works: https://github.com/veracrypt/VeraCrypt/issues/1498#issuecomment-2661644318

I will update the online version of Release Notes to mention the switch from uptime to true.

[ulip]

@idrassi: thanks a lot for that information. It works like a charme.
Using --use-dummy-sudo-password is not neccessary no more.