Re: [Pound Mailing List] Pound 2.7 (FR27: Security Fixes)

2011-12-30 Thread Jorge Fábregas
On 12/30/2011 01:37 PM, Joe Gooch wrote: > Just thought I'd throw in patches already available. > > SSLv2 issues, and BEAST attack mitigation, and client renegotiation issues: +1 I've been using this patch ever since Joe provided it and would like this functionality to be part of the main progra

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Dave Steinberg
On 12/30/2011 12:44 PM, Jaroslav Lukesh wrote: Hi, I give a vote for the emergency server - ie., server, which will be active only in case when all "normal" backends are not responding. Pound can already do this one. See the 'Emergency' block. Regards, -- Dave Steinberg http://www.geekisp.co

RE: [Pound Mailing List] Pound 2.7 (FR27: Misc new features)

2011-12-30 Thread Jacob Anderson
Joe's items #1, #3, and #5 would benefit me. +1 for each. -- jake > -Original Message- > From: Joe Gooch [mailto:mrwiz...@k12system.com] > Sent: Friday, December 30, 2011 9:47 AM > To: 'pound@apsis.ch' > Subject: RE: [Pound Mailing List] Pound 2.7 (FR27: Misc new features) > > I have a

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Jaroslav Lukesh
Hi, I give a vote for the emergency server - ie., server, which will be active only in case when all "normal" backends are not responding. And vote for another detection of "not responding" status by defined page with (regexp) defined content. Regards, Jaroslav Lukesh - Původní zpráva

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Dave Steinberg
Piling on - I like this one too. I'd use it. Theoretically then you'd also need to run fewer checks and/or get quicker convergence as a bonus. ;) Regards, -- Dave Steinberg On 12/30/2011 12:32 PM, Joe Gooch wrote: Clusters/Macros: As someone who has 25+ backends per service and 6-7 service

RE: [Pound Mailing List] Pound 2.7 (FR27: Misc new features)

2011-12-30 Thread Joe Gooch
I have a bunch of other patches that form my branch of pound. (Still based on 2.5 actually) Things you'd see in other software... I'll submit them here for other people to chime in on. These are in my git repo and I could provide patches with little effort. 1) Include and IncludeDir directive

[Pound Mailing List] RE: FR27: Hot Reconfiguration

2011-12-30 Thread Joe Gooch
Backend cookies patch is here https://users.k12system.com/mrwizard/pound/pound_26_backend_cookies.patch.bz2 "init script" patch is here https://users.k12system.com/mrwizard/pound/pound_26_initscript.patch.bz2 Joe > -Original Message- > From: Joe Gooch [mailto:mrwiz...@k12system.com] >

RE: [Pound Mailing List] Pound 2.7 (FR27: Security Fixes)

2011-12-30 Thread Joe Gooch
Just thought I'd throw in patches already available. SSLv2 issues, and BEAST attack mitigation, and client renegotiation issues: 1) My SSL Ciphers and Client Renegotiation patch: http://goochfriend.org/pound_2.6f_ssl_renegotiation_and_ciphers.patch Introduces the SSLHonorCipherOrder option (0

RE: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Joe Gooch
Clusters/Macros: As someone who has 25+ backends per service and 6-7 services, this would be very nice. I would also anticipate this would not be difficult to implement. Joe > -Original Message- > From: Jacob Anderson [mailto:j...@beyond-ordinary.com] > Sent: Friday, December 30, 2011

RE: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Joe Gooch
I agree and disagree with this. Shared/clustered session support adds a level of complexity to the web solution, which I consider to be onerous to set up. Plus you have delay in session sync, and restrictions on what you can place in session support among other things. It depends on what you'

RE: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Joe Gooch
Not really a pound 2.7 specific thing... but personally I'd love to see some community development resources... I.e. 1) Bugzilla, mantis, or other similar place where feature requests could be tracked, patches uploaded/attached, and/or voted for. 2) Community-available git, svn or similar reposit

RE: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Joe Gooch
Disabled backends already allow existing sessions to continue, so this is already implemented. Plus, I wouldn't consider this a config change. This to me is a runtime modification (which is done through poundctl) Joe > -Original Message- > From: Paolo Nesti Poggi [mailto:p...@italyfla

[Pound Mailing List] FR27: Hot Reconfiguration

2011-12-30 Thread Joe Gooch
I anticipate this topic is going to run long, so I thought it best to have a separate thread. I think there are probably two issues here. 1) Maintaining Sessions across Pound Restarts 2) Changing the configuration either without restarting pound, or with #1. I see various approaches to these tw

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Albert
Dave, don't know if you're thinking of the same thing I have in mind, but I'd also like to see a policy where round-robin is used, however, the new backend is not selected on existing connection from client for new requests. Currently, if a client makes a request for a page, and that page has oth

RE: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Jacob Anderson
+1 on the cluster/macro idea. Yeah, that's a really good 2.7 idea. I could really use that and get rid of my m4 templates. -- jake > -Original Message- > From: Todd Freeman [mailto:free...@andrews.edu] > Sent: Friday, December 30, 2011 8:35 AM > To: pound@apsis.ch > Subject: Re: [Pound

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Todd Freeman
I'll second the "config reload" going around... I would also add a request to be able to define clusters or such of servers An example of this would be like: Cluster Name PROD BackEnd Address 192.168.1.20 Port 80 End BackEnd

RE: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Jacob Anderson
Sorry to chime in here on this topic, but this really isn’t a pound function. If you are losing your session data because pound bounces your client to another BE, then you need a shared session state machine for your back ends. We do this in ASP.NET with the session state server and it works

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread MSDirect Internet Diensten - Support
Hi, I totally agree. We have dozens of changes per day and every change has to be followed by a restart. We are currently considering a change window to activate the changes. With reloads these should not be required anymore. Probably even better would be to fully commandline the configurati

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Paolo Nesti Poggi
Hi, I'm not (yet) a user hence at risk to say something not well thought out, however: When/if this (no downtime config reload) is available, then the ability to close for new connections/sessions to a specific back-end server, while letting current active sessions exting

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Dave Steinberg
On 12/30/2011 9:44 AM, Robert Segall wrote: Hallo everybody New year, new version: we declare open the wish-list for 2.7 features. Please reply to this with your list of enhancements/patches/wishes. Please feel also free to offer comments (supportive or not, as the case may be) on items that ot

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Leo
+1 On 12/30/2011 04:05 PM, Erik Hensema / HostingXS wrote: > > THE killer feature: reloading the config without downtime. Currently > it's impossible to reload the config without losing all sessions. > > > On vrijdag 30 december 2011 15:44:06 Robert Segall wrote: > > > Hallo everybody > > > > > >

Re: [Pound Mailing List] Pound 2.7

2011-12-30 Thread Erik Hensema / HostingXS
THE killer feature: reloading the config without downtime. Currently it's impossible to reload the config without losing all sessions. On vrijdag 30 december 2011 15:44:06 Robert Segall wrote: > Hallo everybody > > New year, new version: we declare open the wish-list for 2.7 features. > Please r

[Pound Mailing List] Pound 2.7

2011-12-30 Thread Robert Segall
Hallo everybody New year, new version: we declare open the wish-list for 2.7 features. Please reply to this with your list of enhancements/patches/wishes. Please feel also free to offer comments (supportive or not, as the case may be) on items that others may post. The more support for a feature,