[Issue 18786] AV program detects malware in windows download of DMD (page 2)

https://issues.dlang.org/show_bug.cgi?id=18786 Alexey Kulentsov <crimaniak@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |crimaniak@gmail.com --- Comment #10 from Alexey Kulentsov <crimaniak@gmail.com> --- DMD 2.082.0, Microsoft Windows 10 Enterprise Build 17134 - Defender prevents any work with DMD or compiled by DMD programs. --

https://issues.dlang.org/show_bug.cgi?id=18786 Martin Nowak <code@dawg.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |code@dawg.eu --- Comment #11 from Martin Nowak <code@dawg.eu> --- (In reply to Alexey Kulentsov from comment #10) > DMD 2.082.0, Microsoft Windows 10 Enterprise Build 17134 - Defender prevents any work with DMD or compiled by DMD programs. We're actually signining Windows binaries since 2.082.0 and didn't have any further Defender issues after also submitting dmd for inspection. Do you have any additional info to reproduce the issue, in particular the one with self-built binaries. [¹]: https://dlang.org/changelog/2.082.0.html#signed_windows_binaries --

https://issues.dlang.org/show_bug.cgi?id=18786 --- Comment #12 from anonymous4 <dfj1esp02@sneakemail.com> --- I downloaded 2.082.1, Edge showed message "Running security scan" which took a long time, I opened the Defender interface, and after some time Edge reported that download is complete. Maybe the scan just takes a long time. --

https://issues.dlang.org/show_bug.cgi?id=18786 --- Comment #13 from Alexey Kulentsov <crimaniak@gmail.com> --- Created attachment 1716 --> https://issues.dlang.org/attachment.cgi?id=1716&action=edit Compiled utility rejected by Windows Defender in corporate network --

November 09, 2018

[Issue 18786] AV program detects malware in windows download of DMD

Posted by Alexey Kulentsov

Permalink

Alexey Kulentsov

Permalink

https://issues.dlang.org/show_bug.cgi?id=18786

--- Comment #14 from Alexey Kulentsov <crimaniak@gmail.com> ---
(In reply to Martin Nowak from comment #11)
> We're actually signining Windows binaries since 2.082.0 and didn't have any further Defender issues after also submitting dmd for inspection.
I am in the corporate network with centralized administration. Now I think, maybe, corporate rules are more strict than defaults, and rejects unknown self-signed certificates.

> Do you have any additional info to reproduce the issue, in particular the one with self-built binaries.

DMD installer from official site, DMD version:
DMD32 D Compiler v2.082.0

Copyright (C) 1999-2018 by The D Language Foundation, All Rights Reserved
written by Walter Bright

Utility source and executable (mpgit) are attached to the issue in the previous
comment.

--

https://issues.dlang.org/show_bug.cgi?id=18786 --- Comment #15 from Seb <greeenify@gmail.com> --- It's not a self-Signet certificate, it's one from an officially approved windows certificate vendor. Not sure whether we can do more for you. Maybe you just need to talk to your admins? --

https://issues.dlang.org/show_bug.cgi?id=18786 --- Comment #16 from dlangBugzillaToGithub <robert.schadek@posteo.de> --- THIS ISSUE HAS BEEN MOVED TO GITHUB https://github.com/dlang/installer/issues/662 DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB --

Forums