src
buttersink
Our great sponsors
src | buttersink | |
---|---|---|
745 | 5 | |
3,041 | 190 | |
1.6% | - | |
10.0 | 0.0 | |
2 days ago | over 5 years ago | |
C | Python | |
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
src
-
OpenBSD Upgrade 7.3 to 7.4
The OpenBSD project released 7.4 of their OS on 16 Oct 2023 as their 55th release đź’«
-
OpenBSD System-Call Pinning
Well since https://www.openbsd.org/ still says
> Only two remote holes in the default install, in a heck of a long time!
I'm assuming not, but I could always be mistaken.
- Project Bluefin: an immutable, developer-focused, Cloud-native Linux
-
From Nand to Tetris: Building a Modern Computer from First Principles
> building a cat from scratch
> That would be an interesting project.
Here is the source code of the OpenBSD implementation of cat:
> https://github.com/openbsd/src/blob/master/bin/cat/cat.c
and here of the GNU coreutils implementation:
> https://github.com/coreutils/coreutils/blob/master/src/cat.c
Thus: I don't think building a cat from scratch or creating a tutorial about that topic is particularly hard (even though the HN audience would likely be interested in it). :-)
-
OpenBSD – pinning all system calls
> I don't know how they define `MAX`, but I'm guessing it's a typical "a>b?a:b"
Indeed: https://github.com/openbsd/src/blob/master/sys/sys/param.h#L...
> Then `SYS_kbind` seems to be a signed int.
It's an untyped #define: https://github.com/openbsd/src/blob/master/sys/sys/syscall.h...
I believe your whole analysis is correct, that running an elf file with an openbsd.syscalls entry with .sysno > INT_MAX will allow an out-of-bounds write.
- Une nouvelle mise à jour de Systemd permettra à Linux de bénéficier de l'infâme "écran bleu de la mort" de Windows, mais la fonctionnalité a reçu un accueil très mitigé
-
tmux causing ANSI color-response garbage on attaching?
I can reproduce it. And this is the commit that causes the issue: https://github.com/openbsd/src/commit/d21788ce70be80e9c4ed0c52c149e01147c4a823
-
Sudo-rs' first security audit
This doesn’t really change your conclusion, but I think that’s the wrong file. This is the real doas afaict: https://github.com/openbsd/src/blob/master/usr.bin/doas/doas...
Still just a tidy 1072 lines in that folder though.
I spent 5 minutes staring at your file trying to understand how on earth it does the things in the man page, but of course it doesn’t.
-
OpenBSD: Removing syscall(2) from libc and kernel
OpenBSD developers are making serious effort to kill off indirect syscalls, the base system is completely clean, take a look at the work Andrew Fresh did to adapt Perl. He write a complete syscall "dispatcher" or emulator for the Perl syscall function so that it calls the libc stubs.
https://github.com/openbsd/src/commit/312e26c80be876012ae979...
The ports tree is also being cleansed of syscall(2) usage, until they're all gone.
msyscall, pinsyscall, recent mandatory IBT/BTI, xonly. OpenBSD is making waves, but people aren't really seeing them yet.
-
"<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
Actually, I got it wrong, too many vulnerabilities in flight. They did fix it: https://github.com/openbsd/src/commit/375ccafb2eb77de6cf240e...
buttersink
-
Docker or native?
for data I rely on my filesystem. Both ZFS and BRTFS support atomic snapshots which need no additional storage space (i.e. copy-on-write), and you can sync those to wherever you need using rsync or whatever. As long as you sync the snapshot you are guaranteed to have a consistent state. You can however also efficiently sync the snapshots themselves to other volumes of the same type. There is e.g. buttersink (https://github.com/AmesCornish/buttersink) which allows you to incrementally sync snapshots over the network, as long as both source and target are a btrfs volume. For restore copy the most recent snapshot back to the new drive and off you go.
- Incremental backup of snapper to external drive
- What's a good way to backup a system running btrfs and snapper?
-
Going beyond raspberrypi3
For backup I use Buttersink (https://github.com/AmesCornish/buttersink seems abandoned, but still works well on Python2) to sync my snapshots to a separate disk every once in a while.
-
Ex-distro hoppers, which did you stick with and why?
I've thought about saving snapshots to S3, but I like the idea of being able to randomly access any single file from S3, so some sort of sync (e.g. s3cmd sync) is more attractive.
What are some alternatives?
cosmopolitan - build-once run-anywhere c library
snap-sync - Use snapper snapshots to backup to external drive
bastille - Bastille is an open-source system for automating deployment and management of containerized applications on FreeBSD.
snapsync - A synchronization tool for btrfs-backed snapper snapshot directories
PHPT - The PHP Interpreter
btrbk - Tool for creating snapshots and remote backups of btrfs subvolumes
Joomla! - Home of the Joomla! Content Management System
nextcloud-sync - Persona use. Adapt how you see it fit.
ctl - The C Template Library
frr - The FRRouting Protocol Suite
coreutils - upstream mirror
PostgreSQL - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch