Re: [stunnel-users] stunnel automatically listening to

This is a discussion on Re: [stunnel-users] stunnel automatically listening to within the Stunnel Users forums, part of the Networking and Network Related category; --===============0977339933== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YkJPYEFdoxh/AXLE" Content-...


Go Back   Usenet Forums > Networking and Network Related > Stunnel Users

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 01-11-2008
Brian Hatch
 
Posts: n/a
Default Re: [stunnel-users] stunnel automatically listening to


--===============0977339933==
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="YkJPYEFdoxh/AXLE"
Content-Disposition: inline


--YkJPYEFdoxh/AXLE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Nigh 2008-01-11 17:06 -0500, Alan Pinstein pleaded:

> I don't know a lot about sockets programming, but I am not sure this =20
> makes sense... I don't WANT stunnel to stop listening to those ports; =20
> rather it shouldn't ever start. stunnel has a config file, so I'd =20
> expect it to only listen to the ports it was told to listen to, which =20
> is 4449.


Can you show us the code that is starting Stunnel? Is it running as
the apache user? Is it actually being started from apache itself?

If apache (the webserver daemon) is exec'ing Stunnel, it should be
closing those sockets. If it's not, you'd still see them as LISTENable.
(Now, would stunnel accept on them? I'd think not, because it's bound
4449 and only does listen() on that socket.

> But still I think that stunnel is actively listening on these ports. =20
> Forked processed just don't inherit sockets from parents AFAIK....


google for 'close on exec'

> I suppose that I could just set it up in init.d to run on boot, but =20
> was hoping to not have to deal with another initd process for ease of =20
> management...


You're better off using init.d, honestly. Else you might get more than
one stunnel trying to start up, all that logic to start or not start,
etc.


--=20
Brian Hatch "I jump from aircraft at 14000 feet
Systems and saying my chute always opens - so
Security Engineer I pee on jinxes."
http://www.ifokr.org/bri/ --Martin

Every message PGP signed

--YkJPYEFdoxh/AXLE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFHh+l3VkMj8/ymYEsRArawAKCJF0+CY08WTgbKFqOv13kVJDBmVwCfc+id
YePef/psBxykg+X6sP7MhfE=
=lr9l
-----END PGP SIGNATURE-----

--YkJPYEFdoxh/AXLE--

--===============0977339933==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
stunnel-users mailing list
stunnel-users@mirt.net
http://stunnel.mirt.net/mailman/listinfo/stunnel-users

--===============0977339933==--
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 10:24 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0