[Gitoxide October] The first security issue and usable `gix status` (CLI)

github.com

[Gitoxide October] The first security issue and usable `gix status` (CLI)

github.com

snaggen to

Rust · 1 year ago

[October] The first security issue and usable `gix status` (CLI) · Byron/gitoxide · Discussion #1124

github.com

This month was full of smaller updates with some progress on gix status which now works correctly. However, overall it feels like not a lot of substantial work was done while spending a lot of time...

Chat

stsp@azorius.net
link
fedilink
arrow-up
4·
1 year ago
Nice to see progress on this! Having independent git-compatible implementations is good.

By the way, the “ssh --” issue has prior art:

CVE-2017-9800 (Subversion)
CVE-2017-12426 (GitLab)
CVE-2017-1000116 (Mercurial (hg))
CVE-2017-1000117 (Git)

https://subversion.apache.org/security/CVE-2017-9800-advisory.txt

https://www.mail-archive.com/[email protected]/msg1466490.html

https://wiki.mercurial-scm.org/WhatsNew/Archive#Mercurial_4.3_.2F_4.3.1_.282017-08-10.29

[Gitoxide October] The first security issue and usable gix status (CLI)

[Gitoxide October] The first security issue and usable gix status (CLI)

[October] The first security issue and usable `gix status` (CLI) · Byron/gitoxide · Discussion #1124

[Gitoxide October] The first security issue and usable `gix status` (CLI)

[Gitoxide October] The first security issue and usable `gix status` (CLI)