Opened 8 years ago

Closed 8 years ago

#1802 closed task (complete)

identify whether an in-memory zone is NSEC-signed at load time

Reported by: jinmei Owned by: vorner
Priority: medium Milestone: Sprint-20120515
Component: data source Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket: in-memory NSEC
Estimated Difficulty: 3 Add Hours to Ticket: 0
Total Hours: 1.79 Internal?: no

Description

there can be several possible ways for that. I guess one practical
way is to consider a zone NSEC-signed iff the origin node has an NSEC
RRset.

In this task we'd also update the successful wildcard match case of
find() so it sets the RESULT_NSEC_SIGNED flag of the result context.
We can use this to test the feature.

Subtickets

Change History (7)

comment:1 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 3

comment:2 Changed 8 years ago by jelte

  • Milestone changed from New Tasks to Sprint-20120515

comment:3 Changed 8 years ago by vorner

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

comment:4 Changed 8 years ago by vorner

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

It should be ready for review.

comment:5 Changed 8 years ago by jelte

  • Owner changed from UnAssigned to jelte

comment:6 Changed 8 years ago by jelte

  • Owner changed from jelte to vorner

Looks good, please merge

comment:7 Changed 8 years ago by vorner

  • Resolution set to complete
  • Status changed from reviewing to closed
  • Total Hours changed from 0 to 1.79

Thank you, closing.

Note: See TracTickets for help on using tickets.