Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Defender false alarm #16

Open
ooiikkjj opened this issue May 29, 2021 · 2 comments
Open

Windows Defender false alarm #16

ooiikkjj opened this issue May 29, 2021 · 2 comments

Comments

@ooiikkjj
Copy link

cal-4018 shows up in Windows Defender as infected by virus
is there a new version?
thanks...

@Folds Folds changed the title virus Windows Defender false alarm May 29, 2021
@Folds
Copy link
Owner

Folds commented May 29, 2021

@ooiikkjj — Thank you for pointing out this problem with Windows Defender.

cal-4018 does not contain any viruses. It is compiled from human-readable source code, using a compiler whose source code is part of that human-readable source code. The source code is short enough that individual persons can, and have, read and analyzed all of the code in various versions of the CAL.
cal-4018 is capable of copying files, and of making a new version of itself. But it only does so in response to specific requests by the user. The documentation explains how to make such requests.

Windows Defender keeps a library of tiny snippets of executable code. For example, it thought that the code "to bump a rider" along a string in cal-4016 was suspicious. (This code literally just incremented two pointers.) One of the changes in cal-4018 was a minor change in how this incrementing was done, which (for a while) caused Windows Defender to not complain about cal-4018.

At this time, I do not have time to investigate this issue. But if you (and/or someone else) can identify:

  • What virus Windows Defender is complaining about,
  • Which snippet of executable code is making Windows Defender suspicious,
  • Which line(s) of source code correspond to that executable code, and
  • A proposed change to the source code that is functionally equivalent, but allays Windows Defender's suspicions,

Then I will be happy to:

  • Verify that the proposed change is functionally equivalent, and
  • Release an updated version of the CAL.

You do not need to do all four steps yourself. Simply providing Windows Defender's full complaint about cal-4018 would be helpful.

@ooiikkjj
Copy link
Author

ooiikkjj commented May 30, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants