(I'll re-add the list to the cc, because this is the third time I get
the same suggestion. Please bear with me ;)
On Tue, Jul 03, 2007 at 09:05:37AM +0200, Michael Menge wrote:
> one awy could be to add cnames in the field subjectalternatename,
> or use wildcards like *.mappi.helsinki.fi in the ce
On Mon, Jul 02, 2007 at 01:29:09PM -0400, Wesley Craig wrote:
> On 02 Jul 2007, at 12:00, Janne Peltonen wrote:
> >But then, I'd have to buy
> >twenty-five certificates...
> You could create your own "lite CA" and sign your own certificates.
> This is a very common solution when you control the
On 02 Jul 2007, at 12:00, Janne Peltonen wrote:
> But then, I'd have to buy
> twenty-five certificates...
You could create your own "lite CA" and sign your own certificates.
This is a very common solution when you control the machines that
Pine runs on, or if the machines Pine runs on are "pr
On Mon, Jul 02, 2007 at 03:19:55PM +0200, Michael Menge wrote:
> Hi,
>
> you could try do disable the validation of the certificate with
>
> novalidate-cert
Thanks, yes, I could. :) But I'd like to have a functioning certificate
scheme here. I really wouldn't like anyone pretending to be, say,
Hi,
you could try do disable the validation of the certificate with
novalidate-cert
Quoting Janne Peltonen <[EMAIL PROTECTED]>:
Hi!
I seem to be having trouble with the newest version of pine (4.64) and
fcc's and referrals.
I've implemented a crude load-balancing to my unified cyrus cluster
Hi!
I seem to be having trouble with the newest version of pine (4.64) and
fcc's and referrals.
I've implemented a crude load-balancing to my unified cyrus cluster
using DNS and multiple A records for the public name of the service.
Everything works perfectly, even with pine, except when I try to
