k4nfr3
k4nfr3
Mhmm unfortunatly it didn't much success yet. I'll try again in a few days. Checked installed .net SDK and dotnet --list-sdks 1.1.14 [C:\Program Files\dotnet\sdk] 2.1.202 [C:\Program Files\dotnet\sdk] 2.1.806 [C:\Program Files\dotnet\sdk]...
Confirm too. It worked before applying the security update last night, and no longer today (Win10). Looks like a quick and dirty fix
Hello, Unfortunatly since our publication of this tool, Palo Alto is now stripping the Etag responses. This tool will only work on legacy versions. And as you can see in...
a new version of the code will be released soon. Some URIs still have the etag enabled, and will enable version detection. Working on identifiying 2-3 years of back log...
Yes it's done. I need to send pr. The time consuming work is the fingerprinting of a lot of versions
I'll send pr tonight. Mostly as it is high topic after today's CVE announcement
adding FortiEDR
Hi, i agree with you @hcompleto in your PR you have more versions. But there is probably a big difference of how I suggest the new versions to compare to...