Postponed (maintainer needs more info)
Project:
Hosting Database Login
Version:
6.x-1.0-alpha2
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Nov 2013 at 14:43 UTC
Updated:
3 Feb 2014 at 07:55 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
helmo commentedComment #2
helmo commentedJust had another idea...
It might be better to get phpMyAdmin access to the database of only one site.
The database specific user/password is only known in drush context.
To bridge this I was thinking about a provision task that could be run to inject a password in the php session.
Big limitation is that the aegir user normally does not have access to the php session files... with good reason ;)
But that could e.g. be fixed with sudo.
Just thinking out loud here...
Comment #3
ergonlogicRight, we only want access to that site's db from the link on the site node. If we want to allow broader access as the 'aegir' user, then I'd suggest adding a similar link to the db_server node.
The whole point of redirecting to the db_login path was to avoid having to store the site's db credentials on the Aegir front-end. The fact that we store the 'aegir root' credentials in the front-end is something anarcat and I have discussed trying to remove. So any solution that depends on these being available is questionable, imo.
Comment #4
ergonlogicIf you really want to do this, be my guest. But please make it optional, rather than default behaviour.
Comment #5
helmo commentedI also still have my doubts about the security ... I hope to run into a current phpMyAdmin team member this weekend on Fosdem.
Comment #6
helmo commentedI had a bit of discussion about this but I'm not convinced about the security... postponing for now.