User story #12300
closed
Inconsistent flush of SSH authorised keys
Added by Félix DALLIDET over 6 years ago.
Updated over 5 years ago.
Description
The technique "remove other keys" boolean is quite confusing when you want to flush authorized keys.
You can not predict the order of execution so you can flush multiple time the same file or flush it after some writing and loose some keys managed by rudder
if you have multiple values for the same user.
That is most likely not the desired behaviour or it should be more explicit. The component key should be per user and not per key_tag.
Component key is set on the User, not tag.
- Target version changed from 4.1.11 to 4.1.12
- Target version changed from 4.1.12 to 4.1.13
- Target version changed from 4.1.13 to 411
- Target version changed from 411 to 4.1.13
- Related to User story #12357: Port "SSH authorised keys" Technique to multiversionned technique added
- Subject changed from SSH authorised keys to Inconsistent flush of SSH authorised keys
- Category set to Techniques
- Target version changed from 4.1.13 to 4.1.14
- Target version changed from 4.1.14 to 4.1.15
- Target version changed from 4.1.15 to 4.1.16
- Target version changed from 4.1.16 to 4.1.17
- Target version changed from 4.1.17 to 4.1.18
- Target version changed from 4.1.18 to 4.1.19
- Target version changed from 4.1.19 to 4.1.20
- Target version changed from 4.1.20 to 4.1.21
- Status changed from New to Rejected
this has been fixed in latest version of the technique - rejecting
Also available in: Atom
PDF