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

Recommended temporary/interim solution to antivirus program blocking Bisq 0.9.1 #2208

Closed
RoamingPhil opened this issue Jan 6, 2019 · 9 comments

Comments

Projects
None yet
5 participants
@RoamingPhil
Copy link

commented Jan 6, 2019

Hi, I know and am experiencing antivirus program (Webroot) blocking Bisq from running. Even if I set Bisq as a whitelisted item and temporarily turn off Webroot when starting Bisq, Bisq will quit shortly after I turn on Webroot.

Since Bisq is needed to run all the time even when waiting for trades, this would mean I have to run my computer (Windows 10) naked without antivirus protection, all the time, and hence not desirable.

I read that the Bisq team is trying to fix the problem. But is there a temporary, interim solution while we wait for the fix?

@HarryMacfinned

This comment has been minimized.

Copy link
Contributor

commented Jan 6, 2019

In the long run, using a dedicated linux computer is the right thing.
(a 100$ second-hand PC does a wonderful job).

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Jan 6, 2019

@RoamingPhil AV software can be a pain and I don't see much chances that we can fix the issues they cause by false positives soon. One thing though is that we want to add Windows code signing and maybe that helps with some AV software.
I really recommend to use a didicated Linux (or OSX) computer for any crypto currency related activities. Windows is terribly unsafe and AV software does not fix a failed security model.

@RoamingPhil

This comment has been minimized.

Copy link
Author

commented Jan 6, 2019

Thanks for the quick reply.
I agree running dedicated linux computer might be a safer solution. However, "dedicated" also means not convenient or flexible if I have only one laptop and am traveling all the time.
This problem is even worse for me since Bisq has to be running all the time for the offer to be seen by other Bisq users, not just at the setting up time and trading time.
Is this AV killing Bisq problem only related to the recent updates, i.e., v0.9.0 and v0.9.1? If yes, I can try to run an old version, i.e., v0.8.0, if it is available for downloading.

@ManfredKarrer

This comment has been minimized.

Copy link
Member

commented Jan 6, 2019

No its not related to update. Try using another AV software (AVG for example is known to not create false positives with Bisq).

@devinbileck

This comment has been minimized.

Copy link
Member

commented Jan 6, 2019

I agree it may not always be practical or feasible to run a dedicated Linux or macOS machine just for Bisq. An alternative is to setup a VPS which can be online all the time. However, this could come with other concerns.

Is Webroot informing you that it is blocking Bisq (e.g. a popup)? Is it quarantining any of Bisq's files?
When you attempted to "whitelist" Bisq, did you add the application directory to an exception list or something?

@RoamingPhil

This comment has been minimized.

Copy link
Author

commented Jan 7, 2019

Virtual machines may be an option. I may look at later.
I recall Webroot initially flagged (a pop up) the bisq during installation. I then temporarily disabled Webroot and reinstall, but found it then blocked the bisq.exe file (a pop up) during startup.
I then added the bisq.exe file to the whitelist. After this, I could start bisq.exe, but only halfway until after I entered the password before it quit automatically.
If I disable Webroot, I can start bisq without a problem. But shortly after re-enabling webroot, bisq quits.
I will try to add the full application folder to the whitelist to see if it fixed.
Thanks for the suggestion.

@freimair

This comment has been minimized.

Copy link
Member

commented Jan 9, 2019

just cross-referencing the original issue: #1943

Please feel free to share your findings!

@stale

This comment has been minimized.

Copy link

commented Apr 9, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the was:dropped label Apr 9, 2019

@stale

This comment has been minimized.

Copy link

commented Apr 16, 2019

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@stale stale bot closed this Apr 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.