VB.Net generated Encryption DLL

[Solo712]

I have created a small string encryption DLL in VB Express 10 and tested it in 32-bit environment. Works fine. Could someone test it in a 64-bit version Office ? I would like to see if the "safeptr" gizmo will do the trick. Unfortunately I don't have access to a 64-bit version Office at the moment.

To register the DLL, do the following:
c:\windows\microsoft.net\framework\v4.0.30319[sub your version]\regasm.exe c:\[your path]\utilLibrary.dll /tlb:utilLibrary.tlb /codebase

You can go then to Tools>Reference and check the UtilLibrary entry.

There are two routines in the class, Encrypt and Decrypt. Declare the class variable like :

Dim enc As New UtilLibrary.EncryptBox

and then encrypt a string by

StringEncrypted = enc.Encrypt(String2Encrypt, KeyString)

and to restore the original string

String2Encrypt = enc.Decrypt(StringEncrypted, KeyString)

String2Encrypt is max 255 characters, the KeyString which locks and unlocks the first string can also be 255 characters. Longer KeyString assures stronger encryption. As the algorithm uses bit assembly / dispersion along the length of the buffer the encryption can be pretty strong.

I would like to see if I can use this utility for 64-bit Office with just a compiler directive switch. Thanks for any help !

Best,
Jiri

 

[Solo712]

I have created a small string encryption DLL in VB Express 10 and tested it in 32-bit environment. Works fine. Could someone test it in a 64-bit version Office ? I would like to see if the "safeptr" gizmo will do the trick. Unfortunately I don't have access to a 64-bit version Office at the moment.

To register the DLL, do the following:
c:\windows\microsoft.net\framework\v4.0.30319[sub your version]\regasm.exe c:\[your path]\utilLibrary.dll /tlb:utilLibrary.tlb /codebase

You can go then to Tools>Reference and check the UtilLibrary entry.

There are two routines in the class, Encrypt and Decrypt. Declare the class variable like :

Dim enc As New UtilLibrary.EncryptBox

and then encrypt a string by

StringEncrypted = enc.Encrypt(String2Encrypt, KeyString)

and to restore the original string

String2Encrypt = enc.Decrypt(StringEncrypted, KeyString)

String2Encrypt is max 255 characters, the KeyString which locks and unlocks the first string can also be 255 characters. Longer KeyString assures stronger encryption. As the algorithm uses bit assembly / dispersion along the length of the buffer the encryption can be pretty strong.

I would like to see if I can use this utility for 64-bit Office with just a compiler directive switch. Thanks for any help !

Best,
Jiri

Oops, ....did not notice that the attached file did not upload (it was an dll which it appears is not permitted on AWF). I have zipped it and am attaching it here.

Best,
Jiri