BIND 10 #2641: Disable default account, require authentication setup during initialization

[BIND 10 Development]

#2641: Disable default account, require authentication setup during initialization
-------------------------------------+-------------------------------------
            Reporter:  shane         |                        Owner:
                Type:  enhancement   |  jinmei
            Priority:  very high     |                       Status:
           Component:  bind-ctl      |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130319
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  4             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:32 muks]:

 > I have unified the exceptions to check them in a single `except` clause,
 > and have also updated the messages. Is this a reasonable solution?
 > I ask this because it's still possible for a socket error to occur due
 > to the environment (not just some condition at `b10-cmdctl`) and we may
 > want to handle such an exception.

 Specifically how can that happen?  If it's not related to the user
 account stuff (missing file, lack of permission, missing entry, etc)
 but is purely a network related problem, then it basically looks okay.
 Whether this one makes sense would also depend on how it can happen:
 {{{#!python
             self._print("Please check the logs of b10-cmdctl, there may "
                         "have been a problem accepting SSL connections.")
 }}}
 When this happens would something be actually logged in b10-cmdctl?

 Also, I thought we discussed this before, but possibly repeating
 myself, this double-space after colon is awkward.

 {{{#!diff
 +                'Error while sending login information:  test error')
 }}}

 > > BTW, bindctl unit tests now fail.  I suspect it was because of the
 > > latest changes.
 > >
 > > (and I couldn't confirm whether distcheck now passes).
 >
 > If it fails again, please can you include how this failed for you? I do
 > run `make check` (and in this bug, `make distcheck` after your recent
 > comment) before putting a bug to review. It did not fail for me, so the
 > failure message would be helpful.

 Hmm, after a complete clean and rebuild, unit tests now passed.  Maybe
 it was due to some intermediate leftover.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2641#comment:33>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development