 |
 |
It is at the client side. XrdSecProtocolgsi::ClientDoCert() is called by client only. -- Wei Yang | [log in to unmask]<mailto:[log in to unmask]> | 650-926-3338(O) From: Andrew Hanushevsky <[log in to unmask]> Reply-To: xrootd/xrootd <[log in to unmask]> Date: Wednesday, December 5, 2018 at 10:30 PM To: xrootd/xrootd <[log in to unmask]> Cc: Wei Yang <[log in to unmask]>, Author <[log in to unmask]> Subject: Re: [xrootd/xrootd] Append signed Diffie-Hellman paramaters to the unsigned (#867) Ah, are you telling me this is a server-side issue? That is, the message only appears at the server? If so, I think this is a bit more complicated then. If it's a client-side issue then the check with turnoff is correct. On Wed, 5 Dec 2018, Wei Yang wrote: > I put it there and comment it out because I feel the message is quite misleading: In a TPC case, if the source does not send DH parameters (but the destination does), this message will come out, even though the client never intended to delegate the proxy to the source. > > I guess you are looking at this from debugging prospect while I am looking at it from user?s prospect. Is there an way to print out message only when XrdSecDEBUG is sent to something? > -- > Wei Yang | [log in to unmask]<mailto:[log in to unmask]> | 650-926-3338(O) > > From: Andrew Hanushevsky <[log in to unmask]> > Reply-To: xrootd/xrootd <[log in to unmask]> > Date: Wednesday, December 5, 2018 at 10:03 PM > To: xrootd/xrootd <[log in to unmask]> > Cc: Wei Yang <[log in to unmask]>, Author <[log in to unmask]> > Subject: Re: [xrootd/xrootd] Append signed Diffie-Hellman paramaters to the unsigned (#867) > > > Could you un-comment the message > > std::cerr <<"secgsi: proxy delegation forbidden when server does not provide signed DH parameter!\n" > > that indicates delegation was turned off. Without that message we will be chasing delegation problems for days. With the message we will immediately know why i didn't work. A small price to pay for a message. > > ÿÿ > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub<https://github.com/xrootd/xrootd/pull/867#issuecomment-444758763>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AE9TAx0GnxSVZasMhNlzYdP8yc87QBAiks5u2LM-gaJpZM4ZByBZ>. > > > -- > You are receiving this because you commented. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/pull/867#issuecomment-444762097 ‹ You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/xrootd/xrootd/pull/867#issuecomment-444763403>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AE9TA766dhzeZ09r3hKt-AVze-XkGwGdks5u2LlxgaJpZM4ZByBZ>. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/pull/867#issuecomment-444763714 ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1