I have a perfectly normal hidden volume inside my encrypted volume; I did set it with some values for its startpoint and endpoint. Whenever I require “configure hidden volume” now, I see something I expect : the interface behaves like for a fresh start, ignoring the existing hidden volume.
But when I ask to unlock the existing hidden part, giving the right password, while I am not asked to indicate where it starts and ends, I see the app immediately finds these points.
My question is : how does the key remember the startpoint and endpoint of hidden volume(s)?
Even though this information is not accessible through the app interface, is it somehow stored in the key? (with the risk of cancelling the ‘deniability’)
Or is there some astute process where the app, once given the hidden password, would try each and every location till it finds something worth?
(question is not urgent)