Skip to main content ↑ ↓
Topic: foo_midi (Read 27372 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: foo_midi

Reply #225 –
Okay then. What exactly are you implying? That Microsoft's 2019 Community compiler is infected by design?

If you can produce builds that aren't detected at all, using the same toolkit and build environment that I use.

Fresh Windows 10 1909 x64 English ISO, downloaded from Microsoft. (size: 5,421,459,456; sha256: 01bf1eb643f7e50d0438f4f74fb91468d35cde2c82b07abc1390d47fc6a356be)

Installed into a fresh Linux Qemu/KVM virtual machine, using Gnome Boxes.

Switched to Virt-Manager for more flexibility post-install.

Install desktop updates to current status.

Install MSVC 2019 Community, and Clang-CL for some things now.

Install Git for Windows from its official site.

Git clone the entire bitbucket.org/losnoco/foobar2000 tree, recursively.

Build the component from the solution at <repository root>/plugins/foobar/foobar2000/plugins.sln

Re: foo_midi

Reply #226 –
Quote from: kode54 on
Fine. I'm pulling all binaries for my components. You fuckers can compile your own goddamn shit.
I'm done with this shit.
kode54, please don't let it get to you... :'(
and please don't de-list your components again... it saddens me when u do that...
I rely on your updates to keep Foobar2000 game music plugins working at their best and value your work...


I don't trust AV as far as I can throw them lol..

Kode54 all the componets I use were written by you and I have always considered u a trusted source.. ;^_^;

Re: foo_midi

Reply #227 –
kode54, v2.3.1 doesn't show Yamaha VSTi to me

Re: foo_midi

Reply #228 –
Quote from: kode54 on
Okay then. What exactly are you implying? That Microsoft's 2019 Community compiler is infected by design?

I imply nothing. I state the fact that two files in this component trigger alarms from my AV and apparently with a number of other AVs. I'm not the only one to notice this. That is all.

Re: foo_midi

Reply #229 –
I'd recommend sending detected files for false positive analysis to your antivirus vendor. That way you wouldn't stress the developer needlessly and you'd quickly hear from the vendor that the files are indeed clean. The false positive flagging won't stop unless paying customers complain loudly.

Re: foo_midi

Reply #230 –
GDI you guys! This is why we cannot have nice things.

Re: foo_midi

Reply #231 –
I'm putting them back, soon enough.

There's a new foo_midi, 2.3.2. The VSTi and Secret Sauce components require the MSVC 2015 runtimes, both 32 and 64 bit.

Re: foo_midi

Reply #233 –
Quote from: kode54 on
I'm putting them back, soon enough.

There's a new foo_midi, 2.3.2. The VSTi and Secret Sauce components require the MSVC 2015 runtimes, both 32 and 64 bit.

It works well and doesn't trigger any local or on-line AVs that I have access to. Thank you.

For the benefit of us many incredibly thick fucksticks (also known as every-day users, the target audience for Foobar2000 and its components,) did you find what was triggering all those AV engines? Or did our false-positive reports just catch up with their virus definition updates?

Re: foo_midi

Reply #234 –
Sorry, I need to clean up my language. I must apologize for calling you thick like that, I was really mad and in a bad place.

Basically, I had to do the following:

This step may not matter: Create new VM in place of old, install MSVC 2015 Update 3, final.

This step may matter: After getting everything compiled again, submitting my package to VirusTotal myself, and rescanning a few times to make sure it processed everything. It caught a few false positives, including in Microsoft's scanner.

This step matters: I submitted my software, packaged in an encrypted ZIP with the password "infected", as per instructions, to Microsoft, and kindly asked them to verify my assertion that it wasn't infected. Within about 8 hours, they verified that it was clean.

This step also matters: Once the above was completed, I rescanned the original upload at VirusTotal, which now comes out 100% clean. Note that three of the executables still register individually as "Malicious" or something with Cylance, even though the top level package does not.

It seems whenever I make updates to any of the executable subcomponents of foo_midi, or even the main component, I will need to complete the day long process of submitting it to Microsoft for whitelisting, every time. Oh well. Maybe I can convince someone to extend an EV certificate my way...
 

Re: foo_midi

Reply #235 –
Quote from: kode54 on
Oh well. Maybe I can convince someone to extend an EV certificate my way...
I would donate again when I have some $ to spare...
bills are killing me most of the time so its hard when I don't have much food most of the time...
sorry Kode54
 
SimplePortal 1.0.0 RC1 © 2008-2020