[vdr] Re: RE : [ANNOUNCE] vdr-wapd-0.0.5

[Thomas Heiligenmann <thomas@heiligenmann.de>]

On Tue, 15 Jun 2004, Olivier Jacques wrote:

> Hello Thomas,
>
> Thanks for this wonderful plugin! Now that 0.0.5b brings authentication,
> nothing can stop us from using it!
> Well except that I have some issues :D
> I was able to get (once) the login and password - but didn't passed this
> point.
>

I guess I know why ;-) There's another bug I have to fix in the Base64
decoding. Have you tried a _longer_ login name and password (> 4 chars)?

> For a period of time, vdr even segfaults each time I try to access wapd.
> Here is the backtrace:
> #0  cWapAccess::Acceptable(char*) (this=0x402ffd80, Auth=0x0) at
> access.c:70
> 70        *p++ = 0;
> (gdb) bt
> #0  cWapAccess::Acceptable(char*) (this=0x402ffd80, Auth=0x0) at
> access.c:70
> #1  0x402f9abe in cWapServer::Action() (this=0x81cc528) at server.c:966
> #2  0x080d62db in cThread::StartThread(cThread*) (Thread=0x81cc528) at
> thread.c:189
> #3  0x40041e51 in pthread_start_thread () from /lib/libpthread.so.0
> Current language:  auto; currently c++
>
> => And I got this in the log:
> Jun 15 23:45:11 vdr vdr[18440]: WAPD: connect from 192.168.0.1, port
> 1519 - accepted
>

Possibly related to the bug mentioned about. I'll have a closer look at
that.

> => Looks like the TCP socket is still opened (TIME_WAIT)
> root@vdr:/usr/local/src/VDR# netstat
> Active Internet connections (w/o servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address
> State
> tcp        0      0 .:ssh                   192.168.0.1:1379
> ESTABLISHED
> tcp        0    216 .:ssh                   192.168.0.1:1073
> ESTABLISHED
> tcp        0      0 .:8888                  192.168.0.1:1541
> TIME_WAIT
> tcp        0      0 .:8888                  192.168.0.1:1540
> TIME_WAIT
> tcp        0      0 .:netbios-ssn           192.168.0.1:1092
> ESTABLISHED
> tcp        0      0 .:1175                  192.168.0.1:445
> ESTABLISHED
> Active UNIX domain sockets (w/o servers)
> Proto RefCnt Flags       Type       State         I-Node Path
> unix  8      [ ]         DGRAM                    244    /dev/log
> unix  2      [ ]         DGRAM                    3227849
> unix  2      [ ]         DGRAM                    2736789
> unix  2      [ ]         DGRAM                    2736622
> unix  2      [ ]         DGRAM                    2584481
> unix  3      [ ]         STREAM     CONNECTED     1178   /dev/lircd
> unix  3      [ ]         STREAM     CONNECTED     1177
> unix  2      [ ]         DGRAM                    554
> unix  2      [ ]         DGRAM                    293
> root@vdr:/usr/local/src/VDR#
>

Do these disappear after a certain timeout or are there some vdr processes
still running after the segfault?

> Note: I got some warnings at compile time, but I'm sure that this
> doesn't matter:
> g++: -lcrypt: linker input file unused because linking not done
>

That could be different for the various distributions. Is there a
libcrypt.so or alike in your glibc installed?

Thomas