Doug Barton writes:
> On 3/12/15 2:59 AM, Werner Koch wrote:
>> On Wed, 11 Mar 2015 18:23, dougb@dougbarton.email said:
>>
>>> PuTTY also has its own agent support, which works quite well. I'm not
>>> sure why it's necessary to reinvent the wheel here. :)
>>
>> Because that integrates seemless w
Another option that I often use is https://github.com/wesleyd/charade,
which opens a unix domain socket on cygwin, connected to Pageant, so
cygwin programs and windows programs that use PuTTY can share the same
authentication. Another similar program is
http://github.com/cuviper/ssh-pageant
On Th
On 3/12/15 2:59 AM, Werner Koch wrote:
On Wed, 11 Mar 2015 18:23, dougb@dougbarton.email said:
PuTTY also has its own agent support, which works quite well. I'm not
sure why it's necessary to reinvent the wheel here. :)
Because that integrates seemless with GnuPG. For example you can use
you
On Wed, 11 Mar 2015 18:23, dougb@dougbarton.email said:
> PuTTY also has its own agent support, which works quite well. I'm not
> sure why it's necessary to reinvent the wheel here. :)
Because that integrates seemless with GnuPG. For example you can use
your OpenPGP card (or other supoorted smar
Hi,
I am curious on how/if gpg4win integrates with Windows credential providers. We
at SafeNet have smart cards and middleware for our smartcard, SAC, registers
itself as a credential provider any Windows application that leverages MS
crypto libraries can integrate with it.
Can anyone help me
On 3/11/15 11:30 PM, Xavier Maillard wrote:
Doug Barton writes:
Otherwise, there is an easy way to solve your problem on the Windows
platform, you should strongly consider it.
I fear I do not understand. Did I miss something ? Off course I'd
rather go the easy way ! :D
Try reading my prev
Doug Barton writes:
> Otherwise, there is an easy way to solve your problem on the Windows
> platform, you should strongly consider it.
I fear I do not understand. Did I miss something ? Off course I'd
rather go the easy way ! :D
Regards
-- Xavier.
On 3/11/15 10:27 PM, Xavier Maillard wrote:
Doug Barton writes:
On 3/11/15 3:15 AM, Werner Koch wrote:
The standard ssh client on Windows seems to be Putty; you may use it
with the native GnuPG for Windows (i.e. Gpg4win) by using the option
--enable-putty-support instead of --enable-ssh-supp
Doug Barton writes:
> On 3/11/15 3:15 AM, Werner Koch wrote:
>> The standard ssh client on Windows seems to be Putty; you may use it
>> with the native GnuPG for Windows (i.e. Gpg4win) by using the option
>> --enable-putty-support instead of --enable-ssh-support.
>
> PuTTY also has its own agent
On 3/11/15 3:15 AM, Werner Koch wrote:
The standard ssh client on Windows seems to be Putty; you may use it
with the native GnuPG for Windows (i.e. Gpg4win) by using the option
--enable-putty-support instead of --enable-ssh-support.
PuTTY also has its own agent support, which works quite well.
I would like to second the request for this feature.
On Wed, Mar 11, 2015, 6:23 AM Werner Koch wrote:
> On Wed, 11 Mar 2015 07:18, xav...@maillard.im said:
>
> > I enabled ssh support in the gpg-agent.conf file as usual and I
> > clearly see the socket files for both GNUpg and SSH.
>
> The Unix
On Wed, 11 Mar 2015 07:18, xav...@maillard.im said:
> I enabled ssh support in the gpg-agent.conf file as usual and I
> clearly see the socket files for both GNUpg and SSH.
The Unix Domain Socket emulation used by Cygwin is different from the
emulation used by GnuPG on Windows. Recall that Cygwi
12 matches
Mail list logo
