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.

Sign up for GitHub

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

Jump to bottom

[8.5](backport #33507) docs: add example to extract HEX encoded fingerprint from certificate #33680

Merged
merged 1 commit into from
Nov 15, 2022
Merged

[8.5](backport #33507) docs: add example to extract HEX encoded fingerprint from certificate #33680

merged 1 commit into from
Nov 15, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 15, 2022 •
edited by zube bot
Loading

This is an automatic backport of pull request #33507 done by Mergify.

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

@belimawr @mergify
docs: add example to extract HEX encoded fingerprint from certificate (…
89122e3 
…#33507)

This commit adds an example of how to extract the HEX encoded SHA-256
fingerprint from a CA certificate using openssl, awk and sed. Those
tools should be available on most Unix-like systems.

Co-authored-by: DeDe Morton <dede.morton@elastic.co>
(cherry picked from commit 0ebad69)
@mergify mergify bot requested a review from a team as a code owner November 15, 2022 14:17
@mergify mergify bot requested review from faec and leehinman and removed request for a team November 15, 2022 14:17
@mergify mergify bot added the backport label Nov 15, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 15, 2022
@botelastic
Copy link

botelastic bot commented Nov 15, 2022

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-11-15T14:17:24.687+0000

  • Duration: 8 min 8 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@belimawr belimawr merged commit 8229807 into 8.5 Nov 15, 2022
@belimawr belimawr deleted the mergify/bp/8.5/pr-33507 branch November 15, 2022 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@faec faec Awaiting requested review from faec faec is a code owner automatically assigned from elastic/elastic-agent-data-plane

@leehinman leehinman Awaiting requested review from leehinman leehinman is a code owner automatically assigned from elastic/elastic-agent-data-plane

Assignees

@belimawr belimawr

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @belimawr