Opened 9 years ago

Closed 8 years ago

#767 closed task (complete)

ACLS: define syntax

Reported by: stephen Owned by: UnAssigned
Priority: medium Milestone: Sprint-20110712
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

In order to define an ACL, it must be specified. This task is to determine exactly how information about an ACL can be represented and entered into the system. Research is encouraged - perhaps look at programs such as ipfilter?

Subtickets

Change History (5)

comment:1 Changed 9 years ago by stephen

  • Defect Severity set to N/A
  • Feature Depending on Ticket set to ACL
  • Milestone changed from Year 3 Task Backlog to Sprint-20110531
  • Sub-Project set to DNS

comment:2 Changed 9 years ago by vorner

  • Owner set to vorner
  • Status changed from new to accepted

comment:3 Changed 9 years ago by vorner

  • Owner changed from vorner to UnAssigned
  • Status changed from accepted to reviewing

The current proposal is at AclSyntax. I'm going to send an email to dev list so more people can have a look and discuss if this is a good idea.

comment:4 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 5

comment:5 Changed 8 years ago by vorner

  • Resolution set to complete
  • Status changed from reviewing to closed

As it has been implemented, this can be closed, even if it didn't go trough a formal review (which is hard for non-standard/design tickets anyway).

Note: See TracTickets for help on using tickets.