• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Direct Access of SQLite-DBs

D

Daniel Stefanovski

Guest
Hello,

I wonder if it is possible to directly write into Plesk's SQLite DBs. I found all the data related to Greylisting, Black-White-Listing, User-Auth and even unencrypted Passwords in sqlite.db-Files.

All it needs is Shell Access. I don't want to talk about the Security-Aspect here, I just wonder if the Plesk-Panel takes note of changes directly written to DB or if there's some extra synchronization mechanism between psa-Panel and and DB Contents.

I want to proivide a small Tool that uses Qt's SQLite-Capabilities to perform Queries and write into Greylisting-DB. There's currently nothing available to even have a look at your Greylisting-DB or search for stuck Mail or do manual Unlocks and Locks.

I just can't understand what could be the problem with providing a little more control over your Mailserver. Who wants Greylisting as a black-box mechanism where you have no Possibility of interaction.

Previously I was using Haggy-Bears Greylisting-Manager but I don't know what's happening on the Server-Side when using it. It takes about 5 minutes to refresh the view or just list all the entries in Grey-DB (700+ User Scenrio). It even freezes the Apache process which produces Nagios-Alerts.

I made a Tool that just get's a copy of the db, enables working in a in memory DB and it queries the 17MB SQLite DB in no Time. Everything is instant and works like a charm. So what is the problem with that on the Plesk Server?

After all I just wonder if it's a possible way to manage the Server in the way I described or do I corrupt the server with this? I'm aware of loosing support and so on but I don't feel like this was a problem. I didn't even get support after paying a 50€ Ticket. 3 days after I solved the problem myself I received an answer "Do you still need help". "No I don't I just wanted to spend money"...Ridiculous!
 
Back
Top