diff options
author | Brian Recchia <brian@recchia.name> | 2017-12-07 12:29:21 -0500 |
---|---|---|
committer | GitHub <noreply@github.com> | 2017-12-07 12:29:21 -0500 |
commit | dd7d6f97463aaec2833ce606e41cdbe32c1e2e2e (patch) | |
tree | b96ecd79f6e69e2aa4e0ca713c973f608c7d1b2b | |
parent | 79154f76defa627255891888f4dd62453194fc2c (diff) | |
download | xmr-stak-dd7d6f97463aaec2833ce606e41cdbe32c1e2e2e.zip xmr-stak-dd7d6f97463aaec2833ce606e41cdbe32c1e2e2e.tar.gz |
Grammar and wording regarding virus protection software
I chuckled reading that my virus protection software might flag the miner binary as “male ware,” and rewrote that section of the documentation.
-rw-r--r-- | doc/FAQ.md | 6 |
1 files changed, 2 insertions, 4 deletions
@@ -56,10 +56,8 @@ This typically means you are trying to run it on a CPU that does not have [AES]( ## Virus Protection Alert -Some Virus protection software flag the miner binary as *Male Ware*. -In this case the binary is moved to the quarantine area of the protection software. -This is a wrong alert and not avoid by use. -Add the binary to to protection software white list to solve this issue.s +Some virus protection software flags the miner binary as *malware*. This is a false positive — the software does not contain any malware (and since it is open source, you can verify that yourself!) +If your antivirus software flags **xmr-stak**, it will likely move it to its quarantine area. You may have to whitelist **xmr-stak** in your antivirus. ## Change Currency to Mine |