Currently certain PKI operations are protected against CSRF attack by utilizing a 2-step process where the server returns a nonce in the first step and the client has to send it back in the second step. The protection can be done more efficiently and globally by checking the referer header. See the following pages:
Proposed milestone: 10.3
Per CS/DS meeting of 5/5/2014, moving to milestone 10.3.
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1547
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.