Article delegate-en/1932 of [1-5169] on the server localhost:119
  upper oldest olders older1 this newer1 newers latest
search
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
[Reference:<_A1931@delegate-en.ML_>]
Newsgroups: mail-lists.delegate-en

[DeleGate-En] Re: sslway and root cert
15 Oct 2002 10:34:27 GMT feedback@delegate.org (Yutaka Sato)


On 10/14/02(21:32) you "Stephan Kraemer" <prmdqbdyi-xtqvdm3cnljr.ml@ml.delegate.org> wrote
in <_A1931@delegate-en.ML_>
 |is it possible that the sslway  manage a private certifikate like this
 |configuration , see below
...
 |fine at other  destinations .. but it dont work here the answer ist  " NO
 |PERMISSION" i think that the problem is  the proxy must use 3 certifikates for
 |the connection.. and i dont know to tell him .. how to use it ..
...
 |10/14 14:12:18.81 [2272] 1+1: (0) accepted [17] -@[193.25.207.168]s409nt1pr01.intern.sparkasse-bonn.de:11416 (0.062s)(3)
 |10/14 14:12:18.81 [2272] 1+1: PATH>
 |https://wpdyn.wps.de:443!
 |s409nt1pr01.intern.spb.de:8083!
 |s409nt1pr01.intern.spb.de:11416!anonymous@s409nt1pr01.intern.spb.de;1034597538
...
 |10/14 14:12:22.82 [2272] 1+1: E-P: No permission: s409nt1pr01.intern.spb.de:11416 => https://wpdyn.wps.de

The message "No permission" does nothing to do with SSL certificate.
It is just the result of some (default) access restriction of DeleGate.
See <URL:http://www.delegate.org/delegate/Manual.htm#acl>
DeleGate/8.0 (distributed as in alpha status) shows the parameter which
should be specified to solve the rejection.

Cheers,
Yutaka
--
  @ @ Yutaka Sato <y.sato@delegate.org> http://www.delegate.org/y.sato/
 ( - ) National Institute of Advanced Industrial Science and Technology (AIST)
_<   >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller

  admin search upper oldest olders older1 this newer1 newers latest
[Top/Up] [oldest] - [Older+chunk] - [Newer+chunk] - [newest + Check]
@_@V