| 1 |
On Wed, Dec 14, 2016 at 9:07 AM, M. J. Everitt <m.j.everitt@×××.org> wrote: |
| 2 |
> On 14/12/16 13:53, Mike Gilbert wrote: |
| 3 |
>> On Wed, Dec 14, 2016 at 7:56 AM, Mart Raudsepp <leio@g.o> wrote: |
| 4 |
>>> Ühel kenal päeval, K, 14.12.2016 kell 15:35, kirjutas Andrew Savchenko: |
| 5 |
>>>> This is not a workaround, but officially recommended practice, from |
| 6 |
>>>> man gpg-agent: |
| 7 |
>>>> |
| 8 |
>>>> You should always add the following lines to your .bashrc or |
| 9 |
>>>> whatever initialization file is used for all shell invocations: |
| 10 |
>>>> |
| 11 |
>>>> GPG_TTY=$(tty) |
| 12 |
>>>> export GPG_TTY |
| 13 |
>>> Then the packages or eselect pinentry or whatever should be taking care |
| 14 |
>>> of it, not have users have to mess with .bashrc to have stuff work. |
| 15 |
>> This is not practical. |
| 16 |
>> |
| 17 |
>> Adding it to the global /etc/bashrc is a bad idea. It would slow down |
| 18 |
>> every shell startup (fork/exec), even for users who do not actively |
| 19 |
>> use gpg (like root). |
| 20 |
>> |
| 21 |
>> Also, there is no way to know what shell each gpg user will be using. |
| 22 |
>> |
| 23 |
> Sounds to me like a perfect candidate for an elog/einfo, no?? |
| 24 |
|
| 25 |
Who reads those? ;-) |
| 26 |
|
| 27 |
It's not a bad idea though. |
Archives