Skip to content

Piero Bosio Social Web Site Personale Logo Fediverso

Social Forum federato con il resto del mondo. Non contano le istanze, contano le persone

There's a lot that's been said to new people arriving from bluesky about mastodon, how it works etc, and so in a similar vein I'd really just like to say to our new bsky friends:'nshow me a picture of your cat

Uncategorized
7 5 0

Gli ultimi otto messaggi ricevuti dalla Federazione
  • OK, it turned out to be pretty fun. A lot of the work was looking up various arguments for pox classes and methods, but in the end it's a pretty tight firewall implementation that is passing the test suite. Yippee!

    read more

  • @evan Oooh, you caught a new Teeny Void Demon in the cat trap! What a perfectly seasonal addition to the family, congrats.

    And welcome, Corvus! My black-but-for-that-silly-pointing-mutation Sudo sez "YOOOOWWWWWLLLOOOOooooo".

    read more

  • Making a Virtual Machine Look like Real Hardware to Malware

    Running suspicious software in a virtual machine seems like a basic precaution to figure out whether said software contains naughty code. Unfortunately itโ€™s generally rather easy to detect whether or not oneโ€™s software runs inside a VM, with [bRootForce] going through a list of ways that a VirtualBox VM can be detected from inside the guest OS. While there are a range of obvious naming issues, such as the occurrence of the word โ€˜VirtualBoxโ€™ everywhere, there many more subtle ways too.

    Demonstrated is the PoC โ€˜malwareโ€™ application called Al-Khaser, which can be used to verify oneโ€™s anti-malware systems, such as when trying to unleash a debugger on a piece of malware, run it inside a VM, along with many more uses. Among its anti-virtualization features are specific registry key names and values, file system artefacts, directory names, MAC addresses, virtual devices, etc.

    In order to squeeze by those checks, [bRootForce] created the vbox_stealth shell script for Bash-blessed systems in order to use the VirtualBox Manager for the renaming of hardware identifier, along with the VBoxCloak projectโ€™s PowerShell script thatโ€™s used inside a Windows VirtualBox guest instance to rename registry keys, kill VirtualBox-specific processes, and delete VirtualBox-specific files.

    Theoretically this should make it much harder for any malware to detect that itโ€™s not running inside Windows on real hardware, but as always there are more subtle ways that are even harder to disguise.

    youtube.com/embed/-On6bWFXuM8?โ€ฆ

    hackaday.com/2025/10/27/makingโ€ฆ

    read more

  • On that note, we have a new member of our family. His name is Corvus. He is smol but mighty. We like him alot. /cc @maj @amita @Stavro

    read more

  • read more

  • @evan Can I write it in PHP as long as I call the python library somehow?

    read more

  • Tutti gli psicodrammi in Apple sullโ€™Ai

    L'articolo proviene da e viene ricondiviso sulla comunitร  Lemmy @informatica
    Presa in contropiede da Trump, che l'ha costretta a indirizzare 500 miliardi in piani di sviluppo negli Usa, Apple continua a essere in difficoltร  sul fronte Ai. Siri, dopo tanti rinvii, non puรฒ certo piรน mancare il debutto del prossimo

    read more

  • Are you on the Fediverse because you love social networking, or because you hate social networking?

    read more
Post suggeriti
  • 0 Votes
    1 Posts
    0 Views
    Making a Virtual Machine Look like Real Hardware to MalwareRunning suspicious software in a virtual machine seems like a basic precaution to figure out whether said software contains naughty code. Unfortunately itโ€™s generally rather easy to detect whether or not oneโ€™s software runs inside a VM, with [bRootForce] going through a list of ways that a VirtualBox VM can be detected from inside the guest OS. While there are a range of obvious naming issues, such as the occurrence of the word โ€˜VirtualBoxโ€™ everywhere, there many more subtle ways too.Demonstrated is the PoC โ€˜malwareโ€™ application called Al-Khaser, which can be used to verify oneโ€™s anti-malware systems, such as when trying to unleash a debugger on a piece of malware, run it inside a VM, along with many more uses. Among its anti-virtualization features are specific registry key names and values, file system artefacts, directory names, MAC addresses, virtual devices, etc.In order to squeeze by those checks, [bRootForce] created the vbox_stealth shell script for Bash-blessed systems in order to use the VirtualBox Manager for the renaming of hardware identifier, along with the VBoxCloak projectโ€™s PowerShell script thatโ€™s used inside a Windows VirtualBox guest instance to rename registry keys, kill VirtualBox-specific processes, and delete VirtualBox-specific files.Theoretically this should make it much harder for any malware to detect that itโ€™s not running inside Windows on real hardware, but as always there are more subtle ways that are even harder to disguise.youtube.com/embed/-On6bWFXuM8?โ€ฆhackaday.com/2025/10/27/makingโ€ฆ
  • 0 Votes
    1 Posts
    0 Views
    Are you on the Fediverse because you love social networking, or because you hate social networking? #EvanPoll #poll
  • 0 Votes
    5 Posts
    0 Views
    OK, it turned out to be pretty fun. A lot of the work was looking up various arguments for pox classes and methods, but in the end it's a pretty tight firewall implementation that is passing the test suite. Yippee!
  • <3 #debian

    Uncategorized debian
    2
    1
    0 Votes
    2 Posts
    0 Views
    @governa ๐Ÿ’ช