On 11/3/16 7:34 AM, Ethan Watson wrote:
Turns out we have some good contacts at F-Secure though. So I can see
about getting the problem fixed at the detection level - and because of
the way the security community operates, that knowledge should flush
across to things like Windows Defender.
http://imgur.com/5DnCWYw
One of our guys just tried compiling and running a simple Hello
World program. F-Secure jumped right in.
Code signing the compiler isn't enough. It's been a persistent
problem around here with DMD generated binaries that F-Secure
will pick it up. Needless to say, if
On Wednesday, 12 October 2016 at 06:39:05 UTC, Thomas Mader wrote:
On Tuesday, 11 October 2016 at 06:09:03 UTC, Thomas Mader wrote:
I worked with NSIS and InnoSetup. InnoSetup is much cleaner
and easier.
At work we switched from NSIS to InnoSetup and we create MSI
packages from NSIS and
On Tuesday, 11 October 2016 at 01:37:55 UTC, Martin Nowak wrote:
Whatever makes more sense. From my very limited understanding
.msi installers are natively understood installers in Windows,
and the weapon of choice for robust and more professional
installers.
If innosetup is just another NSIS
On Tuesday, 11 October 2016 at 06:09:03 UTC, Thomas Mader wrote:
I worked with NSIS and InnoSetup. InnoSetup is much cleaner and
easier.
At work we switched from NSIS to InnoSetup and we create MSI
packages from NSIS and InnoSetup packages IIRC.
I think it's better to go with InnoSetup because
On Tuesday, 11 October 2016 at 01:37:55 UTC, Martin Nowak wrote:
On Saturday, 20 August 2016 at 13:45:11 UTC, Basile B. wrote:
"to MSI using innosetup" ?
There's a misunderstanding here. Inno setup doesn't compile to
MS installer, it's a complete independant solution.
Whatever makes more
On Saturday, 20 August 2016 at 13:45:11 UTC, Basile B. wrote:
"to MSI using innosetup" ?
There's a misunderstanding here. Inno setup doesn't compile to
MS installer, it's a complete independant solution.
Whatever makes more sense. From my very limited understanding
.msi installers are
On Saturday, 20 August 2016 at 13:26:03 UTC, Martin Nowak wrote:
On 08/20/2016 03:21 PM, Martin Nowak wrote:
On Monday, 15 August 2016 at 20:47:10 UTC, Basile B. wrote:
Please share your suggestions for how to help with the false
positive issue (or just continue laughing in ignorance based
on
On 08/20/2016 03:21 PM, Martin Nowak wrote:
> On Monday, 15 August 2016 at 20:47:10 UTC, Basile B. wrote:
>>> Please share your suggestions for how to help with the false positive
>>> issue (or just continue laughing in ignorance based on an assumption
>>> of something I never said).
>>
>> If the
On Monday, 15 August 2016 at 20:47:10 UTC, Basile B. wrote:
Please share your suggestions for how to help with the false
positive issue (or just continue laughing in ignorance based
on an assumption of something I never said).
If the origin of the problem is NSIS then in a first time it
On Tuesday, 16 August 2016 at 05:38:00 UTC, Ethan Watson wrote:
D code seems to be sufficiently different that virus scanners
get confused. Both Windows Defender and F-Secure complained
about it being the same trojan in fact.
Don't see any F-Secure problem for dmd-2.071.1.exe.
On Tuesday, 16 August 2016 at 05:38:00 UTC, Ethan Watson wrote:
D code seems to be sufficiently different that virus scanners
get confused.
Well, nothing can be said for sure as nobody bothered with data,
but if all assumptions are met, one thing to try is to compile
with msvc toolchain
On Monday, 15 August 2016 at 19:58:14 UTC, Brad Anderson wrote:
Please share your suggestions for how to help with the false
positive issue (or just continue laughing in ignorance based on
an assumption of something I never said).
DevExpress components are distributed as an encrypted
On Monday, 15 August 2016 at 20:43:59 UTC, Basile B. wrote:
I'm afraid to see people overreacting in front of a minor and
temporary problem.
This is not the first time this is a problem.
Our scanner at Remedy regularly used to block code sent to and
from Walter at the email level. Sometimes
On Monday, 15 August 2016 at 23:58:01 UTC, Mike Parker wrote:
On Monday, 15 August 2016 at 20:43:59 UTC, Basile B. wrote:
It's not trolling (unless you define trolling as "everything
that goes againt my position"), I just exposed my arguments.
I'm afraid to see people overreacting in front of
On Monday, 15 August 2016 at 20:43:59 UTC, Basile B. wrote:
It's not trolling (unless you define trolling as "everything
that goes againt my position"), I just exposed my arguments.
I'm afraid to see people overreacting in front of a minor and
temporary problem. It seems that 3 or 4 posts are
On Monday, 15 August 2016 at 20:43:59 UTC, Basile B. wrote:
It's not trolling (unless you define trolling as "everything
that goes againt my position"), I just exposed my arguments.
I'm afraid to see people overreacting in front of a minor and
temporary problem. It seems that 3 or 4 posts are
On Monday, 15 August 2016 at 19:58:14 UTC, Brad Anderson wrote:
On Monday, 15 August 2016 at 18:52:03 UTC, Basile B. wrote:
On Monday, 15 August 2016 at 17:05:32 UTC, Brad Anderson wrote:
With all of the issues people are having with Windows [...]
There is already an issue created for this
On Monday, 15 August 2016 at 20:07:30 UTC, Seb wrote:
On Monday, 15 August 2016 at 19:58:14 UTC, Brad Anderson wrote:
At work we added class 3 code signing and it helped quite a
bit with McAfee's warnings about our software for end users.
In that case it was warnings about new releases of our
On Monday, 15 August 2016 at 19:58:14 UTC, Brad Anderson wrote:
At work we added class 3 code signing and it helped quite a bit
with McAfee's warnings about our software for end users. In
that case it was warnings about new releases of our software
that hadn't had many installs yet.
On Monday, 15 August 2016 at 18:52:03 UTC, Basile B. wrote:
On Monday, 15 August 2016 at 17:05:32 UTC, Brad Anderson wrote:
With all of the issues people are having with Windows Defender
now would be a good time to start code signing the Windows
installer and binaries (doing this is the first
On Monday, 15 August 2016 at 19:08:56 UTC, Basile B. wrote:
How this is called in everyday's world ? racketeering ?
exactly.
On Monday, 15 August 2016 at 18:52:03 UTC, Basile B. wrote:
On Monday, 15 August 2016 at 17:05:32 UTC, Brad Anderson wrote:
With all of the issues people are having with Windows Defender
now would be a good time to start code signing the Windows
installer and binaries (doing this is the first
On Monday, 15 August 2016 at 17:05:32 UTC, Brad Anderson wrote:
With all of the issues people are having with Windows Defender
now would be a good time to start code signing the Windows
installer and binaries (doing this is the first thing Microsoft
suggests on their page for Software
With all of the issues people are having with Windows Defender
now would be a good time to start code signing the Windows
installer and binaries (doing this is the first thing Microsoft
suggests on their page for Software Developers about Windows
Defender false positives).
I propose the D
25 matches
Mail list logo
