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

Fix Router Access page #854

Merged
merged 6 commits into from
Mar 1, 2020

Conversation

n3vu0r
Copy link
Contributor

@n3vu0r n3vu0r commented Feb 22, 2020

  • Update UCI after saving changes w/o redirect

    In contrast to basic.js, access.js misses to update uciOriginal after saving changes without redirect. Resetting data afterwards results in disabling all remote_accepts (Remote Web Access and Remote SSH Access) because when saving changes, the old firewall sections are deleted from uciOriginal before it is cloned into uci to which the new firewall sections are added. But in the end, uciOriginal must be updated to uci to reflect all the changes including the new firewall sections.

Found some other issues, more commits coming.

@n3vu0r n3vu0r changed the title Update UCI after saving changes w/o redirect. Fix Router Access page Feb 23, 2020
  * Restart firewall on demand.
  * Restart uhttpd on demand.
  * Refresh page on demand, with delay when uhttpd is restarted.
  * Detect if uhttpd is used as a reverse proxy's backend and avoid redirect.
  * Support uhttpd's redirect_https as another HTTP -> HTTPS protocol option.
      * If enabled, sets remote web port field read-only with dashed border and
        updates it when local web port changes. (New common.js functions)
  * Order protocols by security and preselect the next more secure one when
    previously selected remote protocol is no option with new local protocol.
  * Reset proofread color when resetting page. (New common.js function)
  * Reset disabled color instead of setting it to black when enabling element.
  * Support uhttpd's rfc1918_filter as checkbox with unchanged default being on.
  * Detect access area (LAN/WAN or local/remote) to warn when about to lock out.
  * Warn when about to lock out from remote web access.
      * If affected by disabling remote access.
      * If affected by enabling RFC 1918 filter. (New common.js functions)
  * Warn when about to lock out from local/remote web access.
      * On unfit protocol change if uhttpd is used as a reverse proxy's backend.
  * Show access chain of domains and IP addresses as part of warnings.
  * Add dividers before remote web, common web, and remote SSH settings.
  * Add missing visibility initialization of SSH help.
  * Avoid failing double initialization of help visibility when resetting page.
  * Use smooth scrollIntoView(alignToTop = false) instead of jumpy hashtag.
Copy link
Contributor

@lantis1008 lantis1008 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, this looks like a great changeset. Just a few queries to review please.

package/gargoyle/files/www/access.sh Outdated Show resolved Hide resolved
package/gargoyle/files/www/js/access.js Show resolved Hide resolved
package/gargoyle/files/www/js/access.js Outdated Show resolved Hide resolved
package/gargoyle/files/www/js/access.js Outdated Show resolved Hide resolved
package/gargoyle/files/www/js/common.js Outdated Show resolved Hide resolved
@lantis1008
Copy link
Contributor

Also your other code changes will go in this weekend, have not forgotten.

@ericpaulbishop ericpaulbishop merged commit e6715e9 into ericpaulbishop:1.12 Mar 1, 2020
@lantis1008
Copy link
Contributor

Thanks.

Just a reminder, preferably new changes go into master, as that is where the future of Gargoyle lies.
If you would like the change backported to 1.12 as well, please let me know in the pull request and i'll organise it. It is easier for me to go backwards rather than forwards in these cases.

@n3vu0r n3vu0r mentioned this pull request Mar 1, 2020
@n3vu0r
Copy link
Contributor Author

n3vu0r commented Mar 1, 2020

Good to know, thanks!

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

Successfully merging this pull request may close these issues.

4 participants