Package: inadyn
Version: 1.99.3-1
Severity: important

Dear Maintainer,

   * What led up to the situation?
I upgraded inadyn to 1.99.3-1.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I invoked inadyn as I have done for a while, now:
sudo /usr/bin/inadyn --system defa...@no-ip.com --username m...@ema.il -p 
XXXXXXX --alias myhostali.as --period 60 --forced-update 3600000 --verbose 1

   * What was the outcome of this action?
--verbose 3 returns:
<quote>

Wed Aug  7 01:16:43 2013: Inadyn version 1.99.3 -- Dynamic DNS update client.
Wed Aug  7 01:16:43 2013: Cached IP# XXX.XXX.XXX.XXX from previous invocation.
Wed Aug  7 01:16:43 2013: Checking for IP# change, connecting to 
ip1.dynupdate.no-ip.com(8.23.224.121)
Wed Aug  7 01:16:43 2013: Querying DDNS server for my public IP#:
Wed Aug  7 01:16:43 2013: GET / HTTP/1.0
Host: ip1.dynupdate.no-ip.com
User-Agent: inadyn/1.99.3 troglo...@gmail.com


Wed Aug  7 01:16:43 2013: IP server response:
Wed Aug  7 01:16:43 2013: HTTP/1.1 200 OK
Server: nginx
Date: Tue, 06 Aug 2013 23:16:43 GMT
Content-Type: text/html
Connection: close

XXX.XXX.XXX.XXX
Wed Aug  7 01:16:43 2013: Current public IP# XXX.XXX.XXX.XXX
Wed Aug  7 01:16:43 2013: Update needed for alias myhostali.as, new IP# 
XXX.XXX.XXX.XXX
Wed Aug  7 01:16:43 2013: Sending IP# update to DDNS server, connecting to 
dynupdate.no-ip.com(8.23.224.120)
Wed Aug  7 01:16:43 2013: Sending alias table update to DDNS server:
Wed Aug  7 01:16:43 2013: GET 
/nic/update?hostname=myhostali.as&myip=XXX.XXX.XXX.XXX HTTP/1.0
Host: dynupdate.no-ip.com
Authorization: Basic <unprintable stuff>
User-Agent: inadyn/1.99.3 troglo...@gmail.com


Wed Aug  7 01:16:43 2013: Fatal error in DDNS server response:
Wed Aug  7 01:16:43 2013: [401 Unauthorized] This service requires basic http 
authentication
Wed Aug  7 01:16:43 2013: DDNS server response:
Wed Aug  7 01:16:43 2013: HTTP/1.0 401 Unauthorized
Date: Tue, 06 Aug 2013 23:16:43 GMT
Server: Apache/2
Content-Location: update.php
Vary: negotiate
TCN: choice
WWW-Authenticate: Basic realm="dynupdate.no-ip.com"
Content-Length: 47
Connection: close
Content-Type: text/html; charset=UTF-8

This service requires basic http authentication
Wed Aug  7 01:16:43 2013: Error response from DDNS server, exiting!
Wed Aug  7 01:16:43 2013: Failed starting daemon: RC_DYNDNS_RSP_NOTOK

</quote>
(exit with return code 72)

   * What outcome did you expect instead?
I expected the IP update to work as it did in the previous version.

Downgrading back to the wheezy version fixes the problem.
It also makes the "Authorization" header in the IP update request contain 
proper content after "Basic ".
The previous version (?1.99.2?) did not suffer from this problem.

  --Reinhold

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-proposed-updates'), (500, 
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages inadyn depends on:
ii  adduser  3.113+nmu3
ii  libc6    2.17-7

inadyn recommends no packages.

inadyn suggests no packages.

-- Configuration Files:
/etc/inadyn.conf [Errno 13] Keine Berechtigung: u'/etc/inadyn.conf'

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to