On 11/06/2010 10:24, Nathan Whitehorn wrote:
On 11/06/10 01:04, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS,
etc?), and 2) w
On Sun, Nov 7, 2010 at 10:49 AM, Joel Dahl wrote:
> On 07-11-2010 11:40, Daniel Gerzo wrote:
>> On 6.11.2010 6:17, Josh Paetzel wrote:
>> > Without putting much analysis into it, we talked about using lighttpd,
>> > which
>> > is BSDL. As far as another service, it would be running for the insta
On 07-11-2010 11:40, Daniel Gerzo wrote:
> On 6.11.2010 6:17, Josh Paetzel wrote:
> > Without putting much analysis into it, we talked about using lighttpd, which
> > is BSDL. As far as another service, it would be running for the install
> > only
> > which is in most circumstances something that
On 6.11.2010 6:17, Josh Paetzel wrote:
Without putting much analysis into it, we talked about using lighttpd, which
is BSDL. As far as another service, it would be running for the install only
which is in most circumstances something that happens locally.
NGiNX might a worth a shoot as well.
On Nov 5, 2010, at 10:17 PM, Josh Paetzel wrote:
> On Friday, November 05, 2010 11:48:27 pm Garrett Cooper wrote:
>
>>> Just to add to that (because I do find it a novel idea), 1) how
>>> are you going to properly prevent man in the middle attacks (SSL, TLS,
>>> etc?), and 2) what webserver woul
On Nov 6, 2010, at 1:33 PM, Devin Teske wrote:
>
> On Nov 6, 2010, at 9:24 AM, Nathan Whitehorn wrote:
>
>> On 11/06/10 01:04, Garrett Cooper wrote:
>>> On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
>Just to add to that (because I do find it a novel idea), 1) how
> are you go
On Nov 6, 2010, at 9:24 AM, Nathan Whitehorn wrote:
> On 11/06/10 01:04, Garrett Cooper wrote:
>> On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS
On 11/06/10 01:04, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
>>> Just to add to that (because I do find it a novel idea), 1) how
>>> are you going to properly prevent man in the middle attacks (SSL, TLS,
>>> etc?), and 2) what webserver would you use?
>>
>> ht
On 11/06/2010 01:38, Garrett Cooper wrote:
On Nov 5, 2010, at 11:49 PM, Warner Losh wrote:
On 11/06/2010 00:04, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent m
On Nov 5, 2010, at 11:49 PM, Warner Losh wrote:
> On 11/06/2010 00:04, Garrett Cooper wrote:
>> On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS,
On 11/06/2010 00:05, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 11:04 PM, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS,
et
On 11/06/2010 00:04, Garrett Cooper wrote:
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
Just to add to that (because I do find it a novel idea), 1) how
are you going to properly prevent man in the middle attacks (SSL, TLS,
etc?), and 2) what webserver would you use?
https or ssh.
On Fri, Nov 5, 2010 at 11:04 PM, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
>>> Just to add to that (because I do find it a novel idea), 1) how
>>> are you going to properly prevent man in the middle attacks (SSL, TLS,
>>> etc?), and 2) what webserver would yo
On Fri, Nov 5, 2010 at 10:06 PM, Warner Losh wrote:
>> Just to add to that (because I do find it a novel idea), 1) how
>> are you going to properly prevent man in the middle attacks (SSL, TLS,
>> etc?), and 2) what webserver would you use?
>
> https or ssh.
>
> We're also toying with the idea
On Fri, Nov 5, 2010 at 10:17 PM, Josh Paetzel wrote:
> On Friday, November 05, 2010 11:48:27 pm Garrett Cooper wrote:
>
>> > Just to add to that (because I do find it a novel idea), 1) how
>> > are you going to properly prevent man in the middle attacks (SSL, TLS,
>> > etc?), and 2) what webser
On Friday, November 05, 2010 11:48:27 pm Garrett Cooper wrote:
> >Just to add to that (because I do find it a novel idea), 1) how
> > are you going to properly prevent man in the middle attacks (SSL, TLS,
> > etc?), and 2) what webserver would you use?
> >I bring up the former item becaus
> Just to add to that (because I do find it a novel idea), 1) how
> are you going to properly prevent man in the middle attacks (SSL, TLS,
> etc?), and 2) what webserver would you use?
https or ssh.
We're also toying with the idea of having a partition that you could
'dd' your certs and keys
On Fri, Nov 5, 2010 at 9:47 PM, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 9:16 PM, Josh Paetzel wrote:
>> It's been incredibly busy for us in iXsystems land, with a lot of irons in
>> the
>> fire.
>>
>> One of the many things we've been working on is a new installer. Several
>> months ago
On Fri, Nov 5, 2010 at 9:16 PM, Josh Paetzel wrote:
> It's been incredibly busy for us in iXsystems land, with a lot of irons in the
> fire.
>
> One of the many things we've been working on is a new installer. Several
> months ago pc-sysinstall was imported into HEAD from the PC-BSD project.
>
>
It's been incredibly busy for us in iXsystems land, with a lot of irons in the
fire.
One of the many things we've been working on is a new installer. Several
months ago pc-sysinstall was imported into HEAD from the PC-BSD project.
pc-sysinstall is a fine tool, and very useful as the backend
20 matches
Mail list logo
