Dave F

SOLVED At long last i have finally managed to find a fix. I wont pretend i fully understand the problem but my issue appears to have been with the PAM configuration in my Debian 10 base image. Using the pam-auth-update command and selecting only profile 2 (systemd) allows Veracrypt to work.

At long last i have finally managed to find a fix. I wont pretend i fully understand the problem but my issue appears to have been with the PAM configuration in my Debian 10 base image. Using the pam-auth-update command and selecting only profile 2 (systemd) allows Veracrypt to work.

The reason I ask here is that it seems like my issue is directly related to one of the issues discussed is this thread https://sourceforge.net/p/veracrypt/discussion/general/thread/b738c75977/?limit=25&page=2 which seem to indicate an issue with how Veracrypt is using sudo to detect elevated permissions. As there have not been any posts about the issue recently, my hope was that users here either solved or worked around the issue and would be able to provide me with guidance. While docker may be...

I hate to keep bumping this but I have been stuck with this issue for quite some time and I am out of ideas. Any help would be appreciated.

Anyone?

I am the maintainer of a veracrypt docker image and i am having some issues updating my image to use veracrypt 1.24. My current stable image is based on debian 8 with an s6-overlay and veracrypt 1.23. As debian 8 no longer appears to be supported I am transitioning to a debian 10 base image (though debian 9 didnt work either). I believe the issue I am running into is either related to or exactly the issue mentioned here https://sourceforge.net/p/veracrypt/discussion/general/thread/b738c75977/?limit=25&page=2....

I am the maintainer of a veracrypt docker image and i am having some issues updating my image to use veracrypt 1.24. My current stable image is based on debian 8 with an s6-overlay and veracrypt 1.23. As debian 8 no longer appears to be supported I am transitioning to a debian 10 base image (though debian 9 didnt work either). I believe the issue I am running into is either related to or exactly the issue mentioned here https://sourceforge.net/p/veracrypt/discussion/general/thread/b738c75977/?limit=25&page=2....

I am the maintainer of a veracrypt docker image and i am having some issues updating my image to use veracrypt 1.24. My current stable image is based on debian 8 with an s6-overlay and veracrypt 1.23. As debian 8 no longer appears to be supported I am transitioning to a debian 10 base image (though debian 9 didnt work either). I believe the issue I am running into is either related to or exactly the issue mentioned here https://sourceforge.net/p/veracrypt/discussion/general/thread/b738c75977/?limit=25&page=2....