From: Arseny Maslennikov <arseny@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Changelog c CVE
Date: Tue, 7 Jul 2026 12:19:34 +0300
Message-ID: <akzElfuJj91lskZv@cello> (raw)
In-Reply-To: <c945bcbd-6f78-435f-83de-fc2e9825a75d@altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
On Tue, Jul 07, 2026 at 11:40:27AM +0300, Anton Midyukov wrote:
> Доброго времени суток
>
> Возник вопрос. В Changelog с CVE строки разбиваем при превышении 80 символов или нет?
Я бы расширил до 96 всё-таки; пусть, мол, будет ограничение, но не такое
тесное; влезает в терминальное окно 960 точек шириной. Но о вкусах и вайбах
спорить смысла мало.
> Есть какие-то проблемы, если делать переносы?
Главное, чтобы переносимый текст сохранял свои отступы. Например (чуть ниже):
> Пример оформления, которое мне не понравилось:
- Fixes:
+ CVE-2026-55770: prevent LDAP injection via bind DN to group resolution
(auth/ldap, secrets/ldap)
+ CVE-2026-55776: fix server crash from unlock of unlocked mutex for RSA keys
created with derived=true (secrets/transit)
+ CVE-2026-55774: fix unauthorized cross-namespace lease revocation
via leaked lease identifiers (core/leases)
+ CVE-2026-55775: fix namespace path canonicalization of "root"
enabling unauthorized operations on the parent namespace (core/namespaces)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-07 9:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 8:40 Anton Midyukov
2026-07-07 9:19 ` Arseny Maslennikov [this message]
2026-07-07 13:23 ` Sergey V Turchin
2026-07-07 13:32 ` Anton Midyukov
2026-07-07 14:34 ` Sergey V Turchin
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=akzElfuJj91lskZv@cello \
--to=arseny@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git