Date: Fri, 4 Oct 2019 14:11:03 -0300 From: =?utf-8?Q?Lucas_Nali_de_Magalh=C3=A3es?= <rollingbits@gmail.com> To: grarpamp <grarpamp@gmail.com> Cc: freebsd-security@freebsd.org, freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Git/Mtn for FreeBSD, PGP WoT Sigs, Merkel Hash Tree Based Message-ID: <252308D7-D927-4770-92B4-9CD4E6EF13DB@gmail.com> In-Reply-To: <CAD2Ti2_5HndZ1_tnSEBiuTJpvb0fU8X8vobqXD_eVpHiagfTvg@mail.gmail.com> References: <CAD2Ti2_5HndZ1_tnSEBiuTJpvb0fU8X8vobqXD_eVpHiagfTvg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> On Sep 20, 2019, at 6:04 PM, grarpamp <grarpamp@gmail.com> wrote: > > [broken links fixed] > > For consideration... > > SVN really may not offer much in the way of native > internal self authenticating repo to cryptographic levels > of security against bitrot, transit corruption and repo ops, > external physical editing, have much signing options, etc. > Similar to blockchain and ZFS hash merkle-ization, > signing the repo init and later points tags commits, > along with full verification toolset, is useful function. [...] > Note also CVS, which some BSD's still use (ahem: Open, Net), > is even worse than SVN with zero protection > at all in any component regarding this subject. > > It really time to migrate repo tech to year 2020. Are you sure you are talking about plain text files?May I suggest get rid of the binary only part instead? I imagine how painful it is to do a 'git checkout' of many GiB of data. TeXLive is worth a few and is an eternity here. Lc -- rollingbits — 📧 rollingbits@gmail.com 📧 rollingbits@terra.com.br 📧 rollingbits@yahoo.com 📧 rollingbits@globo.com 📧 rollingbits@icloud.comhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?252308D7-D927-4770-92B4-9CD4E6EF13DB>