tallship

https://openssl-library.org/news/secadv/20260127.txt

https://securitylabs.datadoghq.com/articles/openssl-january-2026-security-update-cms-and-pkcs12-buffer-overflows/

You can haz #Cheezburgerz! 🍔 🍟

Enjoy! https://cpm.retrogamecoders.com

#tallship #OS

⛵

The office of the Under Secretary of War for Research and Engineering, in conjunction with the National Spectrum Consortium announced that the first version of the Open Centralized Unit Distributed Unit (OCUDU) radio access network project will be published to GitHub next month, welcoming the participation and contribution of talent from the general public, academia, and industry.

Chief program officer at the National Spectrum Consortium, Mari Silbey, stated that this will provide, "a software stack so that developers don’t have to start from scratch, but they can instead focus on building new things on top of those basic radio functions,” and further, creating an environment where developers can deploy novel wireless technology of their own envisioning.

#FutureG director Tom Rondeau states that what they're hoping to foster, "is a marketplace of competitive ideas,” in an environment where individuals can, "really break that open to this friendly, open development ecosystem".

The Linux Foundation, working closely with the Pentagon, will provide oversight and control of the software repo on GitHub, and as of the beginning of this month announced that 47 organizations have come together as founders of the OCUDU Ecosystem Foundation, including SoftBank, AMD, UC San Diego, AT&T, Ericsson, Redhat, Verizon, Cisco, Nokia, and Nvidia.

Those interested in getting involved now can join or visit the project HERE

#tallship #OCUDU #Open_RAN #War_Department #FOSS #Linux_Foundation

- https://jago.art/en/

#tallship #Jago #art #sculpture

8 years in the making, The US Supreme Court affirms that a provider is merely... a provider, and not complicit in the illegal acts that some of it's subscribers engage in.

You would think that this was a matter of common sense, but where deep pockets are involved... Well, Read on young Grasshoppa*, and while you're at it, *try to snatch the pebble from my hand. That's the lay version in common sense language.

For what it's worth, I say, Boom Shakalaka BOOM 💥 Mic Drop 🎤

For the dry, definitive version of the article you can read the actual unanimous ruling itself HERE

#tallship #SCOTUS #justice #piracy #ISP

⛵

"The Best leader they can possibly have is the one that looks back at them from the mirror."
~David Bowie

Well we're all familiar with MariaDB, Forgejo, and LibreOffice, now one group that is likening the creation of those forks by the original development teams is also asking folks (for the sake of understanding) that #Vinyl-cache is the original, unbroken codebase that was once #Varnish, yet furthermore, is also akin to other software such as those others mentioned above both pre and post forking.

https://vinyl-cache.org/organization/on_vinyl_cache_and_varnish_cache.html#our-opinion

Obviously, this could be confusing. Which should you use? which is the original? which is better?

Honestly, this is a matter of philosophy, business, and other matters of choice; but not so much in substance - yet. These two code bases haven't had much time to diverge, but they are, and have been, for a bit now. Both are FOSS. Both (or at least one) claims to be the continuation of a two decades old code base. Here's what's important now, and how you might want to come to your own conclusions as to which one to choose moving forward.

#Sun_Microsystems manufactured some of the most admired and trusted enterprise server hardware platforms. They also created and maintained #Solaris (SunOS), and they scooped up the custodianship for what was once Star Office in the form of #OpenOffice. They also brought Monty's #MySQL into the fold, while VirtualBox was another free offering.

#Sun was acquired by the #Evil_EllisonCo, aka, #Oracle. Immediately, the company was dismantled. Servers rebranded, while the OpenOffice developer team mutinied under the tutelage of Ellison, and then departed forming "The Document Foundation (TDF) in the process - a fork, #LibreOffice resulted.

Monty Widenius, already soured on the state of MySQL's place at the table with Oracle created the fork, MariaDB (Slackware Linux was the first major Linux distro to include MariaDB as the default during installation of the OS).

MySQL had much use for Oracle but Not OpenOffice (aka OOo), and Ellison refused to give the name to the Document Foundation, so it languished in the Apache Incubator, where he had gifted it, for many years.

Another famous new name that is essentially the original team of creators and developers is #NextCloud, and yes, #ownCloud does still exist... somewhere, or so I'm told ;)

When the three people in charge of steering and the custodianship of Gitea Formed a couple of for profit companies and assigned all trade and service marks of the product to those companies, it caused a great stir within the FOSS community (because this was the de facto leading #FOSS version of a code forge especially appropriate to host FOSS projects). A new Fork, #Forgejo was birthed.

So in a nutshell, When the Varnish project bootstrapped a for profit corporation to operate under (even though at this time it's still FOSS), it likewise spawned a fork of itself, and like the others, the defecting developers created the name #Vinyl, and forked Varnish-cache so that it is Vinyl-cache that continues in the tradition of FOSS while it's expected that Varnish-cache will continue to diverge from the direction of the original code base and philosophy.

#tallship #reverse_proxy #software_forks #open_source

⛵

@jselea Thanks goes out to Jonathan for this (still quite relevant) tidbit. For those of us who spent a lot of time with Sun #Solaris up through Solaris 10 there's a lot to appreciate here.

Solaris has been parted out, but here is an Enterprise production scale incarnation that's worth a looksee and testdrive. It's really a shame that the Evil EllisonCo destroyed so much - just discarded it like trash, following aquisitions, and what they didn't toss out in the trash they dissappointed the developers so much that it spawned forks that exist to fill the vacuum to this day:

- MySQL ==> MariaDB
- OOo ==> LibreOffice (The Document Foundation)
- Sun Enterprise Servers - rebranded as Oracle boxes
- Sun Solaris 10 ==> OpenIndiana and others (OmniOS, for one)
- Sun VirtualBox - Oracle VirtualBox

So without dwelling on the past or further ado, let's follow Jonathan's tour, shall we?

#tallship #FOSS #SunOS #OmniOS #Hypervisor #NAS #ZFS
⛵

RE: https://blogs.linux.pizza/api/posts/1l2sks829g

I'm very happy with the #Linux 7 kernel that I've been rolling with on #Debian 14 the past couple of weeks.

#tallship #FOSS

⛵

.

@internetarchive@mastodon.archive.org

As Mr. Rogers would say... "I knew you could" 👋🤠

There's no downside here folks - This is a very, VERY good thing!

RE: https://mastodon.archive.org/users/internetarchive/statuses/116540969120578575

@auschwitzmuseum@mastodon.world

Finally, a rare documented case of a survivor who risked her own existence to ensure that others may survive.

Hers is the legacy of the human condition, at it's best, emboldened with the courage of what is right and just, when faced with the almost certain demise of oneself.

Accounts such as this are those that inspire others to abandon concerns of terrible retribution for the sake of even a small morsel of humanities rewards.

Thank you for documenting and publishing Stanisława's story.

❤️

RE: https://mastodon.world/users/auschwitzmuseum/statuses/116537900529494605

NOTE: This is a repost from the Fediverse-City Matrix Room.

I meant to post on the progress that @toddsundsted@epiktistes.com has been making on kristec.

You can also checkout this ambitious project itself at:

https://github.com/toddsundsted/ktistec

I've been thoroughly impressed with all of the publishing features of his Fediverse server.

Some of the shortcomings, if that's how you choose to view them, might be that it's essentially a smolweb server leveraging noSQL and an accounts database that trusts all users as literal admins.

But if you're looking to self-host, and your primary interest is in publishing your own material on the #Fediverse, then this may be just the thing you've been looking for.

I cannot atest to the veracity of his claims because I haven't actually installed or tested its capabilities, but it's indeed a laundry list of features I've been hoping to see - leaving that Twitter style cloning of communications in the past, like I've been hoping for.

So for those interested, if you're impressed with the capabilities that #PieFed and #Mitra and #Socialhome bring to the table then here's a fourth initiative that is both visionary and inciteful in it's ambitions.

Your thoughts, observations?

#tallship #FOSS #kristec #Star_Trek #Fediverse #ActivyPub #publishing

Short, i.e., 3m, 4h, Apr 14, 5d, and Dec 16, 2022. Need the full timestamp? No Prob! Just hover w/your mouse. That last post, for example, would display "December 16, 2022 at 3:23 AM PST" (If you're sitting in my seat right now).

Yeah, that's from a real post of mine, which is HERE.

Enjoy!

#tallship #FOSS #Mitra #Fediverse

@ocean@raru.re

They've been doing this for many years. You're right, it hits hard when it's you.

Maybe try it this way instead?:

~$ whois frankandbeanyboitoo.com
No match for domain "FRANKANDBEANYBOITOO.COM".
>>> Last update of whois database: 2026-04-26T23:08:23Z <<<

We correctly, rightfully, and accurately called them all cybersquatters back when, but then that term was legislated to mean something different, and "Domainers" as they still call themselves, came to prominence, seemingly legitimized by the process of semantic labelling - One noun is as good as the next, they're still fricken' cybersquatters as far as I'm concerned, because that's exactly what they're doing - they're squatting on a plot of land in the DNS name space, offering nothing of value themselves.

In the real world there are three types of symbiosis:

- Mutualism: Both the host and the symbiont benefit [the same] from this relationship - although in nature, true mutualism may not actually exist in it's entirety, the relationship between lampreys and sharks are often cited as an example of this kind of symbiotic relationship.
- Commensalism: This is a more realistic plateau whereby it is acknowledged that although neither party are harmed by their relationship, one organism definitely benefits more.
- Parasitism: Domainers, Cybersquatters, and other nouns have been used to identify these blood sucking leeches. The best insecticide is to never consider any offer above that of the standard retail price of registration by that of the registry itself. These insidious parasites wither and perish when they are unable to attach themselves to a host.

Automated scripts that run checking for domain registrations that have freshly fallen out of the redemption period are still a thing. What used to not be a thing was ICANN accredited registrars themselves engaging in this criminal behavior - Yeah, I said criminal. They can sue me.

In my case there were a few domains that slipped away, and for more than twenty years in one case the filthy cybersquatter (legitimized by congressional approval) sat on it, even traded it with another cybersquatter. Eventually, seeing that no one was ever going to pay their exorbitant ransom fees, they (the criminal squatters) themselves eventually let it fall into redemption, and then the black abyss below from which point these strings of characters ultimately will appear in the available name space for registration, but somewhat randomly.

That last bit was supposed to be punishment for the original registrant who let their registration renewal become so delinquent that they could no longer just renew following expiration, but have to spend a tidy (and in some cases, rather arbitrary) sum to "get their domain registration out of redemption".

But why would you pay so much, when you could just wait it out and just pay the standard registration fee at the end of it all? Early on, some folks had to shell out duckets in the neighborhood of $200, to their registration service providers.

The answer, was because someone was waiting in the shadows to snatch up their brand, their domain registration, and could ransom it for even more at that point.

So if you checked for the availability of your desired domain each day to see if it was back in the pool of available domain names (presumably using your registrars facilities to check - so they know you're still interested in claiming it again).

And suddenly it went from the post redemption black hole to coming up in your web based whois search as...

>"You can have this domain for $12,340 or make an offer!"

Man I feel your pain.

In my case, one of the domains came back to me after more than 20 years. The other one was only being ransomed for about three years before the cybersquatters let it go.

Remember, a domain is worth nothing above what the actual registrar charges for the resources under that Top-Level Domain. Period. Your Brand, however, can be worth considerably more, especially with service or trademarks, and therein lies one of the weaknesses of these cybersquatters (although you might pay less to ante up the ransom they demand). I think I've conveyed the idea sufficiently, and notwithstanding WIPO, and ICANN's UDRP, there's always the courts, and reimbursement is not unheard of.

I mention that because in your case it wasn't due to incompetence or negligence that left you without your brand (domain registration), you were spitballing and some nefarious parasite perked up when they said, "Hey I think we got a live one here, let's kidnap it!

And the rest is where things stand as of now.

I do indeed feel your pain, yet the first course of action, if you were planning on using a domain name to expand your brand's recognition, I usually recommend that people search through other Top-Level domains for that SLD and forget about the TLD that the blood sucking leeches snatched up, knowing it had meaning to you. Eventually, they'll have to decide whether it is worth it to continue renewal fees, because you've obviously moved on and have no further interest in the registration - and then, lo and behold, one day you notice that it's in the pool of available domain names again, and one of the registrars is running a special that month: First year $5.

And that's when you can say, Boom Shakalaka BOOM

#Cybersquatters #ransomers #domainers #UDRP #TRADEMARK #USPTO

⛵

RE: https://raru.re/users/ocean/statuses/116461609325897641

Let's get Politcal - Join the Party!

• All is file
• You've got one job
• Make it simple
• Be clear - NOT Clever
• No news is good news
• Plain text is universal
• Write once - Run everywhere
• Connect with others

You can do it right, or you can do it twice

Go here and join the party!

#tallship #FOSS #UNIX #42 #OpenSource

⛵

@karlauerbach@sfba.social @gemelen@mammut.moe

Karl, I've been evangelizing Ente Auth for a little more than two years now. It remains the ONLY fully cross-platform syncing FOSS solution available.

Mobile versions were available more than a year prior, but that didn't satisfy basic cross platform requirements. Back then there was Twilio (Authy), a proprietary solution that announced the sunset of their desktop version soon after the release of Authy desktop, and you could actually migrate your database by exporting it, interestingly enough.

Not surprisingly, they soon pushed and "update" to the desktop version which cripplewared it -presumably in anticipation of Ente Auth mass migrations.

There was a report of a flakey sync between KeepassDX and KeepassSX some time ago, yet I've never experienced issues.

Having said that, you should know that NextCloud itself reports issues with .kdbx syncing if you are stupid enough to install from the Google playstore, other sources like the git repo or F-Droid are not intentionally crippled in this way, by design, and virtue of their contract with Google.

I usually don't mention using password managers together with #MFA authenticators out of an abundance of concern for being flamed by fellow security professionals, but felt it prudent to mention here; the fact is that people will do so anyway because it's convenient.

I do separate, as a best practice, the use of my passwords and my only authenticator, Ente Auth, yet keep backup copies of my #TOTP MFA keys in a .kdbx file (in the comments - not active). I believe that's advisable to keep them in a separate vault and avoids the issue of not being able to migrate (i.e., Twillio's Authy lockdown cripple).

Sure, one could break and reinitialize their MFA on each of their myriad accounts but that's indeed a Major Pain (that's a TV pun).

So for me, I'm a staunch supporter of Pass/OpenKeyChain (sync via Git) & #Ente_Auth on all of my platforms: Android, FreeBSD, Linux (I no longer use Windows) - Sync via my self-hosted Ente Auth server; and a .kdbx client appropriate for my OS, syncing that via #NextCloud. You can use #Peergoss if you prefer.

For everyone else, I usually recommend they go with a combination of Ente Auth and [VaultWarden}(https://vaultwarden.com)

That keeps everything absolutely self-hosted and 💯% #FOSS.

If you're not a stickler for self-hosting those very same solutions are still available to you, except that for #VaultWarden you need to go [HERE](https ://VaultWarden.org).

I don't do Apple, but I am aware of .kdbx clients for that particular manufacturers products and the iPhone was, I believe, the first platform that Ente Auth was released for.

Beyond that I just urge everyone to stick with 100% FOSS solutions whenever feasible (i.e., Use VaultWarden instead of BitWarden) and make sure to contribute whatever they feel is fair to the developer teams that make all of this possible.

I hope that helps!

#tallship #Privacy #fdroid #kdbx #opensource #selfhosting

⛵