| From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
|---|---|
| To: | Adam Scott <adam(dot)c(dot)scott(at)gmail(dot)com> |
| Cc: | Vinicius Santos <vinicius(dot)santos(dot)lista(at)gmail(dot)com>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: Autosave in the SQL Editor |
| Date: | 2012-08-07 09:11:05 |
| Message-ID: | 1344330665.1964.17.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Mon, 2012-08-06 at 20:30 -0600, Adam Scott wrote:
> MySQL Workbench has a similar feature.
>
> This does pose an exposure to save sensitive information without the user
> knowing. How to solve this? A complicated development path: encrypt saved
> document.
We won't go that road for sure. Too complicated, too easy to make it
worse.
> Of course any of the files the user saves should be privileged
> to that user (not group). So another method may be just to make sure the
> file's privileges are for the user only.
This is the minimum we can do.
--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vinicius Santos | 2012-08-07 11:44:54 | Re: Autosave in the SQL Editor |
| Previous Message | Guillaume Lelarge | 2012-08-07 09:10:18 | Re: Autosave in the SQL Editor |