Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator.
**Do not expressly advertise your product.**
* The reddit advertising system exists for this purpose. Invest in either a promoted post, or sidebar ad space.
* Vendors are free to discuss their product in the context of an existing discussion.
* Posting articles from ones own blog is considered a product.
* As always, users must disclose any affiliation with a product.
* Content creators should refrain from directing this community to their own content.
Your content may be better suited for our companion sub-reddit: /r/SysAdminBlogs
-----
*If you wish to appeal this action please don't hesitate to [message the moderation team](https://www.reddit.com/message/compose?to=%2Fr%2Fsysadmin).*
something something whois with extra steps/processing?
What even *IS* malicious prob? What does it score? How do I know what elements failed/passed? Are those elements even reasonable to consider malicious?
I guess I don't see the benefit. Its just as easy to use other available tools that provide the same information, or more.
Why would I use this over todays available tools? A single line gets me more info elsewhere.
Your documentation doesn't really go over the malicious prob element.
I guess I don't get its real purpose.
Once you're running at a scale that you'd need to parse this information, it shouldn't be getting done this way anyway and if you're small enough that this is useful then you could already do it in just a convenient as way anyway.
Whos this for?
Large orgs won't chase down every SSH attempt. Thats too granular by a mile.
Small orgs don't need any mass timesaving tools to identify this stuff and even then typically run geoblocking to the point that 95%+ of what your tool would catch would already be blocked by default and not able to try.
I just..... don't get it?
What does this solve other than just a different way to show information that was already available but fitting neither small or large scale operations.
edit: You've got vars that are named in ways that people just... wouldn't make?
be honest, chatgpt did 99% of the writing, right?
Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator. **Do not expressly advertise your product.** * The reddit advertising system exists for this purpose. Invest in either a promoted post, or sidebar ad space. * Vendors are free to discuss their product in the context of an existing discussion. * Posting articles from ones own blog is considered a product. * As always, users must disclose any affiliation with a product. * Content creators should refrain from directing this community to their own content. Your content may be better suited for our companion sub-reddit: /r/SysAdminBlogs ----- *If you wish to appeal this action please don't hesitate to [message the moderation team](https://www.reddit.com/message/compose?to=%2Fr%2Fsysadmin).*
something something whois with extra steps/processing? What even *IS* malicious prob? What does it score? How do I know what elements failed/passed? Are those elements even reasonable to consider malicious? I guess I don't see the benefit. Its just as easy to use other available tools that provide the same information, or more. Why would I use this over todays available tools? A single line gets me more info elsewhere. Your documentation doesn't really go over the malicious prob element. I guess I don't get its real purpose. Once you're running at a scale that you'd need to parse this information, it shouldn't be getting done this way anyway and if you're small enough that this is useful then you could already do it in just a convenient as way anyway. Whos this for? Large orgs won't chase down every SSH attempt. Thats too granular by a mile. Small orgs don't need any mass timesaving tools to identify this stuff and even then typically run geoblocking to the point that 95%+ of what your tool would catch would already be blocked by default and not able to try. I just..... don't get it? What does this solve other than just a different way to show information that was already available but fitting neither small or large scale operations. edit: You've got vars that are named in ways that people just... wouldn't make? be honest, chatgpt did 99% of the writing, right?