segfault:
> sajolida:
>> Testing VeraCrypt right now I see that on the main window there is an
>> option to "Mount" (which requires first selecting a file or device) but
>> also an option to "Auto-Mount Devices" (which autodetects my VeraCrypt
>> partition). segfault, I think you should have a look at what code is
>> running behind this "Auto-Mount Devices" button:
>>
>> https://www.veracrypt.fr/en/Home_VeraCrypt_Creating_Volume.png
>>
>
> According to the VeraCrypt documentation, the auto-mount option first
> prompts you to enter your password and then tries to decrypt *every*
> device and partition with it:
>
> https://veracrypt.codeplex.com/wikipage?title=Main%20Program%20Window#AutoMountDevices
Yeap, I understand that asking for the password first and then looking
for partitions that opens with it is the way that VeraCrypt found to
avoid false positives and false negatives. It's also one way VeraCrypt
users are used to interact with their volumes.
Deciding to do things similarly in Tails would probably have technical
benefits (in certainty of detection) and UX benefits (by matching what
people already do elsewhere). Now, I understand that this would require
having this VeraCrypt auto-mount feature always visible to people (even
if they are not using VeraCrypt) and this might be difficult to sell to
upstream who will be reluctant to add more visible features to everybody.
Definitely a problem to explore during our UX sprint...
%20but%0A>%20>>%20also%20an%20option%20to%20%22Auto-Mount%20Devices%22%20(which%20autodetects%20my%20VeraCrypt%0A>%20>>%20partition).%20segfault,%20I%20think%20you%20should%20have%20a%20look%20at%20what%20code%20is%0A>%20>>%20running%20behind%20this%20%22Auto-Mount%20Devices%22%20button:%0A>%20>>%0A>%20>>%20https://www.veracrypt.fr/en/Home_VeraCrypt_Creating_Volume.png%0A>%20>>%0A>%20>%20%0A>%20>%20According%20to%20the%20VeraCrypt%20documentation,%20the%20auto-mount%20option%20first%0A>%20>%20prompts%20you%20to%20enter%20your%20password%20and%20then%20tries%20to%20decrypt%20*every*%0A>%20>%20device%20and%20partition%20with%20it:%0A>%20>%20%0A>%20>%20https://veracrypt.codeplex.com/wikipage?title=Main%20Program%20Window#AutoMountDevices%0A>%20%0A>%20Yeap,%20I%20understand%20that%20asking%20for%20the%20password%20first%20and%20then%20looking%0A>%20for%20partitions%20that%20opens%20with%20it%20is%20the%20way%20that%20VeraCrypt%20found%20to%0A>%20avoid%20false%20positives%20and%20false%20negatives.%20It's%20also%20one%20way%20VeraCrypt%0A>%20users%20are%20used%20to%20interact%20with%20their%20volumes.%0A>%20%0A>%20Deciding%20to%20do%20things%20similarly%20in%20Tails%20would%20probably%20have%20technical%0A>%20benefits%20(in%20certainty%20of%20detection)%20and%20UX%20benefits%20(by%20matching%20what%0A>%20people%20already%20do%20elsewhere).%20Now,%20I%20understand%20that%20this%20would%20require%0A>%20having%20this%20VeraCrypt%20auto-mount%20feature%20always%20visible%20to%20people%20(even%0A>%20if%20they%20are%20not%20using%20VeraCrypt)%20and%20this%20might%20be%20difficult%20to%20sell%20to%0A>%20upstream%20who%20will%20be%20reluctant%20to%20add%20more%20visible%20features%20to%20everybody.%0A>%20%0A>%20Definitely%20a%20problem%20to%20explore%20during%20our%20UX%20sprint...%0A>%20%0A>%20 "Nachricht beantworten")
