[go: up one dir, main page]

User Activity

  • Posted a comment on discussion General Discussion on VeraCrypt

    @cwelzel: You should install latest macFUSE version 5.0.6 (https://macfuse.github.io/). This is what I used for my Tahoe mac Mini.

  • Posted a comment on discussion General Discussion on VeraCrypt

    @cwelzel: can you clarify what issue do you have with VeraCrypt on macOS Tahoe? Any error message? I personally installed and tested VeraCrypt 1.26.24 on macOS Tahoe (mac Mini M1) using both macFUSE and FUSE-T and I didn't encounter any issue.

  • Posted a comment on discussion General Discussion on VeraCrypt

    @redjones888: I cannot reproduce this issue on a cleanly installed Fedora 42. VeraCrypt rpm package explicitly depends on fuse-libs which provides libfuse2 library so its dependency is managed automatically by dnf. Obvisouly has messed up with your fuse installation since libfuse.so.2 should be present at /usr/lib64/libfuse.so.2 (you can check manually if the file is there). I would suggest to reinstall fuse-libs using the command: sudo dnf reinstall fuse-libs

  • Posted a comment on discussion General Discussion on VeraCrypt

    @activist4219: unfortunately, I don't have access anymore to an ARM64 device. I'm now resorting to cloud based ARM64 VM to do testing. Working on system encryption requires physical access to ARM64 machine and I cannot afford to buy one for VeraCrypt development. So for now, I can do nothing on this front. If one day I get access, I will resume working on it.

  • Posted a comment on discussion General Discussion on VeraCrypt

    @enigma2illusion: thank you for spotting this. I have fixed the issue. The correct filename is pbkdf2.html in lowercase.

  • Posted a comment on discussion General Discussion on VeraCrypt

    I have done tests on Tahoe using latest version of both MacFUSE and FUSE-T and I didn't encounter any issues. Tests were done after upgrading from macOS Sonoma on a Mac mini M1.

  • Posted a comment on discussion Technical Topics on VeraCrypt

    @nilchernek: the 4 issues you mentionned fall in two categories: pretest failure: this is most likely causes by the fact that the driver fails to locate the bootloader boot arguments necessary for the encryption. These boot arguments are stored in special memory regions that normally allow communication between the bootloader and the driver. It happens that on some machines the memory range used by VeraCrypt bootloader is overwritten by another driver on the machine because VeraCrypt driver could...

  • Posted a comment on discussion General Discussion on VeraCrypt

    @miked0a8sfdgafd Below is a screenshot of where the new option is located (I have changed how preferences are presented in the UI) A warning tooltip message is displayed when the mouse hovers over this new setting to explain its purpose.

View All

Personal Data

Username:
idrassi
Joined:
2009-12-13 21:54:49
Location:
Kobe / Japan / JST
Gender:
Male
Web Sites:
  1. https://www.idrix.fr
  2. https://amcrypto.jp

Projects

This is a list of open source software projects that Mounir IDRASSI is associated with:

  • Project Logo PC/SC Tracker Smart card events and smart cards information tracker Last Updated:
  • Project Logo RSA Converter   Last Updated:
  • Project Logo SCard4Wine Full Smart Card support for Wine Last Updated:
  • Project Logo SIM Card Manager Windows tool to read SIM card information and content Last Updated:
  • Project Logo VeraCrypt Open source disk encryption with strong security for the Paranoid Last Updated:

Personal Tools