home.social

#bootloaders — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #bootloaders, aggregated by home.social.

  1. 🚀 BEHOLD! The mythical "Serial TTL connector" - because clearly, what humanity needs in 2026 is a mystical journey back to medieval wiring adventures. 🔌✨ Who needs efficient tech when you can fumble with "magic pins" and pretend you're Gandalf summoning bootloaders? 🧙‍♂️
    kohlschuetter.github.io/blog/p #SerialTTLConnector #MedievalWiring #TechHumor #MagicPins #Bootloaders #HackerNews #ngated

  2. 🚀 BEHOLD! The mythical "Serial TTL connector" - because clearly, what humanity needs in 2026 is a mystical journey back to medieval wiring adventures. 🔌✨ Who needs efficient tech when you can fumble with "magic pins" and pretend you're Gandalf summoning bootloaders? 🧙‍♂️
    kohlschuetter.github.io/blog/p #SerialTTLConnector #MedievalWiring #TechHumor #MagicPins #Bootloaders #HackerNews #ngated

  3. 🚀 BEHOLD! The mythical "Serial TTL connector" - because clearly, what humanity needs in 2026 is a mystical journey back to medieval wiring adventures. 🔌✨ Who needs efficient tech when you can fumble with "magic pins" and pretend you're Gandalf summoning bootloaders? 🧙‍♂️
    kohlschuetter.github.io/blog/p #SerialTTLConnector #MedievalWiring #TechHumor #MagicPins #Bootloaders #HackerNews #ngated

  4. 🚀 BEHOLD! The mythical "Serial TTL connector" - because clearly, what humanity needs in 2026 is a mystical journey back to medieval wiring adventures. 🔌✨ Who needs efficient tech when you can fumble with "magic pins" and pretend you're Gandalf summoning bootloaders? 🧙‍♂️
    kohlschuetter.github.io/blog/p #SerialTTLConnector #MedievalWiring #TechHumor #MagicPins #Bootloaders #HackerNews #ngated

  5. 🚀 BEHOLD! The mythical "Serial TTL connector" - because clearly, what humanity needs in 2026 is a mystical journey back to medieval wiring adventures. 🔌✨ Who needs efficient tech when you can fumble with "magic pins" and pretend you're Gandalf summoning bootloaders? 🧙‍♂️
    kohlschuetter.github.io/blog/p #SerialTTLConnector #MedievalWiring #TechHumor #MagicPins #Bootloaders #HackerNews #ngated

  6. GrapheneOS has finally cracked the code for #Motorola devices: unlocking and relocking bootloaders! 🎉 Because nothing screams #innovation like reinventing the wheel. 🔄 Meanwhile, users are too busy trying to decipher if they're on a social network or a failed CAPTCHA test with Mastodon! 🤔
    grapheneos.social/@GrapheneOS/ #GrapheneOS #Bootloaders #Mastodon #SocialNetwork #HackerNews #ngated

  7. @peteorrall

    That enlarges the locus of the problem, unfortunately; as the firmware's CSM could be faulty given that behaviour.

    That said, EFI bootstrap instead of PC/AT MBR is the way to go if one can.

    @rl_dane has posted some recent war stories when it comes to #FreeBSD 15 and #WiFi. They may or may not help.

    #BootLoaders

  8. @peteorrall

    Don't get hung up on the message just because it is something that you can see. As I said, it is very likely a red herring.

    In fact the system *has* proceeded beyond it. It has done other stuff, printed that bootstrap loader version line, and is now doing something else.

    That something else could be reading the firmware memory map using INT 15/E820 or reading ZFS boot information or loading fonts; all three of which happen without printing anything.

    #FreeBSD #BootLoaders

  9. @peteorrall

    The actual message is not, strictly speaking, an error. It just means that you're bootstrapping the non-EFI way, and your machine's firmware does not adhere to a convention (I believe from DOS+Windows 95 and the 1990s) for marking "not an MBR virus and safe" firmware add-on disc device I/O handlers.

    It's unlikely that F000:F0BF is actually unsafe, as that's in (notional) ROM.

    This message is very likely a red herring.

    #RealMode #IA32 #BootLoaders #FreeBSD

  10. @peteorrall

    The actual message is not, strictly speaking, an error. It just means that you're bootstrapping the non-EFI way, and your machine's firmware does not adhere to a convention (I believe from DOS+Windows 95 and the 1990s) for marking "not an MBR virus and safe" firmware add-on disc device I/O handlers.

    It's unlikely that F000:F0BF is actually unsafe, as that's in (notional) ROM.

    This message is very likely a red herring.

    #RealMode #IA32 #BootLoaders #FreeBSD

  11. @peteorrall

    The actual message is not, strictly speaking, an error. It just means that you're bootstrapping the non-EFI way, and your machine's firmware does not adhere to a convention (I believe from DOS+Windows 95 and the 1990s) for marking "not an MBR virus and safe" firmware add-on disc device I/O handlers.

    It's unlikely that F000:F0BF is actually unsafe, as that's in (notional) ROM.

    This message is very likely a red herring.

    #RealMode #IA32 #BootLoaders #FreeBSD

  12. @peteorrall

    The actual message is not, strictly speaking, an error. It just means that you're bootstrapping the non-EFI way, and your machine's firmware does not adhere to a convention (I believe from DOS+Windows 95 and the 1990s) for marking "not an MBR virus and safe" firmware add-on disc device I/O handlers.

    It's unlikely that F000:F0BF is actually unsafe, as that's in (notional) ROM.

    This message is very likely a red herring.

    #RealMode #IA32 #BootLoaders #FreeBSD

  13. @peteorrall

    The actual message is not, strictly speaking, an error. It just means that you're bootstrapping the non-EFI way, and your machine's firmware does not adhere to a convention (I believe from DOS+Windows 95 and the 1990s) for marking "not an MBR virus and safe" firmware add-on disc device I/O handlers.

    It's unlikely that F000:F0BF is actually unsafe, as that's in (notional) ROM.

    This message is very likely a red herring.

    #RealMode #IA32 #BootLoaders #FreeBSD

  14. @peteorrall

    The odd thing is that the linear address does not match the segmented address.

    It's likely not the true cause of your problems, though; but the mis-match might be symptomatic.

    #RealMode #80386 #IA32 #BootLoaders

  15. @peteorrall

    The odd thing is that the linear address does not match the segmented address.

    It's likely not the true cause of your problems, though; but the mis-match might be symptomatic.

    #RealMode #80386 #IA32 #BootLoaders

  16. @peteorrall

    The odd thing is that the linear address does not match the segmented address.

    It's likely not the true cause of your problems, though; but the mis-match might be symptomatic.

    #RealMode #80386 #IA32 #BootLoaders

  17. @peteorrall

    The odd thing is that the linear address does not match the segmented address.

    It's likely not the true cause of your problems, though; but the mis-match might be symptomatic.

    #RealMode #80386 #IA32 #BootLoaders

  18. @peteorrall

    The odd thing is that the linear address does not match the segmented address.

    It's likely not the true cause of your problems, though; but the mis-match might be symptomatic.

    #RealMode #80386 #IA32 #BootLoaders

  19. #Microsoft used its #AI-powered #SecurityCopilot to discover 20 previously unknown vulnerabilities in the #GRUB2, #UBoot, and #Barebox #opensource #bootloaders.
    GRUB2 (GRand Unified Bootloader) is the default boot loader for most #Linux distributions, including Ubuntu, while U-Boot and Barebox are commonly used in embedded and #IoT devices.
    bleepingcomputer.com/news/secu #ITSec

  20. The North Koreans and Russians have been busy, Insiders abound, and attacker tradecraft continues to evolve!

    Catch all this and more in our latest wrap-up of the day's news:

    🗞️ opalsec.io/daily-news-update-m

    There are a few noteworthy stories to get across - here's the TL;DR to get you up to speed:

    🕵️ North Korean Infiltration: This is way bigger than many think. DPRK nationals are landing jobs inside global companies, gaining privileged access ("keys to the kingdom" level!). DTEX reports active investigations in 7% of their Fortune Global 2000 clients, and CrowdStrike notes nearly 40% of their NK-related IR cases involved insiders. They move fast post-hire, pivoting to supply chains and installing RATs disguised as onboarding. Watch out for highly anomalous login behaviour (like days-long sessions!). Rigorous remote hiring checks (camera on, resume checks, comms style) are crucial.

    🎣 ClickFix Tactics by Lazarus: The infamous North Korean group is evolving its 'Contagious Interview' campaign (now dubbed 'ClickFake' by Sekoia). They're targeting crypto job seekers (shifting focus to non-tech roles too!) with fake website/document errors ('ClickFix'). These prompt users to run PowerShell/curl commands, dropping the 'GolangGhost' backdoor. Watch out for lures impersonating giants like Coinbase or Kraken. Sekoia has shared YARA rules – definitely worth checking out.

    💻 WordPress MU-Plugin Abuse: Bad actors are getting stealthy by hiding malicious code in WordPress "Must-Use Plugins" (wp-content/mu-plugins/). These execute automatically on every page load without activation, making them hard to spot. Sucuri is seeing redirects to fake browser updates, webshell backdoors fetching code from GitHub, and JS hijackers replacing content or links. Keep those instances patched, clean up unused plugins/themes, and lock down admin accounts (MFA!).

    Check out what else happened in the past 24 hours, and subscribe to get each edition straight to your inbox:
    📨 opalsec.io/daily-news-update-m

    #CyberSecurity #InfoSec #ThreatIntelligence #Hacking #DataBreach #Phishing #Malware #WordPress #NorthKorea #Russia #Ukraine #AI #SecurityCopilot #GRUB2 #Bootloaders #InsiderThreat #DataProtection #CyberAttack #infosecurity #cybersecuritynews #ClickFix

  21. For those of you who are also deep into Windows #reverseengineering, #bootloaders, and #WinDbg: My first blog post on researching the Windows driver load order and all its quirks is out, beginning with some WinDbg fundamentals: colinfinck.de/posts/nt-load-or

  22. Figured something out myself today. How to “Direct Kernel Boot” #gentoo #linux and removing #grub. Thought I’d make a guide and some scripts for helping out if others also want to try doing this.

    Here is the GitHub gist I made about it if you wanna try it yourself!

    gist.github.com/AFellowSpeedru

    #uefi #efi #bootloaders #computers #technology #gentoolinux #linuxkernel

  23. Asking because my only memory on this is that it breaks on #Ubuntu that happily fills up the place with #kernels and fails to write them, yet updates #grub to point to now non-existing image.

    But I believe that there will be a real reason? Like #bootloaders not being able to use the modern filesystems or something?

  24. At least for my time spent on my day off, I got a nice lesson in #BTRFS and #bootloaders, as well as a refresher on partitioning schemes and the basics if settings up #Linux

  25. netbootxyz is a network-based bootable operating system installer based on iPXE.

    github.com/netbootxyz/netboot.

    Pretty useful if you have the weird job/hobby of installing multiple operating systems to “places” and you want an all-in-one bootloader to ease your pain.

    #tools #installers #bootloaders #ipxe #pxe #linux

  26. netbootxyz is a network-based bootable operating system installer based on iPXE.

    github.com/netbootxyz/netboot.

    Pretty useful if you have the weird job/hobby of installing multiple operating systems to “places” and you want an all-in-one bootloader to ease your pain.

    #tools #installers #bootloaders #ipxe #pxe #linux

  27. Locked #bootloaders:

    Hard disagree that a lock on one's computer is somehow "good for security" unless the user, not the vendor, owns key ... and lock.

    Hard disagree that vendor lock-in is in any way "good for users".

    Hard disagree that less freedom to move to free software is in any way "good for users".

    Hard disagree that reliance on single points of trust (i.e. failure (of trust)) is in any way "good for users".

  28. Writing a bootloader that sits between shim and grub (for reasons™) was “fun”.

    You have to relocate the PE image of your next stage by hand, fake up your loaded-image struct contents, determine the entry point and jump to it.

    You must also use the right calling convention (define GNU_EFI_USE_MS_ABI at compile time) and _not_ tag efi_main (or wherever you jump to the next entry point from) as EFI_API.

    Don't ask how long it took me to figure out those last two.

    #programming #bootloaders