linux-kernel - Re: Smaller compressed kernel source tarballs?

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>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.63.0609211517380.17238@qynat.qvtvafvgr.pbz>
Date:	Thu, 21 Sep 2006 15:20:24 -0700 (PDT)
From:	David Lang <dlang@...italinsight.com>
To:	Sean <seanlkml@...patico.ca>
cc:	Dax Kelson <dax@...ulabs.com>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Linux kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: Smaller compressed kernel source tarballs?

On Thu, 21 Sep 2006, Sean wrote:

>> also people could be behind a firewall that prevents git from working properly,
>> for them tarballs and patches are the right way of doing things.
>
> I use git from behind a firewall everyday without a problem.  If you've seen
> such a problem yourself, a bug report would hopefully lead to a solution.

it's not a bug, it's simply the fact that git (properly) uses it's own port for 
it's own protocol, and not all firewalls allow access to that port. in some 
cases even where a person would have the ability to get the firewall changed 
they may not want to for other (political) reasons.

even if git tunneled over HTTP there would be firewalls that would require 
authentication that git wouldn't be able to do and would therefor block the 
access.

David Lang
-
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/