| bio | website | shiftedbits.net |
|---|---|---|
| location | Albuquerque, NM | |
| age | 26 | |
| visits | member for | 2 years, 1 month |
| seen | Aug 27 '12 at 21:39 | |
| stats | profile views | 9 |
Give me something to program. It'll make me happy.
|
Aug 30 |
awarded | Yearling |
|
Aug 30 |
awarded | Nice Question |
|
Aug 27 |
accepted | Keeping the password secret over regular http |
|
Aug 27 |
asked | Keeping the password secret over regular http |
|
Dec 9 |
comment |
Mysql - two-way encryption of sensitive data (email addresses) outside of Apache, PHP and MySQL The same idea applies. The idea would be then to generate a key pair using an administrator's password (ideally, one really good password which all admins know from outside the system) for any time a user's details need to be viewed. If you're looking to use that information within the system, say for sending out auto-generated emails, then well that's a bit (lot) more complicated to keep secure, as you have to store both sides of the key (or the password that made the key) for the system to decode the message. |
|
Nov 10 |
asked | Creating a Private Key using Human Intervention |
|
Apr 29 |
comment |
Different MySQL Users Security Benefits @Graham That won't make his answer any more relevant to the question I was asking... Though this is getting useless to argue, so I'm just gonna leave it be. |
|
Apr 29 |
awarded | Commentator |
|
Apr 29 |
comment |
Different MySQL Users Security Benefits Oh! Thanks for the pointer! I'll definitely be looking into that to see if I can apply it to my application. Thanks again! |
|
Apr 29 |
comment |
Different MySQL Users Security Benefits @ atdre: You did? Where? I don't see it. All you said was to use secure connections, mentioned that there's a bunch of other things about security, and then pointed me to a question that has no relation to what my question was about outside of mysql security. Sure the chosen answer there says something about separation of privileges, but it's not nearly as focused or in depth as a proper answer for what I was looking for. Seriously, your answer would have been better as a comment. |
|
Apr 28 |
awarded | Citizen Patrol |
|
Apr 28 |
awarded | Critic |
|
Apr 28 |
comment |
Different MySQL Users Security Benefits We're generally assuming that the secure stuff should already be happening. The question was not about general MySQL Security, but more or less the benefits of implementing the principle of least privilege on the database vs the cost of slightly more complicated code in the app level. |
|
Apr 28 |
accepted | Different MySQL Users Security Benefits |
|
Apr 28 |
revised |
Different MySQL Users Security Benefits edited tags |
|
Apr 28 |
comment |
Different MySQL Users Security Benefits This is very true. Since my case involves MySQL that's where the question originated. It can, at least in my head, be translated to other RDBMSes. |
|
Apr 27 |
comment |
Different MySQL Users Security Benefits Again, some excellent points. Thanks again. |
|
Apr 27 |
comment |
Different MySQL Users Security Benefits So you're saying that the concern should be placed more on the implementation of the idea, as the idea is apparently rather solid? Hmm. You bring up good points. Thanks for the answer! |
|
Apr 27 |
comment |
Different MySQL Users Security Benefits The sanitizer is on my list, and currently stands up to basic testing. Still looking in more places for new attack vectors to test, so that when it goes to production it'll at least be semi prepared to take on the real world. Thanks for the answer! |
|
Apr 27 |
asked | Different MySQL Users Security Benefits |