git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[feature request] git-daemon http connection filtering of client types

From
Pporpen+git@gmail.com <porpen+git@gmail.com>
Date
Jan 31, 2013, 12:46 UTC
Message-ID
<CAANzHtT83JXhQ8XRifdK5ah7NrnD6hvrCjBO4PnPx=qC=DTT9A@mail.gmail.com>
Hey folks,

When I checked for false positives in my spam this morning, I spotted an interesting malformed img link at the top of a spam message.

{snip}
> <http://git.{snip}.n2.nabble.com/file/{snip}/t3.jpg>
>
> Employ a medal tiffany bracelet  <{snip}> a is
{snip}

So, apparently git-daemon's http features are being used by spammers. In most cases, spam filters will correctly identify this junk.

I wonder if there is a better way... In my mental sandbox, git-daemon http could have a set of deny/allow rules for incoming connection client types. e.g.:

git: allow git-http: allow thunderbird: deny outlook express: replace linked file with rickroll.jpg

and so on.. An out-of-the-box install probably should default to allow all to keep backward compatibility.

While I'd love a chance to hack something out, I sadly doubt I'll ever have the time for it. Perhaps there is a student hacker looking for a project.

Cheers! -phil

p.s. appologies to anyone who now has Astley's song stuck in their head. This was not intentional.

Next: Erik Faye-Lund
Message 1 of 3 in “[feature request] git-daemon http connection filtering of client types”
  1. porpen+git@gmail.comJan 31, 2013
  2. Erik Faye-LundJan 31, 2013
  3. porpen+git@gmail.comJan 31, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.