Files Encrypted under XP contain garbage under 2000 on dual boot! (yes certificate has been exported

[JamesC]

I have experimented loads with this and its definately happening. I
searched google and was surprised no one else has come across this.

I encrypted some folders on my d drive. Exported the certificate.
Rebooted into win2k (use system commander) and as expected could not
access the encrypted files on the d drive.

So I then imported the certificate (under ie6 Tools | internet options
| content | certificates | import) and CAN now open the encypted
files. However they contain total garbage!

As a test I made a new encrypted folder under 2000 (server) added a
simple text file, rebooted into XP and it can decrypt and read it
fine. Created a 2nd encypted text file in XP, went back to 2k and as
expected, it opens it BUT it's full of garbage.

I 'NEED' to dual boot for testing installs. My temporary solution has
been to stop using encryption. Is there a workaround for this or is it
best to just not use microsoft encryption. Seems a bit dangerous to
me. It's a very easily replicated problem, surprised my searches
turned nothing up.

NE1?

 

[JamesC]

Bloody typical, you search for hours, finally give up, post on the NG
then find this 'workaround' :-

http://support.microsoft.com/default.aspx?scid=kb;en-us;329741

Tested it on a folder with 2 files, works. Now to decrypt and
re-encrypt all those files - yawn...

So the M$hite default encryption setting in XP is something that isn't
backward compatable, now why doesn't that deja-vu feeling surprise me.

Anyway it's here in google groups for posterity, so hopefully others
won't suffer this anguish.

 

[Guest]

-----Original Message----- something that isn't
backward compatable, now why doesn't that deja-vu

feeling surprise me.

With encryption it shouldn't surprise you at all.
Encryption is an arms race with newer better algorithms
replacing older ones that have been broken or simply
don't stand up to the brute force attacks of newer
hardware. Expect to re-encrypt your files now and then
to keep them safe in the future.

 

[JamesC]

feeling surprise me.

With encryption it shouldn't surprise you at all.
Encryption is an arms race with newer better algorithms
replacing older ones that have been broken or simply
don't stand up to the brute force attacks of newer
hardware. Expect to re-encrypt your files now and then
to keep them safe in the future.

since when has public key encryption been hacked? I thought the
'square root of high primes 1 way function stuff' seemed pretty secure
when I studied it many years ago.

I'm saying that its not clever to set the 'default' so as XP is
incompat with 2K, or to NOT EVEN ASK would you like encyption back
compat with 2k, no a registry hack is required! now that's bullshit

Or alternatively why isn't there an upgrade patch for 2k so it can use
the newer encryption formats so necessary in this 'arms race'. I have
to admit I'm pretty confident that the 128bit keys on my relatively
unimportant data are safe. 256bit for data? c'mon! maybe for nasa

Anyway after about 12 hours I should be back where I was, busy
re-encrypting after the registry hack. I doubt I'll be the first or
the last.