User Tools

Site Tools

tools:finger

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tools:finger [2026/03/31 19:05] – [Finger Relays] Humphrey Boa-Garttools:finger [2026/04/01 07:53] (current) – [More Reading] Humphrey Boa-Gart
Line 5: Line 5:
 Openly sharing email addresses and live session data was considered fine in the early years of the internet. But by the early 90's, hackers & corporate spies were abusing the utility to exfiltrate sensitive internal data from corporate, government & military networks. When the daemon itself was found to be hackable - enabling full remote hijacking - it was the final straw and Finger daemons were gradually abandoned. By the turn of the millennium it had mostly vanished, surviving mostly on older systems until gradually most of them were tracked down and exploited as well. Openly sharing email addresses and live session data was considered fine in the early years of the internet. But by the early 90's, hackers & corporate spies were abusing the utility to exfiltrate sensitive internal data from corporate, government & military networks. When the daemon itself was found to be hackable - enabling full remote hijacking - it was the final straw and Finger daemons were gradually abandoned. By the turn of the millennium it had mostly vanished, surviving mostly on older systems until gradually most of them were tracked down and exploited as well.
  
-Despite this, the beleaguered protocol still has a small yet avid fanbase that overlaps with the remnants of the once-legendary [[tools:gopher|Gopherspace]]. This owes to the fact that, when you strip away the software, Finger as a //protocol// is just a simple plaintext request/response handshake. Normally you ask the server about ''USER'', and the server responds with a plaintext response containing what it knows about ''USER''. However, the protocol specifications do not dictate //where// this data has to come from or how it is phrased. So hobbyists in the 21st century have developed custom finger daemons that just treat ''USER'' like a generic search key, and run it against a dynamic application. Blogs, support portals, social networks, and even weather beacons, are just some examples of what is now being deployed over Port 79.+Despite all this, the beleaguered protocol still has a small yet avid fanbase that overlaps with the remnants of the once-legendary [[tools:gopher|Gopherspace]]. This owes to the fact that, when you strip away the software, Finger as a //protocol// is just a simple plaintext request/response handshake. You just ask the server about ''USER'', and the server responds with a plaintext response containing what it knows about ''USER''. However, the protocol specifications do not dictate //where// this data has to come from or how it is phrased. So hobbyists in the 21st century have developed custom finger daemons that just treat ''USER'' like a generic slug or search key, and run it against a dynamic application. Blogs, support portals, social networks, and even weather beacons, are just some examples of what is now being deployed over Port 79. Finger is even suitable for vibe-coding experiments, as the protocol is so simple that it barely makes a dent in your Agent's context window.
  
  
Line 54: Line 54:
 ==== Finger Relays ==== ==== Finger Relays ====
  
-One lesser-known feature of Finger was its ability to do **relays**, almost like a built-in proxy service. To explain how it worked, lets suppose the client on ''HOST1'' wants to finger user ''alice'' on ''HOST2'' via ''HOST3''. The client's relay request would look like this:+One lesser-known feature of Finger was its ability to do **relays**, almost like a built-in proxy service. To explain how it worked, lets suppose the client wants to finger user ''alice'' on host ''R7'' via a chain of six other hosts. The client's relay request would look like this:
  
   finger alice@R7@R6@R5@R4@R3@R2@R1   finger alice@R7@R6@R5@R4@R3@R2@R1
Line 69: Line 69:
   R7     -> R7 target logic resolves to user query "alice"   R7     -> R7 target logic resolves to user query "alice"
  
-Since it is hop-by-hop forwarding, ''R7'' would only see the IP address of ''R6'', and so forth. This means that Finger clients essentially had a built-in way to obfuscate their IP address from the final host in the chain, years before the existence of VPN's. Like the rest of the protocol, this feature was widely abused, and many Finger daemons kept relay features turned off.+Since it is hop-by-hop forwarding, ''R7'' would only see the IP address of ''R6'', ''R6'' of ''R5'', and so forth. This means that Finger clients essentially had a built-in way to obfuscate their IP address from the final host in the chain, years before the existence of VPN's. Like the rest of the protocol, this feature was widely abused //(skilled data exfiltrators could exploit third party servers to mask their locations in access logs)// and many Finger daemons kept relay features turned off.
  
  
Line 100: Line 100:
 == Web Links == == Web Links ==
  
 +  * [[https://blog.alexellis.io/the-90s-unix-command-fell-out-of-favour/|The 90s UNIX Utility That Fell Out of Favour]] - Alex Ellis Blog
   * [[rfc>742|RFC 742]] - The original Finger specification (1977)   * [[rfc>742|RFC 742]] - The original Finger specification (1977)
   * [[rfc>1288|RFC 1288]] - Last official revision of the Finger specification (1991)   * [[rfc>1288|RFC 1288]] - Last official revision of the Finger specification (1991)
tools/finger.1774983925.txt.gz · Last modified: (external edit)

Find this page online at: https://bestpoint.institute/tools/finger
CC Attribution-Noncommercial-Share Alike 4.0 International The Anonymous Fruit Company The East Internet Trading Company Erischan Novelty Lanterns

Copyright 2026 Best Point Holdings Limited