[GemStone-Smalltalk] Understanding secure backups

Norm Green norm.green at gemtalksystems.com
Mon Sep 9 07:45:14 PDT 2019

Thanks for the info.  I see your point about needing to switch keys of a 
backup encrypted with a private key that has been compromised.

I've submitted feature request 48314 to track the issue.

I would imagine that copydbf could be enhanced so that a new backup file 
could be created with new pairs of encryption and signing keys.  The 
caller would of course need to provide the old signing and encryption 
keys.  Also the old file would not be modified in place.


On 9/8/2019 10:09 PM, Iwan Vosloo via GemStone-Smalltalk wrote:
> Hi Norm,
> >> On 08-09-2019, at 7:45 PM, Norm Green via GemStone-Smalltalk
> >>
> >> Yes I can add a request.  Could you please explain the practical use
> >> of such a feature?
> I am just wondering how to handle the situation of a compromised key 
> and similar situations where you want protect existing backups from 
> access via a key that is no longer trusted.
> On 2019/09/09 13:11, Jerry Kott via GemStone-Smalltalk wrote:
>> If I may have some input on this conversation, I would suggest that 
>> rotating certs adds complexity, and complexity is the enemy of 
>> security. Without knowing all the details of specific security 
>> requirements, I think properly managing and securing a single 
>> certificate chain would be a better solution.
> I'd love to hear an elaboration.
> Regards
> Iwan
> _______________________________________________
> GemStone-Smalltalk mailing list
> GemStone-Smalltalk at lists.gemtalksystems.com
> https://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk

More information about the GemStone-Smalltalk mailing list