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

update wording in blog to be more clear that the cli is not an archive #386

Merged
merged 2 commits into from
Dec 27, 2021

Conversation

breadchris
Copy link
Contributor

Some people were confused of how to run the cli, the blog post was unclear.

docs/blog/2021-12-12-log4j-zero-day-mitigation-guide.mdx Outdated Show resolved Hide resolved
:::caution Version 2.16.0 vulnerable to DOS
~~Log4j version `2.15.0` which was previously thought to be secure has been found to still have a [limited vulnerability](https://lists.apache.org/thread/83y7dx5xvn3h5290q1twn16tltolv88f),
that could result in a DOS (but not RCE), users must update to `>= 2.16.0`.~~
Copy link
Contributor

Choose a reason for hiding this comment

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

Lets just say update to 2.17.0? It's confusing to say "update to 16....okay now update to 17"

I think having a cohesive and clear message is way more valuable than having a changelog of whats happened to our blog post.

@breadchris breadchris merged commit eda04aa into master Dec 27, 2021
@breadchris breadchris deleted the log4shell-blog-cli-command-update branch December 27, 2021 05:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants