I'm pretty sure we'd have to spawn two instances. I'm looking into this though, we'll see what we can do. In the meantime you _might_ be able to install stunnel and point sync to localhost - I think that'll break a couple of things that we sync, but rules and nat's won't be one of them.
--Bill On 8/23/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > Not really a solution but an alternate option would be to allow access > to the fw on http and https and use fw rules to block http access on > certain interfaces. My interface for syncing is a cross over cable from > one fw to the other so I'm not concerned about any kind of > eavesdropping. So basically rather than a radio button for the 'System: > General Setup: webGUI protocol' you could have checkboxes. Https might > require more system resources than http alone but adding http to https > shouldn't require any additional horse power. Unless of course your > httpd only allows you to serve one or the other on the same daemon. > > On Tue, 2005-08-23 at 14:05 -0400, Scott Ullrich wrote: > > On 8/23/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > > > bingo, I am using https. Is there a work around other than not using > > > https currently? > > > > Not at the moment. > >
