Bug #2068
dyndns update (rfc 2136) error when more as one entry
| Status: | Resolved | Start date: | 12/29/2011 | |
|---|---|---|---|---|
| Priority: | Urgent | Due date: | ||
| Assignee: | - | % Done: | 100% |
|
| Category: | DynDNS | |||
| Target version: | - | |||
| 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
Associated revisions
Fix multiple keys in a file for RFC2136 dyndns updates. Fixes #2068
Fix multiple keys in a file for RFC2136 dyndns updates. Fixes #2068
History
#1
Updated by Jim P over 1 year ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 8ec0a8bc10c094151be41024c6fbea3defeb5a48.
#2
Updated by Jim P over 1 year ago
Applied in changeset 980c1c6da3ec989c1cce72a9716ac56f912e4173.
#3
Updated by Chris Buechler about 1 year ago
- Status changed from Feedback to Resolved