HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
aunali1
super-strip
C2022–2026
aunali1 / super-strip

super-strip

sstrip is a small utility that removes as much as possible from an ELF file without affecting the file's memory image.

2Distinct people
3Mentions
0Explicit recommenders
81GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

sstrip is a small utility that removes as much as possible from an ELF file without affecting the file's memory image.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2022-08-19 23:24:09 UTC to 2026-06-10 05:54:01 UTC.

012022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

3 sources
> Whereas, with ELF – if you want to add a new feature, do you add it as a new program table entry type (PT_), or a new note type (NT_), or a separate note section (SHT_NOTE)? It won't be a note section since ELF binaries don't need to have any sections. You can remove all section headers from an existing ELF binary and it'll still work (sstrip [https://github.com/aunali1/super-strip - not sure the one in ELFkickers is the same thing] does this). Program headers define how & where to load things, notes are for small metadata. Is your point that section headers do generally exist in ELF files, even though they're not necessary? I do agree that this "double indexing" between PHs and SHs is pretty weird and a bit odd.
In Adopting the Parallel DWARF linker in dsymutil
The approach taken there is unfortunately not correct. The existence of sections (and section headers) is completely optional for ELF files; you can have valid executables and libraries without them. `sstrip` [https://github.com/aunali1/super-strip] can be used to generate such files. The correct approach is to process the program headers and find the tail end of anything referenced in PT_LOAD as well as from DT_DYN items. You can combine that with a section based approach; if the file has debug information it won't be covered by program headers and you'd end up cutting it off if going purely by program headers. However, this is technically optional while the program header based approach is really required.
In Carving ELF Files
I think large chunk of it is from dynamic linker, rather than glibc. At least that appear to be the case according to "file a.out". Adding "-static" option seems to prevent that: $ gcc -Wall -s -nostdlib tiny.o; wc -c a.out 12780 a.out $ gcc -Wall -s -nostdlib tiny.o -static $ wc -c a.out 4304 a.out Bulk of what remains is page-size alignment. Linux works with 4KB pages: $ getconf PAGESIZE 4096 ...so it makes sense that gcc (ld, really) aligns to that. But we can dial it down: $ gcc -Wall -s -nostdlib tiny.o -static \ -Wl,-zmax-page-size=64; wc -c a.out 400 a.out ...and a bit more could be shaven by dropping Build ID: $ strip -R .note.gnu.build-id a.out; wc -c a.out 344 a.out This wonderful piece of software: https://github.com/aunali1/super-strip seem to find more things to remove, although not sure what w
Read the rest
ould be that: $ sstrip a.out; wc -c a.out 220 a.out Of course, this is not quite "golfed", and I too, would love to see OP's article updated to x86_64 and current crop of gcc/binutils.
In A Whirlwind Tutorial on Creating Teensy ELF Executables for Linux

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.