Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

registrar TLS related config uptions prefixed with registrar_ seems not to be used #782

Closed
kkaarreell opened this issue Nov 5, 2021 · 2 comments · Fixed by #806
Closed

Comments

@kkaarreell
Copy link
Contributor

Is your an issue a feature request? If so, please raise it as an enhancement

Environment

  • OS / version: RHEL-9 / CentOS Stream 9
  • Processor architecture: x86_64
  • TPM Manufacturer: IBM emulator
  • Keylime version: current upstream Nov 1, 2021

Description

https://github.com/keylime/keylime/blob/master/keylime.conf#L190
The following options withing the [registrar] section of keylime.conf doesn't seem to have any use:

registrar_tls_dir
registrar_ca_cert
registrar_my_cert
registrar_private_key

I have confirmed that by setting it to wrong values, like registrar_tls_dir = /no-such-diretc.

Expected behavior vs. actual behavior

there are no registrar_* TLS options withing [registrar] section (if they are really not used).

Steps to reproduce problem

Relevant logs

Attach any relevant log files that can help to debug your issue.

@kkaarreell
Copy link
Contributor Author

kkaarreell commented Nov 5, 2021

Additionally,
https://github.com/keylime/keylime/blob/master/keylime.conf#L168
and
https://github.com/keylime/keylime/blob/master/keylime.conf#L490
mentions <fully_qualified_domain_name>-public.pem as a default filename for the private key,
I assume it should state -private.pem instead (since it is a private key). The code in keylime/ca_util.py seems to load keys properly (public from -public.pem, private from -private.pem).

@THS-on
Copy link
Member

THS-on commented Nov 12, 2021

The first issue is now fixed with #792. I couldn't find any part of the registrar code that uses those options.

For the -public.pem issue it makes sense and in our setup we also explicitly specify -private.pem,
but I'll have to check that all code actually assumes that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants