Add SharePoint Server logs

[respondersGY]

These logs are very useful to detect ToolShell exploitation events

[respondersGY]

Example log line.

Timestamp               Process                                         TID     Area                            Category                        EventID Level           Message         Correlation
MM/DD/YYYY HH:MM:ss  w3wp.exe (XXX)                               XXXX  SharePoint Foundation           General                         XXXX    Medium          Application error when access /_layouts/15/spinstall0.aspx, Error=The file '/_layouts/15/spinstall0.aspx' does not exist.  [...]

[codecov]

Codecov Report

❌ Patch coverage is 38.46154% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 44.93%. Comparing base (884e5fd) to head (8c16bcb).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
acquire/acquire.py	38.46%	8 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #257      +/-   ##
==========================================
+ Coverage   44.80%   44.93%   +0.13%     
==========================================
  Files          26       26              
  Lines        3560     3527      -33     
==========================================
- Hits         1595     1585      -10     
+ Misses       1965     1942      -23     

Flag	Coverage Δ
unittests	44.93% <38.46%> (+0.13%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[respondersGY]

Yes I have tested it and it works.

[respondersGY]

The linter fails, should the try-except be removed?

fix: commands[1]> ruff check --fix acquire tests
acquire/acquire.py:874:13: PERF203 `try`-`except` within a loop incurs performance overhead
    |
872 |               try:
873 |                   spec.add(("path", reg_key.value("LogDir").value))
874 | /             except Exception:
875 | |                 pass
    | |____________________^ PERF203
876 |
877 |           return spec
    |

Found 1 error.

[Schamper]

The linter fails, should the try-except be removed?

fix: commands[1]> ruff check --fix acquire tests

acquire/acquire.py:874:13: PERF203 `try`-`except` within a loop incurs performance overhead

    |

872 |               try:

873 |                   spec.add(("path", reg_key.value("LogDir").value))

874 | /             except Exception:

875 | |                 pass

    | |____________________^ PERF203

876 |

877 |           return spec

    |



Found 1 error.

No, you can add a # noqa: PERF203 comment on that line. I'm not sure on the exact syntax but the Ruff VSCode extension can do that automatically as an IntelliSense fix.