BIND 10 #3237: user_check library must load even user registry missing; doc needed (was: user_check library should load even if there is no user registry file)

BIND 10 Development do-not-reply at isc.org
Thu Nov 14 11:34:23 UTC 2013


#3237: user_check library must load even user registry missing; doc needed
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  medium        |                    Milestone:  DHCP
           Component:  Unclassified  |  Outstanding Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DHCP          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Description changed by tomek:

Old description:

> The library should load, even if there's not /tmp/user_chk_registry.txt
> file.
>
> From the setup perspective it would be reasonable to just fall back to
> normal operation if the file is missing. From the security persective, it
> would probably be good to treat all packets as unregistered users.

New description:

 The library should load, even if there's not /tmp/user_chk_registry.txt
 file.

 From the setup perspective it would be reasonable to just fall back to
 normal operation if the file is missing. From the security persective, it
 would probably be good to treat all packets as unregistered users.

 I don't have any preference. Whatever the choice is, it should be well
 documented.

 For now that library will act as a substitute for classification. Once
 proper classification is done, it will be relieved of doing that function.
 It is unclear what we'll do next with it.

 In any case, this is our first lib, so it will be used as example. Hence
 we need easy to read introdution for it. It should probably be part of the
 hooks documentation.

--

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


More information about the bind10-tickets mailing list