27 lines
1.6 KiB
Markdown
27 lines
1.6 KiB
Markdown
# firewallissues
|
|
An alternative view of issues documented by our favorite firewall vendor.
|
|
|
|
Feel free to host your own version, or use [the one I host](https://firewallissues.axvig.com/).
|
|
|
|
Inspired by [Pixi888's](https://www.reddit.com/user/Pixi888/) creation [bugidsearch.com](https://bugidsearch.com/).
|
|
|
|
## Data updates ##
|
|
Known and addressed issues for newly released versions are easily added using the process.html page
|
|
- Copy the issue table's HTML from the webpage using devtools.
|
|
- Fill out the process.html page's fields and paste in the table HTML.
|
|
- Download the Markdown file and put it into the correct folder.
|
|
- Fix up the products.json file manually or run `update_products_from_issues.py`.
|
|
- Submit a pull request.
|
|
|
|
The date on the end of the Markdown file names is to have some idea of when the data was grabbed. I would imagine that sometimes there are updates. (I plan to remove the dates in the future. The git history should be sufficient.)
|
|
|
|
There is intentionally no automated scaping of Palo Alto's website, to avoid abuse of server resources. Also releases are not that frequent. A crawler to grab some data from the Common Crawl dataset was started but never really finished.
|
|
|
|
Some data was collected early on when the HTMLTable -> Markdown code was kind of bad, so the formatting of the issue write-up tends to be bad on those. Mostly PAN-OS 10 and 11 stuff.
|
|
|
|
## External references ##
|
|
|
|
The `external_refs.json` file allows for links to be added to other websites that have information or discussion about certain issues.
|
|
|
|
I have vague ideas of something similar for CVEs.
|