-
Story
-
Resolution: Won't Do
-
Undefined
-
None
-
None
-
Medium
-
rhel-idm-ipa
-
ssg_idm
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
x86_64
-
None
-
57,005
1. What is the nature and description of the request?
I want to be able to set restrictions on the SSH public keys field for the users.
It should not be possible to upload weak keys.
2. Why do you need this? (List the business requirements here)
This is needed for security purpose.
3. How would you like to achieve this? (List the functional requirements here)
We could set global settings similar to the gitlab configuration, as described here: https://docs.gitlab.com/ee/api/settings.html
- rsa_key_restriction - The minimum allowed bit length of an uploaded RSA key. Default is 0 (no restriction). -1 disables RSA keys.
- dsa_key_restriction - The minimum allowed bit length of an uploaded DSA key. Default is 0 (no restriction). -1 disables DSA keys.
- ecdsa_key_restriction - The minimum allowed curve size (in bits) of an uploaded ECDSA key. Default is 0 (no restriction). -1 disables ECDSA keys.
- ed25519_key_restriction - The minimum allowed curve size (in bits) of an uploaded ED25519 key. Default is 0 (no restriction). -1 disables ED25519 keys.
4. For each functional requirement listed, specify how Red Hat can test to confirm the requirement is successfully implemented with you.
- Set up an IPA server with the WebUI in the VM
- Create a single user
- login in the webui with that username, adding a prohibited key (as per configuration parameters described in point 3.) should result in an error, with no change applied.
5. Do you have any specific time-line dependencies and which release would you like to target (i.e. IPA Version)?
I would like to get this feature on my current set up on RHEL 7 (updated to the latest minor revision), ideally in the version provided in the repository rhel-7-server-rpms. I currently use 4.6.5 but I can upgrade if an upgrade plan is provided. In all cases, the solution should work under RHEL 7.
6. Would you be able to assist in testing this functionality if implemented?
Yes