[Koha-bugs] [Bug 9562] New: System preference 'insecure' shows wrong value after update to v3.10

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9562

            Bug ID: 9562
           Summary: System preference 'insecure' shows wrong value after
                    update to v3.10
    Classification: Unclassified
 Change sponsored?: ---
           Product: Koha
           Version: 3.10
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: P5 - low
         Component: System Administration
          Assignee: koha-bugs at lists.koha-community.org
          Reporter: fred.pierre at smfpl.org
                CC: gmcharlt at gmail.com

There is an omission in the update script for v3.10, and it affects a critical
system preference: 'insecure'

  On our v3.5 server the value corresponding to "Don't Allow" was recorded as
"NO" - on the new system the value of "Don't Allow" is 0 (zero).

  WARNING: Changing the value to "Allow" (1) could completely hose your system
and could require a new Koha installation!

  The update script did not change the table value from "No" to "0" so the
'insecure' system preference shows up as "Allow" even though the system
interprets the "NO" value as "Don't Allow" for login functionality. In other
words, we still have to log in, and our Koha system is fully functional.

  However this could lead updating clients to believe that the proper setting
is "Allow" when production systems should really use "Don't Allow"

P.S. My past experience of switching to "Allow" was very negative - I could no
longer log in to my system at all - luckily it was a test server.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.