-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/3/2014 5:21 AM, Rocki Hack wrote: > The point is that if you migrate from truecrypt to ciphershed with > windows system encryption enabled you must run the setup provided > by ciphershed just on top of truecrypt. > > The setup makes use of the code base and I think with rebranding it > will fail to detect that truecrypt is installed and/or can't read > truecrypt's settings. I think the best solution is to document all > changes very carefully and also note how they affect truecrypt / > ciphershed. Then adjust the setup to properly migrate from > truecrypt. I agree. We really need to understand how these strings are used. Constants that are effectively part of the volume format should not be changed, and those that are simply used for registry entry names probably should be migrated, or we should look for both. > This is a first draft of functions / constants we need to look at > very carefully. Thanks for tracking these down. Bill -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTtTP0AAoJEL9an3rWhBk+F0oP/RCHtHu2GXLZRj2OaQrf1LyM BJ2PGcFrgM2ViF5RxMskNG3Liq2MfWhyQTEpFKt+tQi5IhKi+wrsJEYDgqivssmV 6n4tE7q4A0h1trzYNHlb70uWWHmwpe5FgCpfMFKky2d1v8ffZeyW91fY6pmWCGiT YPPkGJvXFGN8gkP/zGkRbwPD/2NDF8Je2IjQqK03QXncVDWnXgDKaV6BGVMNeIOQ WAcKk5VCqPyC9WfWTP6lTSzEngPWdhciovm9nOqheveXUv3QRETgGoibv7xmTuuI QNwm1Du1oX6N7jqrNIQppmbc7uLKU6uLmzN8/cwca5c9+5vMHbkVfE+/hXjpVeri +f2V0FlY+2YqApuT+n5VUumc4+ARrSLtPmaEQLW/AcsmPEzNHdLuHlmPvRrwuPzj NZlhVYidkeqAiyl3WfMiwTUY4eVziemPgcVPheD1Asr5K3AVWglfcE6wN4EQCFok XV1otJqDyznRVhJxFOT7s+4h1aTzS7XdykiMfGXj7Huh5KdekD/bymc/UBrON++X LGAUq6+2s5GsdtippgAsMNfWK9FmxcKfxQ1Otx1zil//FLPMpgZM790d7UR1C4aC iThjc3OFEOJbqJWpd/IpmDeg9cSbpiamFeoRHLqq/grZ5lgy87L1nqfAjuAYK157 WdsE8uYmFct7Dd0S+kqJ =j6ku -----END PGP SIGNATURE-----