Re: [vchkpw] Feature request: Usage of SSLREMOTEIP

[Brian Kolaci]

  > Hi Anders,
  > 
  > > > Does anyone know a workaround until either vpopmail reads SSLREMOTEIP
  > > > or ucspi-ssl sets TCPREMOTEIP?
  > > 
  > > How about something like (untested):
  > > "(env TCPREMOTEIP=$SSLREMOTEIP /home/vpopmail/bin/vchkpw)"
  > > in your startup script instead of just "/home/vpopmail/bin/vchkpw" ?
  > 
  > I tested it, but it doesn't work that way. I have now patched sslserver
  > to set TCPREMOTEIP instead, according to Charles' idea, which works
  > fine.

I recommend that you patch sslserver to set both environment variables, 
rather than just replacing it.

Brian

Re: [vchkpw] Feature request: Usage of SSLREMOTEIP

[Jonas Pasche]

Hi Anders,

> > Does anyone know a workaround until either vpopmail reads SSLREMOTEIP
> > or ucspi-ssl sets TCPREMOTEIP?
> 
> How about something like (untested):
> "(env TCPREMOTEIP=$SSLREMOTEIP /home/vpopmail/bin/vchkpw)"
> in your startup script instead of just "/home/vpopmail/bin/vchkpw" ?

I tested it, but it doesn't work that way. I have now patched sslserver
to set TCPREMOTEIP instead, according to Charles' idea, which works
fine.

Thanks for your support!

Jonas

Re: [vchkpw] Feature request: Usage of SSLREMOTEIP

[Charles Sprickman]

On 3 Mar 2003, Jonas Pasche wrote:

> The drawback is that tcpserver sets (besides others) the environment
> variable TCPREMOTEIP, which vchkpw uses for logging and for opening
> dynamic relays. sslserver from the ucspi-ssl package set SSLREMOTEIP
> instead, which causes vchkpw to stop logging IP addresses as well as its
> functionality for roaming users.

I'm no C hacker, but if I'm reading things correctly, something like this
would solve the problem without adding another weird hack to vpopmail:

*** sslserver.c.0rigSun Mar  2 20:42:25 2003
--- sslserver.c Sun Mar  2 20:42:30 2003
***
*** 208,213 
--- 208,214 
}
}
env("SSLREMOTEIP",remoteipstr);
+   env("TCPREMOTEIP",remoteipstr);
env("SSLREMOTEPORT",remoteportstr);
env("SSLREMOTEHOST",remotehost);

What would be the drawbacks to modifying sslserver?

Thanks,

Charles

> What do you think: Should vpopmail read SSLREMOTEIP in addition to
> TCPREMOTEIP, using whatever of them is set?
>
> Does anyone know a workaround until either vpopmail reads SSLREMOTEIP or
> ucspi-ssl sets TCPREMOTEIP?
>
> Jonas
>
>
>

Re: [vchkpw] Feature request: Usage of SSLREMOTEIP

[Anders Brander]

Hi,

On Monday 03 March 2003 00:44, Jonas Pasche wrote:
> Does anyone know a workaround until either vpopmail reads SSLREMOTEIP
> or ucspi-ssl sets TCPREMOTEIP?

How about something like (untested):
"(env TCPREMOTEIP=$SSLREMOTEIP /home/vpopmail/bin/vchkpw)"
in your startup script instead of just "/home/vpopmail/bin/vchkpw" ?

-- 
Anders Brander - http://anders.brander.dk/

[vchkpw] Feature request: Usage of SSLREMOTEIP

[Jonas Pasche]

Hi out there,

I have a small feature request for vpopmail. Currently, I'm checking out
if I could successfully use ucspi-ssl instead of ucspi-tcp for accepting
network connections. Things are a lot easier with this tool, because you
can simple set up your SSL certificates and replace "tcpserver" with
"sslserver", and you're done.

For those of you that are unfamiliar with ucspi-ssl yet: You can inform
yourself on the following website.

http://www.superscript.com/ucspi-ssl/intro.html

The drawback is that tcpserver sets (besides others) the environment
variable TCPREMOTEIP, which vchkpw uses for logging and for opening
dynamic relays. sslserver from the ucspi-ssl package set SSLREMOTEIP
instead, which causes vchkpw to stop logging IP addresses as well as its
functionality for roaming users.

What do you think: Should vpopmail read SSLREMOTEIP in addition to
TCPREMOTEIP, using whatever of them is set?

Does anyone know a workaround until either vpopmail reads SSLREMOTEIP or
ucspi-ssl sets TCPREMOTEIP?

Jonas