linux-kernel - Re: [ANNOUNCE] GIT 1.5.0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0702140839560.3604@woody.linux-foundation.org>
Date:	Wed, 14 Feb 2007 08:45:44 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bill Lear <rael@...yra.com>
cc:	Junio C Hamano <junkio@....net>, git@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] GIT 1.5.0

On Wed, 14 Feb 2007, Bill Lear wrote:
> 
> This is enabled by passing the --enable=receive-pack to the
> git-daemon (usually in the [x]?inetd configuration).
> 
> This has the benefit of:

Before you list the benefits, you should always talk about the lack of 
security! Let nobody enable it without realizing the dangers! Tell people 
to _only_ do this inside a company firewall, and even then, only if you 
trust everybody.

>   2) A less ugly URL to use: git://server/repo, instead of, say,
>      ssh+git://server/path/to/repos/repo.

Why do people use that silly "ssh+git://" format?

It's a cogito thing. Native git has never done it, and only supports it 
because cogito thought it must make sense.

The native git ssh URL is exactly the normal ssh URL:

	server:/path/to/repos/repo

and if you really want to use the "xxx://" format, you might as well just 
use

	ssh://server/path/to/repos/repo

which should also work fine. 

		Linus

PS. This is the commit message that  added "git+ssh://":

	Author: Linus Torvalds <torvalds@...l.org>
	Date:   Fri Oct 14 17:14:56 2005 -0700

	    Support git+ssh:// and ssh+git:// URL

	    It seemed to be such a stupid syntax. It's both what "ssh://" means,
	    and it's what not specifying a protocol at _all_ means.

	    But hey, since we already have two ways of saying "use ssh with
	    pack-files", here's two more.

so it was deemed stupid from the get-go, and isn't even some "legacy" 
thing. It's purely a "cogito people thought it makes sense to point out 
that it's _both_ native git _and_ ssh protocol".
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/