@parzivalwolfram@infosec.exchange

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2mo ago

Replying to

@niconiconi@mk.absturztau.be you forgot the better option: "the Linux driver was rewritten from scratch and is now infinitely better but it's not 80 column compliant so it's forever stuck as a random git repo no one will ever find, and reliant on dkms to use it."

14

0

2

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

(back from break) that's precisely what happened. I had to rebuild like 2 things total because that library and grep were all that was left from early build lmao

1

7

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 1mo ago

Replying to

pictured: shit's broke (the fun part is the only answer I can find at all other than "lol no results" for the symbol name, is the AI answer of "lol glibc broke, contact your dealer." BITCH THIS IS SOLARIS 7 THERE IS NO GLIBC) i'm assuming upgrading binutils to 2.25 and gcc to 6.5.0 has broken something behind the scenes and now my custom fix-my-shit library is unable to link to GCC 2.95.3 libgnu.

1

8

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2mo ago

Replying to

@whitequark@social.treehouse.systems if you really want to flex, i believe you can build 3.10 for WinXP, if your code doesn't need newer Python

1

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2mo ago

Replying to

@xyla@shitpost.trade the baby badge-in enforcement system is getting wildly out of hand if it's mandatory to buy a TV

1

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3mo ago

Replying to

of course I fix time.h so everything's not locked behind a million ifdefs for K&R support and the like, and gcc-6.5.0 starts segfaulting on libquadmath mid-build (and the --disable-libquadmath flag for configure doesn't work, because why would it?)

1

9

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3mo ago

Replying to

i have skipped over half the compiler BUT IT FUCKING WORKS now i just have to get libstdc++ and libatomic to build lol

1

11

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

ah yes, i'm chasing doen a bug where all versions of binutils after 2.17 claim all files are truncated, i accidentally turn off my custom headers for one pass of binutils-2.20.1 and the bug disappears. why is ONLY binutils affected by this and something like gcc 4.5.4 or python 2.7.16 or SDL2 2.30.0 isn't?

1

16

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 5mo ago

Replying to

@xyla@shitpost.trade nice try, but you'll NEVER know how old my kernel is!

1

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 5mo ago

Replying to

Ah yes, we're now segfaulting in, uh... ...ah, fuck, that's init code isn't it? we're not even *in* the ELF yet, are we?

1

21

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 5mo ago

Replying to

No, no it's so much worse than that: libbfd only cares if you have fseeko64 for 64-bit host support. which we do, but it's a lie, and it doesn't just use FILE_OFFSET_BITS in that case, it uses a whole different half of the fucking makefile and undefines FILE_OFFSET_BITS entirely. Oh boy.

1

23

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 6mo ago

Replying to

tragic: GCC fails to link to any library containing symbol "operator new[](void *)", is asked to leave build folder. Onlookers added context at the scene: "What the fuck is GCC doing, that's not how you link to a function. I don't think symbols can even have spaces in their names?"

1

25

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

Perl, can you stop being a dick for five seconds? I have the build system set up specifically for a reason, obey my settings!

1

33

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

Solaris 7 Pro Tip: after installing XFree86 and getting it set up, use the following one-liner to get it to take over the display server: echo ":0 Local local_uid@console root /usr/X11R6/bin/X" > /usr/dt/config/Xservers && reboot

(nowhere in the docs is this clear at all, and the docs lie in general.)

1

34

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

i can't even build binutils-2.13.2.1 anymore, which came before GCC in general earlier. i hate this shit dude it's rotting BEFORE MY EYES

1

36

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

it appears it's time once again.

1

35

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

I've had friends suggest things during the duration of this project, some suggestions are helpful and some are very much not: "Rebuild your scripts, they're ass and hard to maintain" - helpful, broke shit but needed done. "You saw that one Unix book in that store, right? Buy it if it has the CD, i'll just give you the money." - Suspicious, but helpful, contained a lot of good hints and also seemingly lost versions of a lot of GNU software that I can bootstrap with suncc. archive.org listing soon. "Just port glibc!" - trust me buddy, i've tried, it's not as easy as "add sysdefs lmao" like they make it out to be and they removed the ability to port it in like 2014 "Just port GCC !" - god no could you imagine how fucking hard it would be to deal with the macro hell in there? "Just use modern Linux" - not helpful, that's no fun. "Use rust lmao" - not helpful, even taking it seriously I'd have to add full C98/C11/C++11 at minimum to build the vendored LLVM and if I could do that the issue would be over anyways. "Build your own compiler equivalent to GCC !" - i'm not smart enough to not fuck up the system headers, and you want me to do WHAT

1

37

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 9mo ago

Replying to

$ cat sys-patch.sh #Go To Jail For Your Linker Crimes mkdir -p /usr/jail mv /usr/ccs/bin/as /usr/jail/as.orig mv /usr/ccs/bin/ld /usr/jail/ld.orig

1

41

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 5mo ago

Replying to

Ah! Once again, vbox bites me in the ass: most things trust CPUID, *except* libbfd, which seems to build assembly files to test your processor's real capabilities. This might be where all these SIGILLs are from: vbox is masking CPUID, but libbfd is still picking up HOST_BFD_64_BIT on a 32-bit OS.

0

24

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 5mo ago

Replying to

Yup, looks like an ld.so.1 bug in Solaris 7. https://gcc.gnu.org/pipermail/gcc-bugs/2002-October/064911.html It is interesting that they have working gdb, though, i'll have to see if 5.0 builds, as it'd be infinitely easier to use than fucking adb.

gcc.gnu.org

target/8004: All C++ binaries crash in __register_frame_info_bases on Sparc Solaris 2.7

0

20

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 5mo ago

Replying to

see, this is an issue because sol7 defines both long long and int64/uint64 as union(int32*2,double) "for alignment purposes", as you're not meant to actually try to USE them, and fseeko64 is long long, so it's completely valid. After staring into adb (no, not the Android kind) for way too long, it appears what the SIGILLs and SIGSEGVs are from is it's encoding constants into ELF files as 64 bits, inline, as i've noticed almost all of the SIGILLs happen directly after a register store, so something like "mov r32,imm32" and then an illegal 4-byte "instruction." Sounds a lot like it's emitting a 64-bit imm32, which would explain why it's so flaky: the first 32 bits might make it into the register, and then the second 32 fucking don't and might or might not be a valid opcode (the second 32 bits are usually not \x00, so i'm assuming something's also going wrong with the offsets, as no normal ELF is going to be a few terabytes into the address space on a fucking 486.)

0

22

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

oh wow, having a working linker... makes things actually work! who would've thought?

0

17

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

uh oh perl, did you ignore the -ggdb flag?

0

31

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

not only is string comprehension broken when generating the Makefile, a few of the tests are broken due to uninitialized vars or unknown commands. Also, it's got the same bug where a colon means a domain is invalid. I'm starting to think Perl might also be busted in some way, as well...

0

5

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

ah yes, we can BUILD binutils-2.20.1, but if you EVER try to install it it eats shit on INSTALLING a static library. literally how

0

39

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

we have stdatomic. thank you to Jens Gustedt, who put together a libatomic I could understand enough to get working. https://gitlab.inria.fr/gustedt/stdatomic

gitlab.inria.fr

GUSTEDT Jens / stdatomic · GitLab

0

29

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

are build success reports for this platform even helpful if I've had to patch both the program AND the tests? something like patching around MAP_ANON being missing and not being confident at all that it's correct, but it is working? I probably shouldn't submit those, right?

0

30

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

It won't build GCC 4.9... but it WILL build stage1 of GCC 6.5.0, which was a complete "this will be funny for the thread lmao" move that seems to have paid off????? this is gonna be crushing later when it doesn't work in like stage3 and can't easily be fixed

0

5

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

so it turns out at some point in 2003 they fixed the bug and put out a patch for this. for those googling later, it's in the Recommended patch clusters from 2006-ish. (patch ID is 106951-25 for x86, 106950-24 for SPARC.)

0

19

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2mo ago

Replying to

@ralen@social.ralen.top "The POSIX APIs are insecure and outdated..." [citation needed] "...and we don't even want them anyway..." because you're not allowed at the cool kids table? "...but we can't invent a new OS ourselves, so we'll just invent a new kernel with a POSIX shim." no, you won't, because then you won't benefit from free Android security patches and infinitely less people will want to write drivers for your shitass custom kernel.

0

2

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

yeah something is HORRIBLY wrong if it's whipping out statements like "could not load config file at line 134563624", is it Perl or OpenSSL that's busted though?

0

4

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

gdb be like "yeah we need to make this library. oh but we can't actually because the un-built library is missing sorry"

0

2

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

well that gives me binutils-2.25.1 before stdint.h is a hard requirement so there's that, i guess. Let's see if that'll build gcc 4.9 with its weird-ass C++ linking behavior.

0

15

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

yeah i think it's Perl, I missed that it's trying to stat the test-generated config files *out of the root folder* which is why most of them died. this is gonna suck, isn't it?

0

3

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 1mo ago

Replying to

@epicness@shitpost.trade i think containment's leaking out of a sharp corner here guys

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 7mo ago

Replying to

yes thank you gcc, "a != a"

0

28

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2w ago

Replying to

as usual, the documentation is lies. --with-default-trust-store-dir= doesn't exist in gnutls configure despite saying it does online, and curl won't acknowledge non-symlink certificates. fixing update-ca-certificates and moving gnutls to the stupid fucking combined cert fixed everything.

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 7mo ago

Replying to

Again? Again. Earlier, this time. This worked an hour ago, and now by the magic of "here's off_t" we've toasted wchar.h, which has never once needed a patch before. what

0

18

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2mo ago

Replying to

@ralen@social.ralen.top Directly after the post you linked to: https://grapheneos.social/@GrapheneOS/116975921189817720

grapheneos.social

GrapheneOS: "@FediFollows@social.growyourown.services @wariat@…" - GrapheneOS Mastodon

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

this has taken forever, hopefully it works. i'd love to say Solaris 7 is now up to the current OpenSSL LTS. 1.1.1w does work, as well, but has some kind of string parsing bug where "127.0.0.1" is a valid domain but "127.0.0.1:443" isn't, despite the tests using both interchangeably.

0

6

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

"how is this un-debuggable" the default debugger, adb, doesn't catch subprocesses' segfaults, can't pass argv to things, and generally sucks dick. I have yet to find a version of gdb that doesn't build fine but immediately segfault on running a process.

0

12

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 2w ago

Replying to

@whitequark@social.treehouse.systems i was going to port this to solaris 7 For The Funny but cmake 3.x is almost impossible to get working on non-Linux *nixes and I don't think ruby is going to play nice long enough to work correctly either.

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

yeah, there's the undebuggable segfault. it took a while, it got most of the way through libstdc++-v3

0

4

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 9mo ago

Replying to

this legitimately instantly fixed a hundred things because several GNU makefiles reset your PATH at some point and if you're trying to avoid default linker/etc, suddenly resetting the path tends to revert back to them, even with "LD=/very/specific/full/path/to/ld" and such.

0

40

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 7mo ago

Replying to

ah, yes, now CMake forgets that "file.c" is a C file, and "file2.cxx" is a CXX file. How did I fuck this up this badly, exactly?

0

26

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

Oh. Wow, this Just Worked, huh?

0

2

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 8mo ago

Replying to

The answer is no. perl-5.38.0 is occasionally installing itself to $PREFIX/$PREFIX/ instead of $PREFIX/ and this is only happening after moving it up to before gcc 4.2.4 instead of after (the thing responsible for setting this data is a fucking *shell script* so why would that matter?)

0

32

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3mo ago

Replying to

this is the sixth GCC version i've seen that requires you to rebuild libstdc++-v3 after building it proper, which means you can't do a normal bootstrap and call it good. This has applied even on Linux. What the fuck is wrong with GCC most of the time that makes it this hard to build?

0

10

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 3w ago

Replying to

I do not understand how *nix gets CA certs, or where to put them. Supposedly you just dump .pem certs from Mozilla's stockpile into trust_store_dir (usually /etc/ssl/certs) but doing that leaves gnutls still complaining about nothing being trusted. All documentation online about CA certs is either "install ca-certificates dumbass" or "run update-ca-certificates if you made one locally", so what the fuck do? I'm pulling Debian's ca-certificates package and building the certs, but not only does update-ca-certificates not symlink them from (usually) /usr/share like it's supposed to, it just Does Nothing. Copying the certs from another machine doesn't work, either.

0

2

0

ParzivalWolfram @parzivalwolfram@infosec.exchange

· 4mo ago

Replying to

lol. lmao, even

0

18

0