Opened 9 years ago

Closed 6 years ago

#975 closed defect (wontfix)

Non-primitive static object `server_common::keyring` is candidate for intialization problems

Reported by: vorner Owned by:
Priority: medium Milestone: DNS Outstanding Tasks
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

As noted in #931, this might be problematic if one non-primitive static object uses another one for it's initialization, as the second one might be yet unitialized. This should be replaced by some function returning the instance or something to prevent such problems.

Subtickets

Change History (5)

comment:1 Changed 9 years ago by shane

  • Defect Severity changed from N/A to Medium
  • Milestone New Tasks deleted

comment:2 Changed 6 years ago by shane

  • Milestone set to Sprint-20131015
  • Summary changed from Non-primitive static object `server_common::keyring` is candidate for intialization problems to [kean] Non-primitive static object `server_common::keyring` is candidate for intialization problems

comment:3 Changed 6 years ago by kean

  • Summary changed from [kean] Non-primitive static object `server_common::keyring` is candidate for intialization problems to Non-primitive static object `server_common::keyring` is candidate for intialization problems

comment:4 Changed 6 years ago by stephen

  • Milestone changed from bind10-1.2-release-freeze to DNS Outstanding Tasks

comment:5 Changed 6 years ago by tomek

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

DNS and BIND10 framework is outside of scope for Kea project.
The corresponding code has been removed from Kea git repository.
If you want to follow up on DNS or former BIND10 issues, see
http://bundy-dns.de project.

Closing ticket.

Note: See TracTickets for help on using tickets.