- 29 Jan, 2015 5 commits
-
-
Franco Fichtner authored
-
Franco Fichtner authored
While there, "maybe" copyright translates to "yes" copyright. If someone wants to oppose this, feel free to verify each code line and submit a pull request to remove those two statements.
-
Franco Fichtner authored
We do not want to use OpenSSL from base and it may go away at some point as well, breaking e.g. this page. Instead, use the internal tools or the OpenSSL plugin. More of this on the way.
-
Ad Schellevis authored
-
Jos Schellevis authored
-
- 28 Jan, 2015 6 commits
-
-
Jos Schellevis authored
-
Franco Fichtner authored
* US and CA are in the alphabetic list already; no more favouritism. * Use require_once consistently. Minor header tweaks. * Replace legacy State/City info and fix spelling for "Saschsen". Nice touch Jos, I had a big smile on my face while skimming that commit. :)
-
Ad Schellevis authored
* added save/backup actions on config class
-
Jos Schellevis authored
-
Jos Schellevis authored
-
Ad Schellevis authored
* initial model implementation using Phalcon validators and custom binding to config object Still a lot to dow here, no impact on current install base
-
- 27 Jan, 2015 2 commits
-
-
Jos Schellevis authored
-
Jos Schellevis authored
-
- 26 Jan, 2015 2 commits
-
-
Ad Schellevis authored
-
Ad Schellevis authored
-
- 25 Jan, 2015 2 commits
-
-
Franco Fichtner authored
Really don't want to ship this file locally so that others might be encouraged to edit it (again).
-
Franco Fichtner authored
* Prefer the openssh-portable port, but fall back to the base version if it is available. * Refactor the key generation to produce less duplicated code. * Locking is completely bogus, but I have no clue how to fix that short term without doing a full audit of the subsystem-dirty mechanic.
-
- 24 Jan, 2015 4 commits
-
-
Franco Fichtner authored
-
Franco Fichtner authored
-
Franco Fichtner authored
-
Franco Fichtner authored
While there, remove custom code and things that are not needed. Also, there's this thing called `require_once'.
-
- 23 Jan, 2015 2 commits
-
-
Franco Fichtner authored
* Add pkg autoremove for stale package removal. * Refactor progress file output in case it'll change. * Truncate the progress file directly on startup. Unfortunately, that doesn't solve the lingering of upgrade info after navigating away from the firmware page. Need to find a better solution here...
-
Jos Schellevis authored
-
- 21 Jan, 2015 4 commits
-
-
Ad Schellevis authored
-
Jos Schellevis authored
-
Jos Schellevis authored
-
Jos Schellevis authored
-
- 20 Jan, 2015 1 commit
-
-
Ad Schellevis authored
-
- 19 Jan, 2015 1 commit
-
-
Jos Schellevis authored
Added searchbox to dropdown in firewal_rules, the drop down becomes visible when too many interfaces are active to be shown in tabs.. this features uses silviomoreto/bootstrap-select, license is MIT. Also added the MIT license to the templates root.
-
- 18 Jan, 2015 1 commit
-
-
Frank Wall authored
-
- 16 Jan, 2015 2 commits
-
-
Franco Fichtner authored
PHP plugins may change and then clobber the custom php.ini we have previously generated. To make sure everything keeps running smoothly, always regerate it directly after an upgrade, even though there may have been no changes.
-
Jos Schellevis authored
-
- 13 Jan, 2015 2 commits
-
-
Jos Schellevis authored
-
Jos Schellevis authored
Upgrade for firmware upgrade add check for pkg package and change scripting to allow sinlge package upgrade, also fixes #27
-
- 11 Jan, 2015 6 commits
-
-
Franco Fichtner authored
Hides complexity to make it easier to migrate away from the legacy 'check_reload_status' soon.
-
Franco Fichtner authored
-
Franco Fichtner authored
-
Franco Fichtner authored
-
Phil Davis authored
At the moment the user can answer "yes" to most of the questions, but then later code only checks if the answer is "y". Thus you can type in "yes" in some places, have it accepted, but actually the negative action is taken. That is weird and will mess up people who try typing a whole string starting with "y". With this change it makes the user type one of "y", "yes", "n", "no". When they type 1 of those, it is turned into either "y" or "n". Then the existing implementation logic all works as expected. Hopefully this is the "final" version that fixes the behavior of the (y/n) questions. I also included the bit at 296-297 which adds the CIDR bit-count range to the prompt, so the user can see exactly what input is valid/expected there. Redmine issue #4100
-
Phil Davis authored
Currently this allows the user to input any number for the CIDR. I happened to try 44 for an IPv4 CIDR when playing. This fixes that little bug - I think it is good to commit that first/separately so it can be identified apart from the other (y/n) checking/handling I am working on. Better to have separate commits for distinct bugs.
-