×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
David,
It has no way of knowing whether the "password" or "key" you provided is "the right one." Encryption and Decryption is just a mathematical transformation of the data ... using one of several algorithms, such as AES ...
So, if you give it the wrong key, "Garbage In, Garbage Out."
Welcome to the wild and wooly world of encryption. :-)
Enjoy.
Mark S. Waterbury
On Monday, November 18, 2019, 4:32:59 PM EST, David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
My gut says I'm missing something...
For compatibility sake, I'm running on 7.2.
I'm encrypting data in a char column (for bit data) using the SQL
ENCRYPT_AES function.
I use the DECRYPT_CHAR function to decrypt it.
If I use the correct password, it decrypts fine.
If I use the wrong password, it does not fail. SQLCOD and SQLSTATE are
both 0. The returned value is garbage.
Shouldn't the decrypt function, with a wrong password, set an error code?
david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
