What is a good Windows XP file to store encrypted volumes

What is a good Windows XP file to store encrypted volumes

Secure Home | Search | About
 Computer Software Security    Post an article   get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content add this group's latest topics to your Google content
Subject Author Date
What is a good Windows XP file to store encrypted volumes Jane_G 01-19-2007
Posted by nemo_outis on January 20, 2007, 11:22 am
If you were  Registered and logged in, you could reply and use other advanced thread options

> nemo_outis wrote:
>
>> No, Sebastian, it was NOT I who specified the type of adversaries but
>> rather the OP


> And I told you that your misunderstood this specification. Now, what
> about reading comprehension? Go figure!



Here, you thick-as-a-brick moron, is a verbatim quote from the OP's post:
___

But, my question is what file name and location would arouse the least
suspicion were a coworker to be snooping around looking for my personal
data on my WinXP computer?"
___

"Snooping coworker," Sebastian! That's the specific threat model POSED
BY THE OP just as I said. It was the OP, not I, who specified the threat
model (and who additionally even confined the "solution space" only to
recommending the most inconspicuous file type and location).


>> If the adversaries suspecting use of Truecrypt had even minimal
>> competence they would first try, NOT to pore through the HD looking
>> for oversized mislabelled nonfunctional files
>
> Right. He would use Google to find a program which does that for him.


No ordinary "snooping coworker" would be installing and launching
forensic tools. Moreover, this hypothetical NSA-geek snooping coworker
would not know if there were mislabelled files, alternate data streams, a
hidden partition, an even-more-hidden partition in the HPA, files or
directories hidden by a rootkit, or even whether Truecrypt or some other
program was being used.

Nor does the snooper know what method is used to hide the OP's personal
info or even if any such hiding is being done. He's just snooping
around.

And, in the absence of specific info, the NSA-geek snooping coworker
would have no basis for limiting himself to searching for only one of
these stratagems but would either have to use a full-blown forensic tool
(e.g., Encase) to look for any and all of them or deploy a quiver of more
specific search tools. That isn't casual snooping, Sebastian!

No, a casual snoop will do just that: snoop around hoping to stumble upon
unsecured personal data or, failing that, to spot some anomaly that
catches his eye as a possible attempt to hide personal info. A slightly
less casual snoop may use some of the tools native to the environment
(e.g., regedit) but anything beyond that (e.g., installing and using
forensic ttools) is no longer casual snooping.

That's it, Sebastian. That's all the OP asked for: light-duty
camouflage. Nothing more.

But I'll go further, Sebastian, you doofus, in explaining that there is
NO satisfactory way of hiding Truecrypt from a skilled adversary, only
makeshift methods of hiding it from unskilled ones (such as the ones
asked for and given to the OP).

If you're of a mathematical bent call it a mini "existence proof" from
the makers of Truecrypt themselves. Perhaps it will even satisfy David
Eather's pretentious twaddle calling for "mathematical proof or a
conjecture of the computational bounds of an adversary."

You see, Sebastian, Truecrypt goes to great lengths to provide "plausible
deniability," even adding a nesting feature. But obviously "plausible
deniability: is a far weaker status that "undetectability of hidden data
in the first place." If the makers of Truecrypt thought there was an
effective way of providing undetectability they would not have futzed
around adding plausible deniability. QED

Regards,


Posted by David Eather on January 19, 2007, 10:41 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
nemo_outis wrote:
>
>> nemo_outis wrote:
> ...
>>> The following will not fool a sysadmin (well, not a good one) but it
>>> works very well against casual or inept snoops.
>>>
>>> Hide the Truecrypt file as an "alternate file stream" attached to
>>> some other file (which could itself be perfectly functional, such as
>>> an Excel file). The hidden stream will not show in any normal system
>>> operation (directory listings, etc.) although some (by no means all)
>>> antivirus software may report it.
>>>
>>> If the ordinary file you wish to use is, say,
>>> C:\directorypath\somefile.xls then create (and subsequently mount
>>> and use) the Truecrypt file as, say, C:
>>> \directorypath\somefile.xls:tc (i.e., the alternate file name -
>>> extent, really - is defined as prefixed by the regular file name and
>>> a colon)
>>>
>>> Regards,
>>>
>>>
>>>
>> So, your saying it is OK that your security is not based on a
>> mathematical proof or a conjecture of the computational bounds of an
>> adversary, but rather based on the hope that the adversary is
>> incompetent.
>>
>> Do you see anything wrong with that?
>
>
> Short answer: No, I see nothing wrong with that.
>
> Longer answer:
>
> The OP framed her question in terms of using nothing stronger than an
> inconspicuous file. Compared to that, an alternate data stream is
> leagues ahead.
>
> Going further, the OP's threat model is coworkers who casually snoop,
> folks who are, if not outright incompetent, clearly without special
> resources or competence.
>
> Against a sufficiently competent, well-funded, and motivated adversary -
> especially one who has repeated unobserved direct access to the machine
> as could happen in a work environment - I fell confident in saying there
> is NO satisfactory method of disguising the use of Truecrypt.
>
> So, the task is not to overdesign the system inordinately in a misguided
> attempt to thwart the NSA. Instead, as with most security questions, the
> real task is to implement a scheme appropriate to the specified threat
> model.
>
> And this is exactly what my suggested use of ADS in these circumstances
> does. It is a convenient, readily implemented method that is entirely
> suitable and appropriate for the described threat model.
>
> Regards,
>
>
The rub:

The adversary is not the NSA. You saw how quickly SG was onto the
faults in this idea. It will only take one person who knows what he is
doing, to show one script-kiddie what to do, who will show everyone else
and security becomes zero or even worse; the user still thinks they have
some security and may well be indiscreet.

Posted by nemo_outis on January 20, 2007, 12:08 am
If you were  Registered and logged in, you could reply and use other advanced thread options

> The adversary is not the NSA. You saw how quickly SG was onto the
> faults in this idea. It will only take one person who knows what he
> is doing, to show one script-kiddie what to do, who will show everyone
> else and security becomes zero or even worse; the user still thinks
> they have some security and may well be indiscreet.


Once again, with feeling:

The method I outlined is entirely appropriate to the threat model specified
by the OP: casual office snoopers. It is significantly superior to the
grossly oversized, non-functional, muslabelled file ruse. Moreover, it is
exceedingly straightforward and easy to implement since Truecrypt natively
supports it with nary a tweak required (an important aspect given the
obvious non-geekiness of the OP).

And here's a flash for you: There is NO satisfactory method of hiding
Truecrypt from a skilled adversary, especially on a workplace machine. As
just one example, Truecrypt leaves awkward-to-erase tracks in the registry.
An adversary of only modest skills using regedit would detect that
Truecrypt was being used in seconds rather than having to do a full HD scan
looking for ADS with special programs.

Regards,






Posted by vedaal on January 19, 2007, 11:29 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Jane_G wrote:

> To contain the TrueCrypt encrypted volume, I can choose any file name and
> location that doesn't already exist. But, my question is what file name and
> location would arouse the least suspicion were a coworker to be snooping
> around looking for my personal data on my WinXP computer?
>
> Specifically what binary file could reasonable be expected to be a few
> megabytes in size, yet have a normal sounding name in a normal sounding
> location containing "gibberish" (ie encrypted data) that would not arouse
> suspicions that it is actually a TrueCrypt encrypted volume?


a .dll file in the windows system folder
[not high on the curious co-worker list of snoop folders ;-) ]
and there are so many of them that most people have no idea of what
they do,
or if they are legitimately required to be there

you can call it something benign and not unexpected, like
'AdobeUPD.dll'
(although i don't remember ever seeing a dll file 5mb or greater)


vedaal


Posted by =?ISO-8859-1?Q?j=F8rgen?= on January 19, 2007, 11:56 am
If you were  Registered and logged in, you could reply and use other advanced thread options
Jane_G wrote:
> What is a good filespec to hold an encrypted volume on WinXP?


If using NTFS, check up on alternate data streams

Similar ThreadsPosted
Any good free spyware scan that I can run in bat file so I can schedule it daily June 21, 2007, 10:32 am
Index.btr file in Windows XP Help please January 20, 2006, 12:56 pm
HELP. Windows file names changed September 29, 2006, 11:01 am
Evidence of file copy to external device on Windows 2000 / FAT 32 April 19, 2006, 4:05 am
Re: portably encrypting a file system's partition, directory and/or file November 25, 2005, 6:10 pm
Encrypted Anonymous Surfing January 1, 2006, 10:52 pm
Can you keep a secret? This encrypted drive can... October 30, 2006, 11:25 pm
Secure encrypted data backup? January 31, 2008, 3:10 pm
Encrypted backup of whole-disk encryption March 13, 2008, 11:50 am
Webmasterslookup launches Encrypted Messaging Service. March 10, 2008, 4:21 pm

The site map in XML format XML site map

Contact Us | Privacy Policy