From: Fabian Ebner <f.ebner@proxmox.com>
To: Aaron Lauterer <a.lauterer@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v2 storage] CephConfig: ensure newline in $secret and $cephfs_secret parameter
Date: Tue, 25 Jan 2022 10:54:15 +0100 [thread overview]
Message-ID: <e95ed6d5-8e07-0a94-c5e5-ec4e5126f604@proxmox.com> (raw)
In-Reply-To: <20220124151153.1390196-1-a.lauterer@proxmox.com>
Am 24.01.22 um 16:11 schrieb Aaron Lauterer:
> Ensure that the user provided $secret ends in a newline. Otherwise we
> will have Input/output errors from rados_connect.
>
> For consistency and possible future proofing, also add a newline to
> CephFS secrets.
>
> Signed-off-by: Aaron Lauterer <a.lauterer@proxmox.com>
> ---
>
> changes:
> - instead conditional with regex, use chomp and always adding the newline
> - do the same to $cephfs_secret
>
> From previous version (though not sure if they still apply with these
> changes):
>
Reviewed-by: Fabian Ebner <f.ebner@proxmox.com>
Tested-by: Fabian Ebner <f.ebner@proxmox.com>
since I gave the new version a go.
>
> PVE/CephConfig.pm | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/PVE/CephConfig.pm b/PVE/CephConfig.pm
> index 5c94a04..c388f02 100644
> --- a/PVE/CephConfig.pm
> +++ b/PVE/CephConfig.pm
> @@ -227,14 +227,16 @@ sub ceph_create_keyfile {
> eval {
> if (defined($secret)) {
> mkdir '/etc/pve/priv/ceph';
> - PVE::Tools::file_set_contents($ceph_storage_keyring, $secret, 0400);
> + chomp $secret;
> + PVE::Tools::file_set_contents($ceph_storage_keyring, "${secret}\n", 0400);
> } elsif ($type eq 'rbd') {
> mkdir '/etc/pve/priv/ceph';
> PVE::Tools::file_copy($ceph_admin_keyring, $ceph_storage_keyring);
> } elsif ($type eq 'cephfs') {
> my $cephfs_secret = $ceph_get_key->($ceph_admin_keyring, 'admin');
> mkdir '/etc/pve/priv/ceph';
> - PVE::Tools::file_set_contents($ceph_storage_keyring, $cephfs_secret, 0400);
> + chomp $cephfs_secret;
> + PVE::Tools::file_set_contents($ceph_storage_keyring, "${cephfs_secret}\n", 0400);
> }
> };
> if (my $err = $@) {
next prev parent reply other threads:[~2022-01-25 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 15:11 Aaron Lauterer
2022-01-25 9:54 ` Fabian Ebner [this message]
2022-01-25 9:58 ` [pve-devel] applied: " Thomas Lamprecht
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=e95ed6d5-8e07-0a94-c5e5-ec4e5126f604@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=a.lauterer@proxmox.com \
--cc=pve-devel@lists.proxmox.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