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

Re: [PATCH] Support username and password inside URL

From
KHKrzysztof Halasa <khc@pm.waw.pl>
Date
Nov 20, 2005, 20:46 UTC
Message-ID
<m3br0fujwc.fsf@defiant.localdomain>
In-Reply-To
<7vwtj3xe72.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> writes:
Show 9 quoted lines
> It is handy to have weak "authentication" in some situations.  I
> am not ashamed to admit that I've used security-by-obscurity
> myself, when I sent an email to a friend, saying:
>
>         Hi, I have some pictures I took during our last trip
>         together, but due to their size I am not attaching them
>         to this e-mail.  Please pick them up at:
>
> 	        http://members.cox.net/junkio/r0ZIEF/5S54m/

If the above is security by obscurity then any password scheme is, too. After all you're obscuring the password, right? Well, private key and its password can be obscure as well. :-)

A common definition says that security by obscurity is using a hidden algorithm and not a shared or private secret.

-- 
Krzysztof Halasa
Previous: Junio C HamanoNext: Kalle Valo
Message 4 of 8 in “HTTP basic authentication support”
  1. Kalle ValoNov 20, 2005
  2. Support username and password inside URLKalle Valo, Nov 20, 2005
  3. Junio C HamanoNov 20, 2005
  4. Krzysztof HalasaNov 20, 2005
  5. Kalle ValoNov 23, 2005
  6. Junio C HamanoNov 24, 2005
  7. Johannes SchindelinNov 24, 2005
  8. Junio C HamanoNov 24, 2005

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.