[HN Gopher] Practical /dev/TCP in the HTTPS Era
___________________________________________________________________
Practical /dev/TCP in the HTTPS Era
Author : azathothas
Score : 6 points
Date : 2025-06-02 13:40 UTC (9 hours ago)
(HTM) web link (blog.pkgforge.dev)
(TXT) w3m dump (blog.pkgforge.dev)
| azathothas wrote:
| Since /dev/tcp doesn't work with https, complex redirect chains
| or even dns sometimes, almost all mentions of it in the hacking
| articles online are not that useful
|
| We had to make soar's install script be able to work anywhere, In
| the article you get to know about http://http.pkgforge.dev & how
| you can use it to make /dev/tcp finally practical & useful in the
| modern https age
| codedokode wrote:
| They are solving the problem that should not have existed. Simply
| include the binaries into the installer.
|
| Also I wouldn't run suspicious third-party binary installer
| anyway. If it is not in the official repositories, it doesn't get
| installed, because I have no time to figure out if it is a safe
| software or not, what it will do to my system, does it include
| telemetry, and I have no time to build a sandbox.
| ptsneves wrote:
| I think /dev/tcp is bash specific. The actual socket is at
| /proc/net/{tcp,udp}
| yonatan8070 wrote:
| I don't fully understand how this works
|
| Does bash "overlay" /dev/tcp over the filesystem? If the kernel
| created an actual /dev/tcp file, would bash be unable to access
| it or...?
| cmeacham98 wrote:
| > Checksums can be verified after download
|
| They can be but _are_ they? Does their installer actually verify
| the checksum?
|
| Because if it's designed for systems so minimal/broken they can't
| do normal HTTPS, I kinda doubt it...
___________________________________________________________________
(page generated 2025-06-02 23:02 UTC)