[cisco-voip] re-genarate certifications

[Brian Meade]

In 8.0 I believe, cert changes didn't reset phones.  I think that started
in 8.5 as a fix for everyone breaking their clusters regenerating all the
certs at once.

It would be a good idea to allow for a much larger ITL where you can add
whatever certs you want but I think the older phone hardware is pretty
limited for memory and you also don't want these files getting too large.
Kind of similar to Phone VPN Cert changes where you add an additional cert
to the VPN Gateway in CUCM ahead of time.  Difference there is the phones
are only downloading a hash of the certificate to compare against.

Probably need a new feature to put your CA root on the 7800/8800 CA list,
 everyone gets on those model phones, then just allow those model phones to
use that CA list for trusting config files and we may be good to go.  I
think right now the CA list is only used for MRA.

There's probably some security concerns there though about the CA list
being used for these items.

On Fri, Jun 23, 2017 at 5:00 PM, Dave Cardwell <dave.cardwell1 at gmail.com>
wrote:

> Fair enough, the 90 day cycle of LetsEncrypt is probably too short for the
> situation where you have phones sat on shelves.  But, if you implement the
> fix to allow phones to import multiple certs and not reset when doing so it
> solves a whole lot of other problems and reduces the stress involved in
> migrations.
>
> You can still use longer cert lifetimes.  In the case of your large regen
> project you push out the new certs 60 days before the old ones expire then
> roll the servers over 30 days later.  You now, first, have a month to make
> sure all the phones have been plugged in and then if there are any problems
> with the cutover you can just roll back and have another month to deal with
> it.  That sounds less stressful than the current process.  It shouldn't
> even require downtime :)
>
> IPSec vpn's manage to gracefully handle key rollover in PKI environments.
>
>
> On 23 Jun 2017 21:16, "Brian Meade" <bmeade90 at vt.edu> wrote:
>
> You still are going to have issues with phones that were offline when the
> new cert was pushed.  For a large regen project, we just plan to have
> everyone make sure their phones are online but you can't do this every
> couple of months.
>
> With websites, people don't have persistent connections as well so it's
> easy to switch certs.
>
> Anyone know of any persistent services able to use technology like
> Let'sEncrypt without dropping connections?
>
>
>
> On Fri, Jun 23, 2017 at 3:29 PM, Dave Cardwell <dave.cardwell1 at gmail.com>
> wrote:
>
>>
>>> The bigger problem is the automatic phone reset.
>>> -Rya
>>>
>>
>> Well fix the phones, why do they need to reset to support new
>> certificates?
>>
>> Key rotation is a long solved problem, push out the new new certificate
>> when its generated after 60 days but don't activate it on the server.  The
>> phones should now trust both the new one and the old one (until it expires
>> 30 days later), then activate the new one on the server a couple of days
>> before the old one expires.  Once the phones can import certificates
>> without reloading the switch-over on the server side should be a non-issue.
>>
>>
>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170623/b8da5b17/attachment.html>