From: atweiden <atweiden@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vim: build with +sodium feature
Date: Tue, 13 Sep 2022 01:26:14 +0200 [thread overview]
Message-ID: <20220912232614.1tUSipB945y1qCZ394VPSmtSn7lNPlpFW6c1_1lPM9c@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39225@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1652 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/pull/39225#issuecomment-1244705605
Comment:
> You're trying to enable this experimental feature on for everyone, not an opt-in for someone.
Perhaps I’ve miscommunicated.
`--enable-libsodium` at compile time doesn’t activate `cryptmethod=xchacha20` at runtime.
Vim’s `cryptmethod` is a user setting. This setting is disabled by default.
All `--enable-libsodium` does at compile time is allow users to, at runtime, *opt in* to using xchacha20+poly1305 to encrypt a file via running `:set cryptmethod=xchacha20`. This is as opposed to users being limited to running e.g. `:set cryptmethod=blowfish2`. Neither of these commands is ever run in the course of normal Vim operation.
> I (personally) don't want to see bug report for vim `x.y.z` can't read some binaries produced by vim `a.b.c`.
In the worst case scenario, users can 1) compile a specific version of Vim before compatibility was broken either through `xbps-src` or manually, 2) decrypt the affected files, 3) re-install Vim via `xbps-install` if necessary, and 4) re-encrypt the affected files with the new version of Vim. This is relatively easy to accomplish, and would only affect users who elected to run `:set cryptmethod=xchacha20`.
That may sound like a lot, but Vim compiles relatively quickly and easily, and the feature comes with a clear warning in its documentation. If Vim’s xchacha20 implementation breaks between versions upstream, it wouldn’t be a valid reason to veer from the existing void-packages strategy of steadily updating the Vim template.
next prev parent reply other threads:[~2022-09-12 23:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 5:31 [PR PATCH] " atweiden
2022-09-12 1:58 ` sgn
2022-09-12 11:36 ` atweiden
2022-09-12 11:36 ` atweiden
2022-09-12 11:37 ` atweiden
2022-09-12 11:37 ` atweiden
2022-09-12 11:37 ` atweiden
2022-09-12 13:16 ` sgn
2022-09-12 23:26 ` atweiden [this message]
2022-09-20 15:24 ` leahneukirchen
2022-12-20 1:58 ` github-actions
2023-01-04 1:59 ` [PR PATCH] [Closed]: " github-actions
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=20220912232614.1tUSipB945y1qCZ394VPSmtSn7lNPlpFW6c1_1lPM9c@z \
--to=atweiden@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).