This is what happens if test.csr is not ASCII armored:
$ ipa cert-request test.csr Principal: host/vm-141.idm.lab.bos.redhat.com ipa: ERROR: non-public: TypeError: must be encoded string without NULL bytes, not unicode Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ipalib/backend.py", line 129, in execute result = self.Command[_name](*args, **options) File "/usr/lib/python2.7/site-packages/ipalib/frontend.py", line 433, in __call__ self.validate(**params) File "/usr/lib/python2.7/site-packages/ipalib/frontend.py", line 710, in validate param.validate(value, self.env.context, supplied=param.name in kw) File "/usr/lib/python2.7/site-packages/ipalib/parameters.py", line 819, in validate self._validate_scalar(value) File "/usr/lib/python2.7/site-packages/ipalib/parameters.py", line 831, in _validate_scalar error = rule(ugettext, value) File "/usr/lib/python2.7/site-packages/ipalib/plugins/cert.py", line 168, in validate_csr if csr and os.path.exists(csr): File "/usr/lib64/python2.7/genericpath.py", line 18, in exists os.stat(path) TypeError: must be encoded string without NULL bytes, not unicode ipa: ERROR: an internal error has occurred
3.4 development was shifted for one month, moving tickets to reflect reality better.
Honza, is this issue addressed by your latest 3.4 certificate/refactoring patches? Is it a simple task to do or does it require wider changes in the framework?
No, the refactoring is necessary for CA certificate renewal and thus touches mostly only certificate renewal and installer code. This issue is caused by improper handling of file input. I think it can be worked around, but I would like to see a proper solution for this in the framework in the future (see #2933 and http://www.redhat.com/archives/freeipa-devel/2012-August/msg00048.html).
Adjusting time plan - 3.4 development was postponed as we focused on 3.3.x testing and stabilization.
Moving to the same bucket as it's prerequisite - #2933.
Metadata Update from @jcholast: - Issue assigned to someone - Issue set to the milestone: Future Releases
Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.
Metadata Update from @rcritten: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.