Hi there,
I have a simple bit of VBcode in my database which reads the password a user enters and 'encrypts' it for storing in the user table. It's more obfuscation than encryption to be honest, and I feel limited by the 'text' data type assigned to the password field.
At the moment it works by taking the password entered, and converting the whole lot into a byte array, then for each 'character' in the array, changing its binary value. At the moment it's then converted back into a string and dumped into the 'password' field, as garbage characters. But they are still characters, and if I go out of range of the character set it results in horrible errors
.
I feel I may be missing the blindingly obvious and could just not convert it back to string, and write the binary into a text field instead, but I'm not sure how I'd get intelligible data back.
The reason it's not exactly encryption is because the key is the same for all characters on all passwords (I just multiply the binary value by 2!) what I want is to have a key as well, stored in another field alongside, but again can't implement this due to character-set range issues.
So my question is - is there a 'raw' data field hidden somewhere amongst the features of microsoft access, or should I be thinking about just storing the numbers themselves? For the moment I'll investigate the latter, but I'll appreciate any help! Thanks
I have a simple bit of VBcode in my database which reads the password a user enters and 'encrypts' it for storing in the user table. It's more obfuscation than encryption to be honest, and I feel limited by the 'text' data type assigned to the password field.
At the moment it works by taking the password entered, and converting the whole lot into a byte array, then for each 'character' in the array, changing its binary value. At the moment it's then converted back into a string and dumped into the 'password' field, as garbage characters. But they are still characters, and if I go out of range of the character set it results in horrible errors
.I feel I may be missing the blindingly obvious and could just not convert it back to string, and write the binary into a text field instead, but I'm not sure how I'd get intelligible data back.
The reason it's not exactly encryption is because the key is the same for all characters on all passwords (I just multiply the binary value by 2!) what I want is to have a key as well, stored in another field alongside, but again can't implement this due to character-set range issues.
So my question is - is there a 'raw' data field hidden somewhere amongst the features of microsoft access, or should I be thinking about just storing the numbers themselves? For the moment I'll investigate the latter, but I'll appreciate any help! Thanks
