From: Krzysztof Halasa <khc@pm.waw.pl>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Support username and password inside URL
Date: Sun, 20 Nov 2005 21:46:59 +0100 [thread overview]
Message-ID: <m3br0fujwc.fsf@defiant.localdomain> (raw)
In-Reply-To: <7vwtj3xe72.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 20 Nov 2005 12:21:53 -0800")
Junio C Hamano <junkio@cox.net> writes:
> 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
next prev parent reply other threads:[~2005-11-20 20:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 8:38 HTTP basic authentication support Kalle Valo
2005-11-20 10:05 ` [PATCH] Support username and password inside URL Kalle Valo
2005-11-20 20:21 ` Junio C Hamano
2005-11-20 20:46 ` Krzysztof Halasa [this message]
2005-11-23 20:56 ` Kalle Valo
2005-11-24 22:14 ` Junio C Hamano
2005-11-24 22:24 ` Johannes Schindelin
2005-11-24 23:01 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3br0fujwc.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).