[...]
We will no longer waste time answering made-up facts. We will act and implement what we have announced in several previous posts.
Umm... you
do aware that though the post being quoted by
BitcoinGirl.Club was mine, that was fully intended to be answered by you? I can give my guess, but I'm afraid that'll be considered as a made-up facts. So, the podium is yours.
I was expecting an answer for them to be honest.
The front end stored the data [email and password], when it was sending insertion query to the database it encrypted the data. Anyone with direct access of the database can not read the data. It make sense.
When the front end is retrieving the data [email and password], it's reading the encrypted data and decrypting to perform different functions [checking user when sending login request, password reset, user information and many other things].
Betnomi have the same casino script [functional front end], and the database. Where is the problem?
Let's make it simpler.
Encryption is two way because you always need the original data to perform the functions you have associated with it.
In a web form password can be encrypted or hashed. Hash is one way. If I am not wrong [from my outdated knowledge], hash contains your password, a component called salt or sult and a key. When a database is compromised the salt or sult is compromised but the 128 [I suppose] bits key is not. Without the key you will never know the original password. Because of that developers prefers to store the hash instead of the password you given.
But for email and any other data, it is always encrypted [if it needs more security] and encryption are two way.
Considering the emails were encrypted, certainly it can be decrypted. I believe the team is still trying to mislead everyone or the person behind the account do not have such knowledge.
By the way, I do not have latest knowledge about the tech but anyone who is trustworthy and have programing knowledge, can confirm if I have mistaken anything to explain hash.