From: Fabrice Popineau <fabrice.popineau@centralesupelec.fr>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Emacs master, security concernes, ms-windows
Date: Thu, 14 Sep 2017 17:56:46 +0200 [thread overview]
Message-ID: <CAFgFV9MRdPBcD7+soO_apmSDDjpq18Ni0VBuOdWEU9X=UUU0ZA@mail.gmail.com> (raw)
In-Reply-To: <87fubpxq60.fsf@qcore>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
2017-09-14 17:20 GMT+02:00 Óscar Fuentes <ofv@wanadoo.es>:
> Fabrice Popineau <fabrice.popineau@centralesupelec.fr> writes:
>
> > At the moment, any libpng.dll (for example) on the PATH can be loaded by
> > emacs.
> > With this restriction, only the one provided with an emacs package will
> be.
> >
> > I came to 'fix' this because I am using the Anaconda Python distribution
> > which also
> > provides its own set of dlls. At some point I got a failure because their
> > dlls got loaded,
> > instead of the mingw64 ones.
>
> I suffered a similar problem on the past.
>
> The real concern about this patch is that it raises quite a bit the
> minimum supported OS version, which is a big no-no, AFAIK.
>
> Although I'm not sure what happens if you pass an unsupported flag to
> LoadLibraryEx.
>
>
> It is possible to implement your idea by using explicit paths.
>
Yes, emacs could itself decide where to look for these dlls.
At least for the ones that are non system.
And the system ones should be looked for only in the System32 directory.
I know that my patch was a radical one. I mainly wanted to raise the issue.
Fabrice
[-- Attachment #2: Type: text/html, Size: 1939 bytes --]
next prev parent reply other threads:[~2017-09-14 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 7:58 Emacs master, security concernes, ms-windows Fabrice Popineau
2017-09-14 13:33 ` Óscar Fuentes
2017-09-14 13:46 ` Fabrice Popineau
2017-09-14 15:20 ` Óscar Fuentes
2017-09-14 15:56 ` Fabrice Popineau [this message]
2017-09-14 17:27 ` Eli Zaretskii
2017-09-14 17:24 ` Eli Zaretskii
2017-09-14 17:18 ` Eli Zaretskii
2017-09-14 14:13 ` Andy Moreton
2017-09-14 17:08 ` Eli Zaretskii
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='CAFgFV9MRdPBcD7+soO_apmSDDjpq18Ni0VBuOdWEU9X=UUU0ZA@mail.gmail.com' \
--to=fabrice.popineau@centralesupelec.fr \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.