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-20130305
         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
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => jinmei


Comment:

 Replying to [comment:24 jinmei]:
 > Replying to [comment:23 muks]:
 > > Hi Jinmei
 >
 > > > {{{#!python
 > > >         except ssl.SSLError as err:
 > > >             self._print("SSL error while sending login information:
 ", err)
 > > >             if err.errno == ssl.SSL_ERROR_EOF:
 > > >                 self.__print_check_ssl_msg()
 > > >         except socket.error as err:
 > > >             self._print("Socket error while sending login
 information: ", err)
 > > >             # An SSL setup error can also bubble up as a plain
 CONNRESET...
 > > >             # (on some systems it usually does)
 > > >             if err.errno == errno.ECONNRESET:
 > > >                 self.__print_check_ssl_msg()
 > > >             pass
 > > > }}}
 > >
 > > If such exceptions are raised (due to any environmental reasons),
 > > they'll go unhandled. So maybe there's no harm in leaving them there.
 >
 > Could you also explain this?

 The method's description has been updated for it.

 > > Looks like so, but I now wonder why the socket or SSL error doesn't
 > > happen when, e.g., the account file exists but lacks permission.
 >
 > And, depending on the answer for it, the message printed by
 > `__print_check_ssl_msg` shouldn't make sense any more.

 The message here has also been updated. It still asks to check b10-cmdctl
 logs (as something may be logged in this case), but doesn't say anything
 about permissions anymore.

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