From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Suspected bug with LaTeX export: the pdf does not open
Date: Mon, 20 Aug 2018 12:59:07 -0400 [thread overview]
Message-ID: <87efetm0tg.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 23418.60380.333783.437135@frac.u-strasbg.fr
Alain.Cochard@unistra.fr writes:
> Nick Dokos writes on Mon 20 Aug 2018 11:50:
>
> > [...] you have security problems: the current Fedora is 28, Fedora
> > 26 is either end-of-life already or about to be shortly, and Fedora
> > 23 is obsolete and possibly dangerous. Please consider upgrading.
>
> Thanks. Yes, 23 is obsolete. But what do you mean "possibly
> dangerous"? What are the risks?
>
I'm pretty sure you have not had security updates for it for a while: see
https://fedoramagazine.org/fedora-23-end-of-life/
so you are running with unpatched bugs since Dec. 2016. Some of these
bugs *might* be remotely exploitable. I would not use such a machine
to e.g. check my bank account from a public place - *I* would not use it
from a private place over WiFi either - maybe over hardwired ethernet
but that would depend on other factors; but different people
tolerate the possibility of such problems differently: you will have
to decide what to do in your case. I hope this information can help
you make an informed decision.
--
Nick
"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler
prev parent reply other threads:[~2018-08-20 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 4:52 Suspected bug with LaTeX export: the pdf does not open Alain.Cochard
2018-08-18 19:34 ` Robert Klein
2018-08-18 20:59 ` Alain.Cochard
2018-08-19 2:31 ` Tim Cross
2018-08-19 4:21 ` Alain.Cochard
2018-09-23 8:41 ` Alain.Cochard
2018-09-24 3:37 ` Alain.Cochard
2018-08-20 15:50 ` Nick Dokos
2018-08-20 16:27 ` Alain.Cochard
2018-08-20 16:59 ` Nick Dokos [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efetm0tg.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).