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

security/openconnect: add field to add certificate hash #723

Merged
merged 19 commits into from
Jul 8, 2018
Merged

security/openconnect: add field to add certificate hash #723

merged 19 commits into from
Jul 8, 2018

Conversation

mimugmail
Copy link
Member

If using wildcard cert or CA is untrusted you have to add the certificate hash manually.
https://forum.opnsense.org/index.php?topic=9090.0

@fichtner fichtner self-assigned this Jul 8, 2018
<id>general.servercert</id>
<label>Certificate Hash</label>
<type>text</type>
<help>If you have a wildcard certificate or the CA is untrusted, you have to enter the SHA hash of the certificate to force a connect.</help>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHA1 or SHA256 ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can add a dropdown to choose for both

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only sha256 is ok, but it should say so in the label and help text

@@ -23,5 +23,9 @@
<default>password</default>
<Required>Y</Required>
</password>
<servercert type="TextField">
<Required>N</Required>
<ValidationMessage>Please provide a valid hash.</ValidationMessage>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No validation logic no validation error?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you have a look in one of the last commits in PR? I had a validator nur it wasn't accepted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which format does it accept? XXXXXX.. or XX:XX:XX..?

@mimugmail
Copy link
Member Author

Now it's correct ...

<multiple>N</multiple>
<Required>Y</Required>
<OptionValues>
<sha256>sha256</sha256>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHA256 for the label

<Required>Y</Required>
<OptionValues>
<sha256>sha256</sha256>
<sha1>sha1</sha1>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHA1 for the label

@mimugmail
Copy link
Member Author

fixed ..

Copy link
Member

@fichtner fichtner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️

@fichtner fichtner merged commit 7d40d1a into opnsense:master Jul 8, 2018
@fichtner
Copy link
Member

fichtner commented Jul 8, 2018

Merged, thanks!

@mimugmail mimugmail deleted the occert branch July 9, 2018 04:59
fichtner pushed a commit that referenced this pull request Jul 10, 2018
fichtner pushed a commit that referenced this pull request Jul 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants