Tootfinder

Opt-in global Mastodon full text search. Join the index!

@publicvoit@graz.social
2026-01-28 08:12:29

#GNUTaler mit Echtgeld ausprobiert - Teil 4: Fazit
gnulinux.ch/gnu-taler-mit-echt
Spannende Option für wirklich freien digitalen

@michabbb@social.vivaldi.net
2026-01-28 18:49:51

⚠️ Unlike typical exploits, no buffer overflow or memory corruption needed - just one manipulated environment variable grants root access
🛡️ Not all Telnet implementations affected - only #GNU inet utils; proprietary versions like #Cisco and

@seav@en.osm.town
2025-11-20 15:47:51

In 2021 I gave a talk about “openness” briefly tracing the history from the Free Software movement, #GNU, and OSS, to open formats like XML and ODF, then to the #FreeCulture and #OpenData movement like

Open Formats and Standards
Open Geospatial Consortium

Free and Open Source Software
OSGeo

Linked Open Data
OpenStreetMap
@mgorny@social.treehouse.systems
2025-11-11 16:13:00

#GNU findutils help:
> ‘environment is too large for exec’
>
> This message means that you have so many environment variables set (or such large values for them) that there is no room within the system-imposed limits on program command line argument length to invoke any program. This is an unlikely situation and is more likely result of an attempt to test the limits of xargs, or break it. Please try unsetting some environment variables, or exiting the current shell. You can also use ‘xargs --show-limits’ to understand the relevant sizes.
Okay, let's check:
$ xargs --show-limits
xargs: environment is too large for exec
🤦