You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2021. It is now read-only.
Encrypting key with another encryption + salt method so MariaDB can decrpyt/encrypt securely
Things to do:
Since latest XAMPP is using MariaDB 10.1.38 (the latest ver. ones is 10.3.14) and lacks plugin for that encryption work, i'll try to using this version 1st before MIGRATING to the latest ver.
Testing.
The text was updated successfully, but these errors were encountered:
hey I still don't know about it, but do MariaDB can be used on a native-browser-app or php docker or something like that that make this web app standalone?
hey I still don't know about it, but do MariaDB can be used on a native-browser-app or php docker or something like that that make this web app standalone?
ALL DB HAS BEEN ENCRYPTED WHEN ISN'T USED OR LOGGED IN
5 ROTATING KEYS AVAILABLE FOR MAKING ENCRYPTION ALGORITHM MORE HARDER TO BE ANALYSED
Hiding decryption priv key (this one needs extra attention since i cant using Amazon Web Service API for key management or other online service ) why? because private key needs to be separated from the host/server so attacker cant guessing/searching (via directory travesal,exploitable php function or even LFI but i already taking prevention for those vulns, maybe) key in localhost
Changing file permission for priv key and conf file
Things to do:
Making auto script to change the rotation of keys each specific time
Changing CBC to CTR (will try if CTR is supported) ❌
VULN FOR NOW
Since CBC is used, the table column name is still in plain text
DONT ASK THIS (IF YOURE ASKING THIS, THEN YOU'RE AN IDIOT)
Steps taken:
Things to do:
The text was updated successfully, but these errors were encountered: