Dirmngr and proxy

[John R. Shannon]

I did not include enough information.

 The outgoing message on 192.168.1.4 is to 192.168.1.4:80, indicating that the 
LDAP server is using the specified http-proxy IP address, but, not the port 
number.

On Monday 03 January 2005 10:17 am, Bernhard Reiter wrote:
> On Wed, Dec 29, 2004 at 03:09:36PM -0700, John R. Shannon wrote:
> > I have a network where all outgoing traffic must pass through a proxy
> > server. The proxy server, 192.168.1.4, runs both an http proxy at port
> > 3128 and an LDAP proxy (slapd) at port 389.
> >
> > Dirmngr on a client is running:
> >
> > /usr/pkg/bin/dirmngr --daemon \
> >     --http-proxy http://192.168.1.4:3128 \
> >     --ldap-proxy 192.168.1.4
> >
> > When I try a test signing the uses certificate with an http crlDP, I see
> > an outgoing message on 192.168.1.4 from the client to 192.168.1.4 that's
> > blocked by the firewall.
>
> Debug your firewall?
>
> Seriously: It seems fine behaviour from your description unless the port
> is wrong, so I guess you need to bring in more details before somebody
> can help you. (Or am I missing something obvious here?)

-- 
John R. Shannon
john at johnrshannon.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : /pipermail/attachments/20050103/ce2d5351/attachment.bin