Bug: Audit log entries are written to files with old timestamps
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- observability
Research direction
Start at src/linux/server/Main::main(), where the plog loggers are created, and trace how their file paths are determined and used for audit entries. Reproduce the issue by comparing the installation date with a later log-entry date; done means entries are written to a file whose timestamp matches the date of those entries.
Written by the indexing model from the issue text.
Description
Describe the bug
The plog loggers are created in the beginning of src/linux/server/Main::main(), which only gets executed one-time when the netremote server is installed on a system. The date of installation is used for the log file path, e.g. 20240730-LogNetRemote-audit.txt. This means that if netremote is used on a future date (e.g. 20240801), then those log entries will still write to 20240730-LogNetRemote-audit.txt.
Steps To Reproduce
- Install netremote-server.
- On a future date, perform a Wi-Fi action that causes an entry to be written to the audit log.
Expected behavior
Audit log entries should be written to a log file that has the timestamp of the same date of the log entries themselves.
Actual behavior
Audit log entries are written to the log file that has the timestamp from the installation date.
Example output
cat /var/log/20240724-LogNetRemote-audit.txt
2024-07-24 18:34:18.078 NONE [36787] [main@109] Netremote server starting (log level=info)
2024-07-30 17:25:01.429 INFO [36824] [Microsoft::Net::Wifi::AccessPointControllerLinux::SetOperationalState@159] Operational state of AP wlo1 set to 'disabled'
- Dominant language
- C++
- Stars
- 20
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/netremote
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
bug
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
All issues in microsoft/netremote
Similar issues
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mlcommons/mobile_app_open#1182 ·
-
Needs-Triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/winget-cli#6547 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·