it's this little fucker in the tray spying on you because microsoft thinks normies are too stupid to understand when their internet is not working
| ! Feed | |
| www.reddit.com##shreddit-feed | |
| ! Top carousel | |
| www.reddit.com##shreddit-gallery-carousel | |
| ! Recommended posts in sidebar | |
| www.reddit.com##reddit-pdp-right-rail-post |
| # Documents | |
| *.doc binary | |
| *.docx binary diff=pandoc | |
| *.xls binary | |
| *.xlsx binary | |
| *.xlt binary | |
| *.xltm binary | |
| *.pdf binary | |
| *.ppt binary |
Original report
- Affected Vendor: OpenPrinting
- Affected Product: Several components of the CUPS printing system: cups-browsed, libppd, libcupsfilters and cups-filters.
- Affected Version: All versions <= 2.0.1 (latest release) and master.
- Significant ICS/OT impact? no
- Reporter: Simone Margaritelli [[email protected]]
- Vendor contacted? yes The vendor has been notified trough Github Advisories and all bugs have been confirmed:
| // gcc -shared -fPIC -I/usr/local/cuda-12.0/targets/x86_64-linux/include/ hook.c -o hook.so -ldl && LD_PRELOAD=./hook.so python3.11 obfuscated_file.py | |
| // Thanks Claude! | |
| #include <nvml.h> | |
| #define _GNU_SOURCE | |
| #define PAGE_SIZE 4096 | |
| #include <stdio.h> | |
| #include <dlfcn.h> |
I was trying to apply some Windows updates (specifically KB5048652) and it was failing. The system would reboot and try to apply the update (where it spins before the login screen), fail to apply the update, undo the update, and reboot.
Checking C:\Windows\Logs\CBS\CBS.log, I saw poqexec.exe failing on HRESULT 0x80071AB1 - ERROR_LOG_GROWTH_FAILED.
This HRESULT means
An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log.
Log here might give the impression of a log file, but I think it is actually related to "log" in the concept of "transaction log for commit and rollback" like in databases. For an update service, I'd expect Windows wants the filesystem to have some kind of transaction mechanism so failed updates can be cleanly and safely rolled back. I'm not an engineer at Microsoft and I am just speculating, so I could be wrong.

