This is a diff between the xz-embedded repositories listed on github and at git.tukaani.org.
$ git remote -v
github https://github.com/tukaani-project/xz-embedded (fetch)
github https://github.com/tukaani-project/xz-embedded (push)
origin https://git.tukaani.org/xz-embedded.git (fetch)
origin https://git.tukaani.org/xz-embedded.git (push)
This is a living document. Everything in this document is made in good faith of being accurate, but like I just said; we don't yet know everything about what's going on.
On March 29th, 2024, a backdoor was discovered in xz-utils, a suite of software that
Note: this is an ongoing process which I'm documenting here. Semi-experimental, but this is my daily driver machine since September 2021 (work included), so I'm aiming for stability (hence why I'm not using the recommended Fedora 39 Beta).
Upgraded from an Intel i7-1165G7 to AMD 7080U mainboard:
These notes are for Fedora 38 6.5.8-200.fc38.x86_64 with SwayWM.
Booted into Fedora with BIOS 3.02 and seemed fine. First thing I did was upgrade to 3.03.
| // code updates are now there: | |
| // https://github.com/Bleuje/processing-animations-code/blob/main/code/fractalsliding2d/fractalsliding2d.pde | |
| // Processing code by Etienne JACOB | |
| // for collab with Yann Le Gall (https://demozoo.org/graphics/322553/) | |
| // motion blur template by beesandbombs | |
| // See the license information at the end of this file. | |
| // View the rendered result at: https://bleuje.com/gifanimationsite/single/2dfractalslidingsquares/ | |
| // using double instead of float makes the code a bit more complicated |
| First in pulsview set the log level to 5. | |
| If the error is fx2lafw: unable to get version info: libusb_error_timeout. | |
| Then to fix it install the firmware with: | |
| apt install sigrok-firmware-fx2lafw |
| Assuming you have followed all the steps to install / setup WSL2 -> https://docs.microsoft.com/en-us/windows/wsl/install-win10 | |
| **Tested on Ubuntu 20.04** | |
| Step 1 - Find out default gateway and DNS servers | |
| - Navigate to `Control Panel\Network and Internet\Network Connections` | |
| - Right click on relevant connection type WiFi or Ethernet and select `Status` | |
| - Status screen will be displayed, click on `Details` button | |
| - Network Connection details screen will be displayed | |
| - Note down `IPv4 default gateway` and `IPv4 DNS Servers` if available |
| ffmpeg -i http://192.168.2.11:80/sdi_ext -c:v copy -f hls -method PUT -hls_time 1 -hls_playlist_type event -http_persistent 1 'https://a.upload.youtube.com/http_upload_hls?cid=KEY©=0&file=stream.m3u8' |
I was switching to a new computer today and wanted to install all the flatpaks on my old one, without having to do anything manually of course
It turned out to be pretty easy, but I didn't find any obvious guide on the internet, so I figured I would document my solution
At first I tried the command:
flatpak list --app --columns=application > installed_flatpaks.txt
This will give you a list of only the application ID's, but each will be on a newline
The issue is that each ID is on its own line. To fix this, I added a second part to the command:
flatpak list --app --columns=application | xargs echo -n > installed_flatpaks.txt
| <?php | |
| use TYPO3\CMS\Core\Context\Context; | |
| use TYPO3\CMS\Core\Utility\GeneralUtility; | |
| // ... | |
| $context = GeneralUtility::makeInstance(Context::class); | |
| /** @var TYPO3\CMS\Core\Site\Entity\Site */ |
I wanted to integrate the camera into my home security system. The only problem is that I want to toggle the alarm of the camera based on the security system status. Currently, this is only available via the app or a time trigger which is booth not sufficient for me. So the main target was to change the alarm status without the app.
My first try was to capture the TCP packages between the Android app and the camera. Soon I realized that they are only TCP+SSL (not pinned) requests to a cloud service of Hikam. So I installed an emulator with the Hikam app and Wireshark. I've seen some packages but the payload is very strange and even if I send the UDP commands again the status won't change. So this was a dead end for me.
