On Wed, Aug 2, 2017 at 10:04 PM, Fraser Tweedale wrote:
> On Wed, Aug 02, 2017 at 09:59:35AM -0400, Rob Crittenden wrote:
>> Petr Vobornik via FreeIPA-devel wrote:
>> > On Wed, Aug 2, 2017 at 3:30 AM, Fraser Tweedale
>> > wrote:
>> >> Hi devs,
>> >>
>> >> This is at least the second time recentl
On Wed, Aug 02, 2017 at 09:59:35AM -0400, Rob Crittenden wrote:
> Petr Vobornik via FreeIPA-devel wrote:
> > On Wed, Aug 2, 2017 at 3:30 AM, Fraser Tweedale wrote:
> >> Hi devs,
> >>
> >> This is at least the second time recently that people needing to
> >> renew service certificates used ``ipa-ca
Petr Vobornik via FreeIPA-devel wrote:
> On Wed, Aug 2, 2017 at 3:30 AM, Fraser Tweedale wrote:
>> Hi devs,
>>
>> This is at least the second time recently that people needing to
>> renew service certificates used ``ipa-cacert-manage renew`` (the
>> wrong command) and either didn't solve the probl
On Wed, Aug 2, 2017 at 3:30 AM, Fraser Tweedale wrote:
> Hi devs,
>
> This is at least the second time recently that people needing to
> renew service certificates used ``ipa-cacert-manage renew`` (the
> wrong command) and either didn't solve the problem or got into a
> deeper mess.
>
> Clearly we
Hi devs,
This is at least the second time recently that people needing to
renew service certificates used ``ipa-cacert-manage renew`` (the
wrong command) and either didn't solve the problem or got into a
deeper mess.
Clearly we have a usability problem here.
The ipa-cacert-manage(1) man page is
