Remember folks: You must provide your password to authorities in the U.K. if told to. Failing to provide your password to authorities will get you convicted of a crime.
Remember folks: You must provide your password to authorities in the U.K. if told to. Failing to provide your password to authorities will get you convicted of a crime.
@Faveing In the UK? Most definitely.
In the US? Most likely, but since IANAL I can only say I don't believe it is not settled by case law. Yet.
1K Toots, 254 Following, 973 Followers Β· <p>Just Ask</p>
@jason @omnipotens in the US, if it's not issued by a judge, it's not a court order (Imo, but IANAL).
On the other hand, NSLs...
3.24K Toots, 356 Following, 358 Followers Β· Based out of #Arizona. #Linux advocate. Gamer. Father. Technician @ #Intel Fab32. Getting old. Loves #chiptune and #metal #nobot please
Exactly! It should be noted that the non-hidden part shouldn't be a brand new, default OS installation as that would raise suspicion.
Another method would be using a live environment that encrypts all temporary data, whether in RAM or on disk. Having a password vault hidden and inaccessable 'somewhere' might make this more viable.
But in the end - this is mitigating a situation that shouldn't be there in the first place. Madness!
True that. I think hidden partitions aren't the best means to achieve opsec. Also, one shouldn't trust a sole method. Like TOR - even if properly used, if there is a vulnerability in the browser, the user and location info could be at serious risk.
The best bet - as far as I am concerned - is to design the opsec model to the particular situation, with the assumption that everything is comprimised from the start.