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.
Update: I've disabled comments as of 2025-01-26 to avoid everyone having notifications for something a year on if someone wants to suggest a correction. Folks are free to email to suggest corrections still, of course.
| ## Linux binfmt loaders | |
| `fs/Kconfig.binfmt` defines a few loaders. | |
| * `BINFMT_ELF` defaults to y and depends on `MMU`. | |
| * `BINFMT_ELF_FDPIC` defaults to y when `BINFMT_ELF` is not selected. A few architecture support `BINFMT_ELF_FDPIC` for NOMMU. ARM supports FDPIC even with a MMU. | |
| * `BINFMT_FLAT` is provided for a few architectures. | |
| `BINFMT_AOUT`, removed in 2022, had been supported for alpha/arm/x86-32. |
| ffmpeg -re -i INPUT -c:v libx264 -c:a aac -preset slower -f dash ARBITRARY_NAME.mpd |
| | |
| https://ziglang.org/documentation/master/#Pointers | |
| Local std lib docs: | |
| ```bash | |
| $ zig std | |
| ``` | |
| Browse the std lib code | |
| ```bash | |
| $ vi $(zig env | jq -r .std_dir) |
| -- Roblox's Luau as a Luau script | |
| -- Translated using https://github.com/Rerumu/Wasynth | |
| local luau_script = [[ | |
| print("Hello, World!") | |
| ]] | |
| local Integer = (function() | |
| local Numeric = {} | |
| local NUM_ZERO, NUM_ONE, NUM_SIX_FOUR |
| -------------------------------------------------------------------------------- | |
| -- Batched Yield-Safe Signal Implementation -- | |
| -- This is a Signal class which has effectively identical behavior to a -- | |
| -- normal RBXScriptSignal, with the only difference being a couple extra -- | |
| -- stack frames at the bottom of the stack trace when an error is thrown. -- | |
| -- This implementation caches runner coroutines, so the ability to yield in -- | |
| -- the signal handlers comes at minimal extra cost over a naive signal -- | |
| -- implementation that either always or never spawns a thread. -- | |
| -- -- | |
| -- API: -- |
Discord timestamps can be useful for specifying a date/time across multiple users time zones. They work with the Unix Timestamp format and can be posted by regular users as well as bots and applications.
The Epoch Unix Time Stamp Converter is a good way to quickly generate a timestamp. For the examples below I will be using the Time Stamp of 1543392060, which represents November 28th, 2018 at 09:01:00 hours for my local time zone (GMT+0100 Central European Standard Time).
| Style | Input | Output (12-hour clock) | Output (24-hour clock) |
|---|---|---|---|
| Default | <t:1543392060> |
November 28, 2018 9:01 AM | 28 November 2018 09:01 |
| # The following script (ab)uses the Windows 10 Task Scheduler to create a UAC | |
| # whitelist for applications. | |
| # | |
| # Why? Because Windows does not let you fine-tune your UAC settings. It's | |
| # either you turn off all dialogs and risk some app messing your shit up as it | |
| # runs in a privileged context, or you turn on notifications for everything and | |
| # risk your sanity and hearing loss from the loud bell that chimes through your | |
| # ears every time you want to view your CPU temps or adjust your fan speeds. | |
| # | |
| # Any programs added to the whitelist below will not show a UAC prompt when |
| The 'mizers dream | |
| ================= | |
| The GCC randstruct plugin (randomize_layout_plugin.c) by Open Source Security, Inc., Brad Spengler and PaX Team | |
| allows some sensitive structures in the Linux Kernel to have their layout shuffled. The aim is to obfuscate the | |
| location of sensitive data (e.g some function pointers) and make certain types of exploitation more difficult. | |
| It's explained in detail here: https://lwn.net/Articles/722293/ | |
| The randstruct plugin is built with a randomisation seed included (randomize_layout_seed.h) which is generated | |
| at compile time by the gen-random-seed.sh script: |
TL;DR
