Noticed some nasty spam in my inbox this morning, had some trouble getting in to codeberg's site initially, now see the above message.
Readit Newsdsm9000 commented on Codeberg Down blog.codeberg.org/we-stay... · Posted by u/dsm9000
From the report:
> Finally, if sshd cannot be updated or recompiled, this signal handler race condition can be fixed by simply setting LoginGraceTime to 0 in the configuration file. This makes sshd vulnerable to a denial of service (the exhaustion of all MaxStartups connections), but it makes it safe from the remote code execution presented in this advisory.
Setting 'LoginGraceTime 0' in sshd_config file seems to mitigate the issue.
would cold-restarting sshd every hour also make this unlikely / harder to exploit?
dsm9000 commented on Why does an extraneous build step make my Zig app 10x faster? mtlynch.io/zig-extraneous... · Posted by u/ojosilva
This post is another example of why I like zig so much. It seems to get people talking about performance in a way which helps them learn how things work below today’s heavily abstracted veneer
For those who haven't seen it: https://www.youtube.com/watch?v=XTaNi6uL41s
BIOSes of the time were all written in highly-optimised Asm, and I suspect those little "easter eggs" they added were because the programmers knew they had enough space left over to put some more fun stuff in.
There was also AMI WinBIOS that provided a GUI, but I remember it being much less featureful than other BIOSes of the time with a TUI and didn't like mobos that used it, so in that case they may have sacrificed functionality for appearance.
I miss Openboot firmware that was on SunOS servers and workstations. It was IIRC mostly written in FORTH and we could write forth snippets at the serial console to make mods / query the pre boot environment. I also found the SGI boot firmware similarly functional. Both allowed changing boot settings and allowed to boot from network without any trouble at all. Graphical BIOS that came with the x86 systems was such a downgrade for us especially since you could not interact over serial/remotely with a simple terminal connection. IMHO
With respect to end of sentence spaces. I'm an "old" and learned on typewriters and type two spaces is etched into my muscle memory and my brain. It wasn't until 2016 that while working collaboratively on a large google doc (which was occasionally brought into Word by others) that I was made aware that two spaces were no longer the norm.
It was like an editing PVP game where these would be fixed in near real-time by others in the document we were working on :-)
Yes the web text today removes these today but I still prefer reading text in the old RFC document style where it's not only fixed width fonts, but also right and left column justified. In emacs this can be done by selecting a region and doing a C-u ESC q
:-)
I liked programming the m68k cpus. They were also the CPU used in my computer science department curricula for assembly language programming classes.
At school we had lots of Sun{2,3,4}, Apollo, HP, Mac, and NeXT computers which we could practice on. Kinda saw the writing on the wall when we got a 6 CPU i386 sequent symmetry system and then SPARC, MIPS RISC, and PowerPC while nothing really from Motorola. I never enjoyed programming x86 cpus after being self taught on 6502 and then m68k systems :-)
I still have an ATARI Mega ST and a Sun 2 at home for sentimental reasons only.
I just, can't imagine what benefit you get from opening an X gigabyte file.
Maybe I don't fully understand the context, but... why shouldn't you open a big file?
I haven't read the whole article, but I did read that the author complains that a 172 kb text file makes the editor slow. It seems that the syntax highlighting is the culprit.
I have a similar problem with my current editor of choice. I used to have a "raw" visualizer for all kind of files. Sometimes the file format is just unknown and it's useful to take a look at its contents (does it start with PK?) or you want to make a quick overwriting edit (to change some binary flags) or edit text in a huge machine-generated text file without any formatting beyond line feeds.
If I understood the author correctly, he's saying that structured editors are superior to a syntax highlighting system that's based on regexps, when you use them for programming. I agree wholeheartedly. It's a clear-cut case of the "don't repeat yourself" principle.
I’ve used emacs to open and edit binaries back in the old days - basically one long line. We often needed to install proprietary software in non standard locations so changing the embedded strings within binaries worked great and better than using vi (pre vim era). Always best if the new path had a length less than that of the existing one.
In any event I guess the whining about editors will never stop but meanwhile they seem to be GoodEnough(tm) for me and most things.
Emacs used to be mocked for being bigger than the OS but now I think most editors are much larger. I used to work at a University lab helpdesk of sorts where first time users of UNIX systems would ask us for help getting started entering their first CSCI programs on a Sun or other UNIX-like os and my unscientific but high n observation is that vi, emacs, ed or cat all worked and occasionally people would find a way to get confused equally on any method when starting out. Level of education didn’t seem to make a difference.
Editor ergonomics seem to be very personal, like furniture so I’m glad we have so many options.
On another side note I am glad that most text input fields across many operating systems and applications usually do the right thing with Emacs cursor control sequences e.g. CTRL-a, CTRL-n, CTRL-p, CTRL-e. So hopefully that legacy lives on
dsm9000 commented on A Fire Upon the Deep by Vernor Vinge (1992) archive.org/details/fireu... · Posted by u/cybernautique
For those that aren't familiar, a short teaser:
Future archaeologists have traveled to a remote asteroid to investigate an alien artifact found within it, a computing device of some kind. They bring it to life and begin extracting its data and programs for their research.
A debate breaks out about the substantial virus risk known to be associated with these "found" computing devices. They decide to cut and run, but not before the artifact has regained its ancient sentient awareness, unbeknownst to the crew.
They wipe and rebuild their onboard computers as quickly and thoroughly as they can.
But as they are rocketing away, the artifact scans their ship and finds a neglected peripheral on its surface.
A software vulnerability is found! It makes its move.
This scene in the book is maybe one of the earliest examples of fuzzing being used n fiction :-) ?
dsm9000 commented on The Raspberry Pi can boot off NVMe SSDs now jeffgeerling.com/blog/202... · Posted by u/geerlingguy
I use my cluster of rpis to run light compute jobs so I prefer to run everything in RAM using alpine Linux. I don’t need to have sdcard or nvme adding extra cost. NFS for persistence and cheap independent wall warts plugged into a couple power strips. However I guess if you need the IOPS maybe the nvme is called for and worth the extra cost.