[vlc-devel] [PATCH] win32: do not load wininet.dll on startup, it's not a Known DLL

[Pierre Ynard]

> And then you break the signature.

Or you strip/replace it etc...

> > You wake up in the morning, your paint is peeling, your curtains
> > are gone, and the water is boiling. Which problem do you deal with
> > first?
>
> Exactly, you start with the biggest issues, and you fix them, one by
> one.

No, that's not the answer to the riddle. But you seem pretty dead set
and it would be lost on you anyway.

> Which is EXACTLY what is already done on macOS and also what is
> happening on Windows 10.

Excellent! I hope it happens, the issues seen in these threads seem
challenging!

See, I've given up on my dissenting opinion, how nice for you.

> Well, you see? We do.
> With what we've done, and the loading plugins signature check, the
> integrity is maintained. And BECAUSE we use embedded manifest, and
> BECAUSE we use dlopening of un-knowndll.

Okay, it'll work out just fine :) It always does every time something
gets pushed despite reviews :)

> Plonk. You go too far. What corporate interests?

You ask, but:

 - you already know the answer, and are playing dumb or taking a
   rhetorical posture
 - you already know the answer and think it goes too far
 - you won't even read the answer because you plonked me
 - you're obviously dead set to deny and refute the answer anyway

> You've already insulted me more than twice in this thread.

You make it easy!

> Once again, you show that you've read absolutely nothing about the
> issue. So let me explain it again: YOU CANNOT MODIFY KnownDLL LIST!

I've only read the thread. I don't know if your arguments in the thread
about the issue count for "absolutely nothing", but according to them,
it's hard but possible:

Le perjantaina 10. maaliskuuta 2017, 17.50.46 EET Jean-Baptiste Kempf a 
écrit :
> On Fri, 10 Mar 2017, at 17:49, Rémi Denis-Courmont wrote:
> > You can also remove DLLs from the known list.
> 
> This requires a lot of manipulation and is hard to do without breaking
> the whole Windows.

> How about you come and ask on IRC what we're working on?
> Instead of coming and attacking us like you are doing?

How about you don't push code and do things with flaws to be attacked?
Oh wait, sorry, that's not how it works, I'm the one required to justify
myself.

> Sorry, but then you have no idea what you are talking about.

> You don't know what known libraries are.

> You speak without understanding anything

> How about you come and ask on IRC what we're working on?
> Instead of coming and attacking us like you are doing?

> Once again, you show that you've read absolutely nothing about the
> issue.

> Before answering, you should really look at the documentation, install
> Windows, and read a bit about what has been done.

Nice demonstration of how not completing the prerequisite reading,
tinkering, IRC discussions, and having no authority on the topic
disqualifies me from contributing an opinion? Is that your point? It's
true that you have president and CEO authority, meanwhile your fixes got
pushed, and I got pushed into giving up my dissenting opinion - which
was of course disqualified anyway. Life is nice.

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."