Avoid "binary-component" entries in Chrome registration to opt-in for Default to Compatible #42

Closed
xabolcs opened this Issue Mar 14, 2012 · 2 comments

2 participants

@xabolcs

As the comment states in #37, NTT could be compatible by default.

@xabolcs xabolcs added a commit to xabolcs/nightlytt that referenced this issue Mar 20, 2012
@xabolcs xabolcs Don't register binary crashme components. Fixes #42 cc94d93
@xabolcs

Should NTT track Bug 728429?

At first sight it is not needed.

@whimboo

I have already checked bug 728429 together with Ted and we are good. The DLLs have been compiled with ASLR support.

I have merged the pull request.

@whimboo whimboo closed this Mar 20, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment