Opened 9 years ago

Closed 8 years ago

#766 closed task (wontfix)

ACLS: define properties ACLs should check

Reported by: stephen Owned by: jelte
Priority: medium Milestone: Sprint-20110628
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: ACL
Estimated Difficulty: 5.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Research (possibly via user stories) and come up with a list of properties that any ACL code should check in order to determine if access is allowed. These might include IP Address, TSIG, message contents.

Subtickets

Change History (7)

comment:1 Changed 9 years ago by stephen

  • Defect Severity set to N/A
  • Milestone changed from Year 3 Task Backlog to Sprint-DHCP-20110517
  • Sub-Project set to DNS

comment:2 Changed 9 years ago by stephen

  • Feature Depending on Ticket set to ACL

comment:3 Changed 9 years ago by stephen

  • Milestone changed from Sprint-DHCP-20110517 to Sprint-20110531

comment:4 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 5

comment:5 Changed 9 years ago by stephen

  • Owner set to stephen
  • Status changed from new to assigned

comment:6 Changed 9 years ago by stephen

  • Owner changed from stephen to jelte

comment:7 Changed 8 years ago by jelte

  • Resolution set to wontfix
  • Status changed from assigned to closed

This kind of got overtaken by events, and most if not all of the properties (but not the checks) are in the code already (see acl/dns.h). If it turns out we need more or less, we can update them later.

Note: See TracTickets for help on using tickets.