alchemio (u/alchemio)

alchemio commented on The C++ standard for the F-35 Fighter Jet [video] youtube.com/watch?v=Gv4sD... · Posted by u/AareyBaba

elteto · 6 days ago

Not exactly sure what your experience is, but if you work with in an -fno-exceptions codebase then you know that STL containers are not usable in that regime (with the exception of std::tuple it seems, see freestanding comment below). I would argue that the majority of use cases of the STL is for its containers.

So, what exact parts of the STL do you use in your code base? Most be mostly compile time stuff (types, type trait, etc).

alchemio · 6 days ago

You can use std containers in a no-exceptions environment. Just know that if an error occurs the program will terminate.

alchemio commented on No Leak, No Problem – Bypassing ASLR with a ROP Chain to Gain RCE modzero.com/en/blog/no-le... · Posted by u/todsacerdoti

kingforaday · a month ago

You typically don't see ASLR enabled on these armhf embedded devices. I see the statement by the author, " quickly confirmed on the device that address space layout randomization (ASLR) was enabled...", but how was it quickly checked? What was the output of /proc/sys/kernel/randomize_va_space?

Also not familiar at all with the checksec program, but from my look at the documentation, you expect to see PIE enabled not DSO (which implies dynamic shared object).

alchemio · a month ago

checksec is part of the pwntools suite. Along with other tools for finding ROP gadgets and shellcode generation.

alchemio commented on No Leak, No Problem – Bypassing ASLR with a ROP Chain to Gain RCE modzero.com/en/blog/no-le... · Posted by u/todsacerdoti

alchemio · a month ago

The most shocking part is the absence of stack canaries. I know there are issues with them on microcontrollers, but still I would assume they’re enabled by default by the compiler.

alchemio commented on Stdio(3) change: FILE is now opaque undeadly.org/cgi?action=a... · Posted by u/gslin

notepad0x90 · 5 months ago

it's already not working that way in Linux, it's just that there is no rhyme or reason to it. Even on stable Debian I have to have pipx/pyenv/venv for python and juggle multiple versions of rust and go because of mismatches between software and distro versions.

alchemio · 5 months ago

Python, rust and Go aren’t beacons of software stability though.

alchemio commented on Memory Safety Features in Zig gencmurat.com/en/posts/me... · Posted by u/todsacerdoti

alchemio · 7 months ago

Zig’s general purpose allocator might detect use after free in debug builds, however zig appears to be ok with dangling (invalidated) pointers/slices and use after free for stack variables, which is more concerning, especially from a security standpoint.

```zig

const std = @import("std");

fn get_ptr() i32 { var a: i32 = 6; return &a; }

pub fn main() void {

    var x: ?*i32 = undefined;
    {
        var a: i32 = 5;
        x.? = &a;
    }
    std.debug.print("{} {}", .{ x.?.*, get_ptr().* });

}
``` These are trivial examples that Zig doesn’t even warn about, even though similar code in C or C++ gets a warning in gcc and clang.
This discussion:
https://ziggit.dev/t/what-makes-ban-returning-pointer-to-sta...
indicates that core zig devs aren’t interested in diagnosing such usage.

alchemio commented on Asahi Linux lead developer Hector Martin resigns from Linux kernel lkml.org/lkml/2025/2/7/9... · Posted by u/Mond_

steveklabnik · 10 months ago

It's nonsense because if his C code breaks the Rust binding or drivers, that is not his problem. It adds zero maintenance for him.

alchemio · 10 months ago

But it does. He has to notify R4L of what his changes were and how it broke the Rust driver. Even if he didn’t, he will still be contacted for information regarding these things.

alchemio commented on Asahi Linux lead developer Hector Martin resigns from Linux kernel lkml.org/lkml/2025/2/7/9... · Posted by u/Mond_

steveklabnik · 10 months ago

The person who quit was not the author of the patch, or a member of Rust for Linux.

alchemio · 10 months ago

So they stirred a whole lot of drama for not much, potentially harming R4L.

alchemio commented on ruffle-rs/ruffle: A Flash Player emulator written in Rust github.com/ruffle-rs/ruff... · Posted by u/rcarmo

alchemio · a year ago

Flash apps and Java applets (via Cheerp) can run again in browsers thanks to wasm.

alchemio commented on Microsoft donates the Mono Project to the Wine team mono-project.com/... · Posted by u/itherseed

alchemio · a year ago

Embrace, Extend, Extinguish, Endow

alchemio commented on Curl will be dropping Hyper due to lack of maintenance github.com/curl/curl/blob... · Posted by u/pjmlp

alchemio · a year ago

> It is undoubtedly hard work to fix these remaining problems, as they typically require both rust and C knowledge in addition to deep HTTP familiarity. There does not seem to be that many persons interested or available for this challenge. Meanwhile, there is little if any demand for hyper from existing (lib)curl users.

You might as well replace HTTP with OS, hyper with rust and curl with linux, and you get the current situation with Rust adoption on Linux.

u/alchemio

KarmaCake day55May 18, 2023View Original