From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Mauger <mmauger@protonmail.com>,
larsi@gnus.org, 8427@debbugs.gnu.org, stefan@marxist.se,
ahyatt@gmail.com
Subject: bug#8427: [SECURITY] sql.el -- comint process passwords are leaked to ps(1) listing
Date: Tue, 19 Oct 2021 14:05:57 +0200 [thread overview]
Message-ID: <874k9djk2i.fsf@gmx.de> (raw)
In-Reply-To: <83pms1cjl8.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 19 Oct 2021 14:58:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> I've pushed to master for now. I'll test this week and decide then whether I push to emacs-28.
>
> If you decide to backport to emacs-28, please cherry-pick from master,
> instead of making a separate independent commit, because cherry-picks
> are automatically skipped when emacs-28 branch is merged to master
> (which happens almost daily these days).
Except the etc/NEWS change. This file differs heavily between emacs-28
and master branches. Furthermore, I have fixed some oddities in that
file wrt this change.
> Thanks.
Best regards, Michael.
next prev parent reply other threads:[~2021-10-19 12:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 11:27 bug#8427: [SECURITY] sql.el -- comint process passwords are leaked to ps(1) listing Jari Aalto
2012-02-28 23:35 ` bug#8427: (no subject) Michael Mauger
2014-03-06 2:06 ` bug#8427: [SECURITY] sql.el -- comint process passwords are leaked to ps(1) listing Glenn Morris
2014-03-07 23:02 ` Stefan Monnier
2018-01-07 17:54 ` Andrew Hyatt
2019-10-06 3:28 ` Stefan Kangas
2019-10-13 1:51 ` Andrew Hyatt
2019-10-13 22:09 ` Stefan Kangas
[not found] ` <meny2xh8p4o.fsf@ahyatt-macbookpro6.roam.corp.google.com>
2019-10-20 15:57 ` bug#8427: Fwd: " Stefan Kangas
2019-10-20 16:02 ` Stefan Kangas
2019-10-21 0:56 ` Andrew Hyatt
2019-10-21 20:33 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-02 1:10 ` Andrew Hyatt
2019-11-02 19:41 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-11-11 5:31 ` Andrew Hyatt
2019-12-16 4:59 ` Andrew Hyatt
2019-12-16 15:12 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-12-18 6:15 ` Andrew Hyatt
2019-12-18 12:45 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-12-18 16:57 ` Eli Zaretskii
2019-12-18 17:52 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-12-30 15:11 ` Andrew Hyatt
2019-12-30 18:34 ` Michael Albinus
2019-12-30 19:26 ` Andrew Hyatt
2019-12-30 19:39 ` Eli Zaretskii
2019-12-30 23:36 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-21 12:45 ` Lars Ingebrigtsen
2021-10-12 5:05 ` Stefan Kangas
2021-10-13 16:05 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-13 17:47 ` Stefan Kangas
2021-10-13 18:26 ` Eli Zaretskii
2021-10-13 21:26 ` Stefan Kangas
2021-10-19 4:37 ` Michael Mauger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-19 11:58 ` Eli Zaretskii
2021-10-19 12:05 ` Michael Albinus [this message]
2021-11-05 7:11 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k9djk2i.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=8427@debbugs.gnu.org \
--cc=ahyatt@gmail.com \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=mmauger@protonmail.com \
--cc=stefan@marxist.se \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).