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

Move the wiki to user.js comments or README #220

Closed
17 tasks done
nodiscc opened this issue Feb 28, 2017 · 11 comments
Closed
17 tasks done

Move the wiki to user.js comments or README #220

nodiscc opened this issue Feb 28, 2017 · 11 comments

Comments

@nodiscc
Copy link
Contributor

nodiscc commented Feb 28, 2017

From #218:

Maybe we could document these in the wiki?

:/ I think information is currently too much scattered between user.js comments, the wiki, the readme... In my experience it leads to duplicate/outdated/don't-know-where-to-look documentation. It can be made cleaner eg by:

@nodiscc
Copy link
Contributor Author

nodiscc commented Feb 28, 2017

Move info from https://github.com/pyllyukko/user.js#what-does-it-do to section descriptions in user.js, and instead generate the "What does it do?" section do from section descriptions in user.js (ezpz sed/awk/Makefile magic)

I don't think that's a good idea. I think we should have it the similar way it's now, kinda summarizing different aspects of the hardening.


Move some tests from https://github.com/pyllyukko/user.js#online-tests to relevant prefs/sections in user.js

Moved or copied? I think the online tests section is good in the README as it is, but some of the tests could be also in the user.js.

@nodiscc
Copy link
Contributor Author

nodiscc commented Mar 1, 2017

@pyllyukko
Copy link
Owner

network.proxy.type (http://kb.mozillazine.org/Network.proxy.type) found in Misc page: no such entry in user.js

Not needed.

browser.frames.enabled (https://bugzilla.mozilla.org/show_bug.cgi?id=729030) found in Misc page: no such entry in user.js

Not needed.

@nodiscc
Copy link
Contributor Author

nodiscc commented Mar 1, 2017

@nodiscc
Copy link
Contributor Author

nodiscc commented Mar 1, 2017

@nodiscc
Copy link
Contributor Author

nodiscc commented Mar 1, 2017

First part completed (main issue checklist + FAQ migration), along with some doc improvements.
@pyllyukko I will open a Pull Request and wait for review before continuing.
Feel free to delete the wiki (I deleted all pages, more info at https://github.com/pyllyukko/user.js/wiki).
There's also the few inconsistencies reported above, if you'd like to have a look.

Thanks

@pyllyukko
Copy link
Owner

Thanks! I disabled the wiki and start reviewing the PR.

@nodiscc
Copy link
Contributor Author

nodiscc commented Mar 14, 2017

Once current PRs are reviewed we can resume working on this (see unchecked checkbox items)

@pyllyukko
Copy link
Owner

security.enable_tls_session_ticket found in TLS/HTTPS/OCSP page: no such entry in user.js

Sound like security.ssl.disable_session_identifiers.

security.enable_ssl3 (https://support.mozilla.org/en-US/kb/enable-ssl-fix-cannot-connect-securely-error?redirectlocale=en-US&redirectslug=Firefox+cannot+connect+securely+because+the+SSL+protocol+is+disabled) found in TLS/HTTPS/OCSP page: no such entry in user.js

This should be covered by security.tls.version.min.

security.warn_entering_weak (http://kb.mozillazine.org/About:config_entries#Security) found in UI Related page: no such entry in user.js

Sounds like this is deprecated: Re: What happened to security.warn settings in about:config. They are missing in FF25. Please help!!.

security.ssl.warn_missing_rfc5746 (https://developer.mozilla.org/en/Preferences/Mozilla_preferences_for_uber-geeks) not found in user.js, no longer documented on the page

Sounds exactly like security.ssl.treat_unsafe_negotiation_as_broken.

Marking these as done.

@pyllyukko
Copy link
Owner

Once current PRs are reviewed we can resume working on this (see unchecked checkbox items)

BTW. the checkbox counter in the issues list doesn't seem to count the ones in comments, but only the ones in the first comment/description. It currently shows 17/17, even though there are still open ones in the comments.

@nodiscc
Copy link
Contributor Author

nodiscc commented Mar 20, 2017

browser.history_expire* prefs are no longer present in recent Firefox releases. Everything fixed, closing.

@nodiscc nodiscc closed this as completed Mar 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants