1. 29 Jan, 2015 5 commits
  2. 28 Jan, 2015 6 commits
  3. 27 Jan, 2015 2 commits
  4. 26 Jan, 2015 2 commits
  5. 25 Jan, 2015 2 commits
    • Franco Fichtner's avatar
      openssl: fix issues with port version not finding config · 9af57742
      Franco Fichtner authored
      Really don't want to ship this file locally so that others
      might be encouraged to edit it (again).
      9af57742
    • Franco Fichtner's avatar
      rc: rework sshd handling · ab28de2e
      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.
      ab28de2e
  6. 24 Jan, 2015 4 commits
  7. 23 Jan, 2015 2 commits
  8. 21 Jan, 2015 4 commits
  9. 20 Jan, 2015 1 commit
  10. 19 Jan, 2015 1 commit
  11. 18 Jan, 2015 1 commit
  12. 16 Jan, 2015 2 commits
  13. 13 Jan, 2015 2 commits
  14. 11 Jan, 2015 6 commits
    • Franco Fichtner's avatar
      inc: remove a wee bit of over-engineering · 1b6984c7
      Franco Fichtner authored
      Hides complexity to make it easier to migrate away from
      the legacy 'check_reload_status' soon.
      1b6984c7
    • Franco Fichtner's avatar
      mvc: fix a couple of style errors · e40924c6
      Franco Fichtner authored
      e40924c6
    • Franco Fichtner's avatar
      3ff299e1
    • Franco Fichtner's avatar
      src: apply whitespace cleanups · 5e9ab6d8
      Franco Fichtner authored
      5e9ab6d8
    • Phil Davis's avatar
      Validation of y/n answers in setlanip · 6b1ca069
      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
      6b1ca069
    • Phil Davis's avatar
      rc.initial.setlanip fix validation of CIDR within range · e19ddeff
      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.
      e19ddeff