Abhilash Raj writes:
> Then i guess I will simply create a new key with list's credentials
> when the list is created,
I really think that's best for nontechnical users. Read the article
Terri cited on mailman-developers a few days ago.
Adding an upload option (non-trivial to implement secure
Abhilash Raj writes:
> > I think the address should be $LIST-owner@fqdn. For other parameters,
> > defaults are OK I think (size=2048, type=RSA IIRC).
>
> Here should not the address be the list's posting address? Like for
> mm-dev list should it not be "mailman-developers@python.org"?
May
On Friday 16 August 2013 10:35 AM, Stephen J. Turnbull wrote:
> Abhilash Raj writes:
>
> > 1) How do list owner create keys? What parameters? Which address?
>
> python-gnupg provides a key-generation API, GPG.gen_key().
> Alternatively, this could be done manually by the trusted
> site-manager.
On Friday 16 August 2013 12:30 PM, Stephen J. Turnbull wrote:
> Abhilash Raj writes:
>
> > But can we achieve required randomization to create keys on virtualized
> > systems?
>
> Not your problem. We can do it on physical hosts, and that's good
> enough. People who care this much about secur
Original Message
Subject: Re: [Mailman-Developers] GSoC Updates
Date: Fri, 16 Aug 2013 11:48:56 +0530
From: Abhilash Raj
To: Stephen J. Turnbull
On Friday 16 August 2013 10:35 AM, Stephen J. Turnbull wrote:
> Abhilash Raj writes:
>
> > 1) How do list owner create keys? Wha
Original Message
Subject: Re: [Mailman-Developers] GSoC Updates
Date: Thu, 15 Aug 2013 19:44:43 +0530
From: Abhilash Raj
To: Stephen J. Turnbull
Thanks for the replies, I tried working on it and it was good enough to
be used for now. Thanks Steve for trying it yourself.
I h
Abhilash Raj writes:
> But can we achieve required randomization to create keys on virtualized
> systems?
Not your problem. We can do it on physical hosts, and that's good
enough. People who care this much about security will be prepared to
pay for it. Generalizing to handle sites that need
