News for hackers. Stuff that matters.

alschwalm

Re:The LD_DEBUG environment variable (2012) on Tuesday June 09, 2026 @03:55PM (#48466749)
LD_AUDIT is another one worth knowing about (though I admittedly use it less often than LD_DEBUG) https://man7.org/linux/man-pages/man7/rtld-audit.7.html
Yeah, that was my assumption as well, good to have it confirmed though. Thanks for your excellent work on bytehound!
Interesting approach. How is performance compared to something like https://github.com/koute/bytehound
Re:Show HN: Unblob – extraction suite for 30+ file formats on Wednesday January 18, 2023 @06:59PM (#34434902)
Looks nice! Kind of reminds me of binwalk: https://github.com/ReFirmLabs/binwalk
I'm curious how the benchmarks are for Btrfs on 6.1, given the improvements that (I think) landed in it: https://www.phoronix.com/news/Linux-6.1-Btrfs
Re:Lisp-Stick on a Python on Monday November 14, 2022 @04:38PM (#33601537)
Looks like it: https://docs.hylang.org/en/stable/api.html#let

I recall hearing it had been implemented a while back, seems like it's true!

Re:Nyxt 3 Pre-release 1 (a Lisp powered web browser) on Thursday July 14, 2022 @01:46PM (#32099253)
I've also hit this issue. About a year ago I made an effort to use blink, but after a bit of work I recall essentially discovering that any support was effectively abandoned. I wish they would remove the note in the FAQ about supporting multiple engines, as it doesn't seem to be the case.
Re:The Little Book of Rust Macros on Sunday November 21, 2021 @11:56AM (#29297718)
It is definitely also worth mentioning the now-stabilized procedural macros [1] (unless I missed where they are described). proc macros power some of the more complex macro usage in the rust ecosystem (like rocket and actix-webs router macros, any sort of custom derive, etc).

[1]: https://doc.rust-lang.org/reference/procedural-macros.html

Re:Ask HN: Who wants to be hired? (August 2021) on Monday August 02, 2021 @11:45AM (#28038183)

  Location: Huntsville, AL, USA
  Remote: Yes
  Willing to relocate: No
  Technologies: Rust, C, C++, python, Xen, KVM, hypervisor development, Linux kernel development, IDA Pro
  Résumé/CV: https://alschwalm.com/resume/resume.pdf
  Email: [email protected]
I am currently a technical lead for a hypervisor product. My career has primarily been focused on low-level security and performance for quasi-embedded systems, but I also have experience with reverse engineering and machine learning applications. I am passionate about using modern technologies like rust to improve the security posture of products and would like to continue to work in that area.
https://github.com/alschwalm/transient - A tool for quickly creating short-lived virtual machines for doing kernel or hypervisor testing, made after I got tired of dealing with races and general complexity from libvirt-based tools.
Re:Linux Hypervisor Setup (Libvirt/QEMU/KVM) on Saturday May 01, 2021 @11:11AM (#27006926)
VirtIO is very usable via QEMU, without libvirt (naturally, because in the configuration described in the article, libvirt is just calling QEMU). It is usually as simple as `qemu-system-x86_64 -drive file=/path/to/my/disk,if=virtio`.
Re:1Password for Linux beta on Wednesday October 21, 2020 @05:05PM (#24852171)
I'm concerned about self hosting a service like this as well, so I put mine behind an nginx reverse proxy that requires a client cert for auth. That way, an attacker won't even be able to reach the bitwarden server to try to get in (unless there's a vulnerability in nginx).
We were actually previously using vagrant (-libvirt) for our CI, but moved away from it to this because vagrant does not seems to work very reliably when run in parallel. For example image downloading doesn't seem to have a filesystem lock, so one would succeed and the others failed.

In general, we wanted to be able to spin up our test VMs under docker containers to eliminate issues with differences between our CI shell-runners. Using libvirt based tooling makes that pretty hard. Calling to qemu directly, on the other hand, makes this easy.

There are some other benefits as well such as having direct console access which is not provided by vagrant, but can be very useful for kernel tests.

Re:Zero Cost Abstractions on Thursday May 16, 2019 @03:14PM (#19932063)
There is a typo under the 'optimal performance' section. "A zero cost _abstractoin_ ought..."
Re:United States v. Microsoft Corp. Dismissed [pdf] on Tuesday April 17, 2018 @12:56PM (#16860094)
Shameless plug: If you enjoy that, you may like a version that I made that sinks the audio and transcripts with puppies[1], available here: https://www.youtube.com/channel/UCn1ibFnn3NcXjQHY47o0yWg/vid... Though this particular case is not available yet.

[1]: The idea was originally inspired by Last Week Tonight, I just automatically generate them.

Wow this is really detailed. Thanks!
The keyboardio is the only keyboard I know of that has the palm keys, but I've been interested in buying or making a keyboard that has them. Any writup on your build?
Re:Why Is It Taking 20 Minutes to Mine This Bitcoin Block? on Monday February 26, 2018 @05:36PM (#16469618)
The article on the "hitchhiker's paradox" that this links to made this much more clear to me (as well as being shorter): https://the8layers.com/2016/10/30/how-long-will-you-wait-hit...
I tend to like https://www.draw.io/ for that sort of thing (there is a chrome app if you want to run offline).

Older »