Project

General

Profile

Bug #9470

unbound remotecontrol.conf not rewritten when the file is empty

Added by Jim Pingle 8 months ago. Updated 7 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
DNS Resolver
Target version:
Start date:
04/11/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:
All

Description

If /var/unbound/remotecontrol.conf is empty, it will not be rewritten. The code to write the file checks that the file exists, but not its size.

https://forum.netgate.com/topic/142446/should-unbound-control-work-by-default/2

Associated revisions

Revision 4b70a200 (diff)
Added by Jim Pingle 8 months ago

Rewrite unbound remotecontrol.conf when it is empty. Fixes #9470

Revision 6cb5a937 (diff)
Added by Jim Pingle 7 months ago

Rewrite unbound remotecontrol.conf when it is empty. Fixes #9470

(cherry picked from commit 4b70a2006e6afb7813344eec8cafb8570e67256b)

History

#1 Updated by Jim Pingle 8 months ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#2 Updated by Chris Linstruth 8 months ago

Looks good here. cp /dev/null /var/etc/unbound.conf then a save of the unbound configuration populated the file.

#3 Updated by Jim Pingle 8 months ago

  • Status changed from Feedback to Resolved

#4 Updated by Jim Pingle 7 months ago

  • Target version changed from 2.5.0 to 2.4.4-p3

#5 Updated by Jim Pingle 7 months ago

  • Status changed from Resolved to Feedback

#6 Updated by Chris Linstruth 7 months ago

2.4.4-p3 Looks good:

cp /dev/null /var/unbound/remotecontrol.conf
Save unbound configuration
/var/unbound/remotecontrol.conf populated

#7 Updated by Jim Pingle 7 months ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF