Skip to content
This repository has been archived by the owner on May 20, 2021. It is now read-only.

GFM 0.2.0 blocked by Carbon Black security software #151

Open
jan-molak opened this issue May 13, 2019 · 3 comments
Open

GFM 0.2.0 blocked by Carbon Black security software #151

jan-molak opened this issue May 13, 2019 · 3 comments
Assignees

Comments

@jan-molak
Copy link

Hi there and thanks for the GFM!

It looks like v0.2.0 is being flagged as a security risk by the Carbon Black corporate security software:

cb security issue with gfm

Version 0.1.14 worked fine, so perhaps something has changed in the way how the JXBrowser is being installed?

Best,
Jan

@jan-molak jan-molak changed the title GFM 2.0 blocked by Carbon Black security software GFM 0.2.0 blocked by Carbon Black security software May 13, 2019
@ShyykoSerhiy ShyykoSerhiy self-assigned this May 13, 2019
@jan-molak
Copy link
Author

I did some more digging and it looks like making the installation location of jxbrowser configurable would solve the problem.

Context: companies using Carbon Black often specify a location on the file system where developers can install their tools (like "C:\Projects", "C:\Tools", etc.). If GFM allowed us to install the jxbrowser at such custom location it would address the problem.

@ShyykoSerhiy
Copy link
Owner

ShyykoSerhiy commented May 22, 2019

I'll add an option for dynamic jxbrowser download in a next release. It will 'fix' #32 and will hopefully fix this issue as well. You can expect the new version at the end of this weekend.

@jan-molak
Copy link
Author

Oh cool, that sounds great! Thanks for putting so much effort into this 👍

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

No branches or pull requests

2 participants