Bug #2068: dyndns update (rfc 2136) error when more as one entry - pfSense - pfSense bugtracker

Actions

Copy link

Bug #2068

closed

dyndns update (rfc 2136) error when more as one entry

Added by Andreas Huser almost 13 years ago. Updated over 12 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

Category:

Dynamic DNS

Target version:

Start date:

12/29/2011

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Affected Version:

2.0.1

Affected Architecture:

i386

Description

when i create a entry at service dnydns rfc2136. The first entry in .private file are fine

cd /var/etc/
cat K0drmr.cu.xxx.+157+00000.private

Private-key-format: v1.2
Algorithm: 157 (HMAC)
Key: VhgheA83hWmrsw7BKxRdS6qerrL1b0oasNFbswefDAiZyqJeb3qwer+soJvjNquURA9Sj5fsdfV6L6+XElk3M6gPA==

when i make a second entry at service dnydns rfc2136. The service generate two entrys at the .private file

cd /var/etc/
cat K1drmr.cu.xxx.+157+00000.private

Private-key-format: v1.2
Algorithm: 157 (HMAC)
Key: VhgheA83hWmrsw7BKxRdS6qerrL1b0oasNFbswefDAiZyqJeb3qwer+soJvjNquURA9Sj5fsdfV6L6+XElk3M6gPA==
Private-key-format: v1.2
Algorithm: 157 (HMAC)
Key: VhgheA83hWmrsw7BKxRdS6qerrL1b0oasNFbswefDAiZyqJeb3qwer+soJvjNquURA9Sj5fsdfV6L6+XElk3M6gPA==

etc. etc.

the error was then : could not read key from K1drmr.cu.xxxx.+157+00000.private: private key is invalid