From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs in a Corporate Environment
Date: Sat, 15 Apr 2023 19:16:09 +0800 [thread overview]
Message-ID: <87edoliefa.fsf@yahoo.com> (raw)
In-Reply-To: <83wn2dcwj7.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Apr 2023 12:41:32 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sat, 15 Apr 2023 10:21:08 +0200
>> Cc: help-gnu-emacs@gnu.org
>> From: <tomas@tuxteam.de>
>>
>> > Seriously: you should talk to your CISO, if you have one. You _think_
>> > you control everything on your "civilised" OS, but that's an illusion.
>> > Unless you build your machines yourself, from the ground up, and also
>> > code all the software that runs on it.
>>
>> You just moved the goalposts. We had it about paging files (which in
>> my case would be a partition, but I disgress). I control that. I don't
>> control the IME, alas.
>
> No, the original issue was about whether some stuff Emacs has in
> memory could end up on your local disk somewhere. Pagefiles are just
> one such mechanism, but it isn't the only one.
I think you're all missing the most obvious snafu (which has actually
gotten me in trouble with our security folks): auto-save files.
next prev parent reply other threads:[~2023-04-15 11:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:48 Emacs in a Corporate Environment Yuan Cao
2023-04-12 20:10 ` Corwin Brust
2023-04-12 20:48 ` John Yates
2023-04-12 21:33 ` Yuan Cao
2023-04-13 0:08 ` Corwin Brust
2023-04-13 14:35 ` Marcin Borkowski
2023-04-14 14:36 ` Michael Albinus
2023-04-14 14:52 ` Eli Zaretskii
2023-04-14 15:08 ` Óscar Fuentes
2023-04-14 15:47 ` Eli Zaretskii
2023-04-14 16:11 ` tomas
2023-04-15 6:12 ` Marcin Borkowski
2023-04-15 7:31 ` tomas
2023-04-15 9:12 ` Marcin Borkowski
2023-04-15 6:11 ` Marcin Borkowski
2023-04-15 7:17 ` Eli Zaretskii
2023-04-15 7:34 ` tomas
2023-04-15 7:59 ` Eli Zaretskii
2023-04-15 8:21 ` tomas
2023-04-15 9:41 ` Eli Zaretskii
2023-04-15 11:16 ` Po Lu [this message]
2023-04-15 12:04 ` Marcin Borkowski
2023-04-15 12:18 ` Ruijie Yu via Users list for the GNU Emacs text editor
2023-04-15 13:22 ` tomas
2023-04-15 18:45 ` Michael Albinus
2023-04-15 6:10 ` Marcin Borkowski
2023-04-15 21:14 ` Björn Bidar
2023-04-16 7:51 ` Michael Albinus
2023-04-13 14:23 ` Marcin Borkowski
2023-04-13 17:23 ` Yuan Cao
2023-04-12 20:52 ` Jean Louis
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=87edoliefa.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).