From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: Using ZChunk for setup…
Date: Sat, 22 Jan 2022 21:45:07 +0100 [thread overview]
Message-ID: <87tudvts8c.fsf@Rainer.invalid> (raw)
In-Reply-To: <6ee3cda2-33b8-ccdc-ef24-f75a1d8ee046@dronecode.org.uk> (Jon Turney's message of "Sat, 22 Jan 2022 20:23:21 +0000")
Jon Turney writes:
> How would the signature be checked? Is it for the reconstructed full
> zchunk file?
The signature should be for the full (reconstructed) file I think, the
individual chunks of the changeset are locked in by SHA256 checksums
anyway.
> One slightly related issue which it would be good to address if
> possible when adding this is that rsync is only file-atomic, not
> repo-atomic, so we may get a compressed ini file and signature which
> don't match as they are different moments in time during an update. I
> think currently no-one notices this if it happens, as setup silently
> falls back to an older compression type, but it would be nice to stop
> generating those eventually.
One of the things I am still thinking about is switching from the ini
format to YAML. In this case the signature could/should be part of the
data structure (JOSE/COSE style), so you'd only ever have to look at a
single file and it wouldn't matter how you got it together.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2022-01-22 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 11:05 Achim Gratz
2022-01-22 20:23 ` Jon Turney
2022-01-22 20:45 ` Achim Gratz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tudvts8c.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).