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

[FEATURE] Include more information in certificate output #407

Open
ZachHaber opened this issue Sep 7, 2022 · 1 comment
Open

[FEATURE] Include more information in certificate output #407

ZachHaber opened this issue Sep 7, 2022 · 1 comment
Assignees

Comments

@ZachHaber
Copy link

Is your feature request related to a problem? Please describe.
For my use case with ARX, I'd like to be able to output the final attacker model results as part of the output PDF (File => Create Certificate).
image

Describe the solution you'd like
Just having the values in the output certificate would be very helpful, as that would mean that one file would have all the information, rather than need to screenshot the attacker models page separately.

Describe alternatives you've considered
I'm not really sure what other ways it can be added in, but the main alternative is just what we are already doing - screenshotting the values separately.

@prasser prasser changed the title [FEATURE] Certificate output include predicted risk [FEATURE] Include more information in certificate output Sep 10, 2022
@prasser
Copy link
Collaborator

prasser commented Sep 10, 2022

Thanks for suggesting this. The certificate is currently quite limited in the amount of information it contains. The main reason is that a lot of the risk and utility measures provided by ARX can be quite computationally demanding to calculate. Hence, to extend the certificate with additional information would probably require (1) a rewrite to generate the certificate in a background thread and (2) a dialog where users can select the information that they want to have included.

This requires some work and we are not able to implement this at the moment due to a lack of resources. I will leave the issue open for others to take up or for us to come back to it when we have time.

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

No branches or pull requests

2 participants