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

At least 51 security issues... #192

Closed
T-vK opened this issue Mar 1, 2017 · 3 comments
Closed

At least 51 security issues... #192

T-vK opened this issue Mar 1, 2017 · 3 comments
Labels

Comments

@T-vK
Copy link

T-vK commented Mar 1, 2017

Are there any plans to update this project more regularely? Since the last commit, there have been at least 51 new security issues: https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html

I'd love to use this project, but it's just too dangerous if you only get security fixes every 3 months or so.

@GauthierPLM
Copy link

GauthierPLM commented Mar 1, 2017

Check the develop branch which is updated more often. The master branch represent the last released version.
Also, note that each release comes with a lot of changes, so it's not easy to update all the code base each time a version is released and it takes time.

@Eloston
Copy link
Member

Eloston commented Mar 1, 2017

Are there any plans to update this project more regularely?

Of course I would like to update more regularly, but as @Kendos-Kenlen mentioned, there's a lot of work involved. Update the patches requires a lot of trial-and-error and reading the source code for changes.

Currently, this process is done one patch at a time, since the current update method is very simplistic (which is difficult to parallelize). However, this issue has caused me to create #193.

Closing now since the question seems to be answered.

@ffa
Copy link

ffa commented Mar 2, 2017

there are other paths you can take until an update is available, particularly security tools. And, in general, using security tools goes a long way to preventing currently unknown exploits.

  1. use firejail or a sandbox
  2. use the umatrix extension

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

No branches or pull requests

4 participants