Denis Ovsienko <[email protected]> wrote:
> git.tcpdump.org has been available for git cloning as both https:// and
> git:// for a while. I consider introducing Debian 13 to provide this
> service, but this version of this Linux distribution made it more
> difficult to serve git:// because "The git-daemon-run and
> git-daemon-sysvinit packages have been removed from trixie due to
> security reasons." [1] I do not know which security reasons these are
> besides the obvious lack of encryption (which is moot for a public
> repository) and server authentication of origin (which is not).
yeah, it's pretty unclear what's up.
Is it *git-daemon* that's the problem, or the scripts that start it?
> Before I look deeper into this, does anybody see a sound use case that
> it would be impossible or difficult to switch from git:// to https:// ?
I don't think it ought to be a problem.
At some point, Python/pip insisted on going from http->https, but the package to
enable https was only available via https, and this was a serious annoyance.
That's more of a *production* side thing, and I think that this does not
apply to building libpcap/tcpdump. Places with significant outgoing port
restrictions likely are happier with https: anyway.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | IoT architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
_______________________________________________
tcpdump-workers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
