Bug#1067405: ERROR: permission denied for function pg_ls_waldir

[Skibbi]

Package: prometheus-postgres-exporter
Version: 0.15.0-2
Severity: normal

Dear Maintainer,

Despinte executing sql statements in
/usr/share/doc/prometheus-postgres-exporter/README.Debian I'm observing
following errors in the porstresql (16) log files:

2024-03-21 06:52:38.383 UTC [56394] prometheus@postgres ERROR:  permission 
denied for function pg_ls_waldir
2024-03-21 06:52:38.383 UTC [56394] prometheus@postgres STATEMENT:
SELECT
COUNT(*) AS segments,
SUM(size) AS size
FROM pg_ls_waldir()
WHERE name ~ '^[0-9A-F]{24}$'

I think additional permissions are needed for prometheus sql user,
however I'm unsure what is the best and safest way to grant them to the
monitoring user.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages prometheus-postgres-exporter depends on:
ii  adduser  3.137
ii  init-system-helpers  1.66
ii  libc62.37-15.1
ii  systemd-sysv 255.4-1+b1

prometheus-postgres-exporter recommends no packages.

prometheus-postgres-exporter suggests no packages.

Bug#1055275: dhcpcd: Version 10.0.4 fails to fork in the background

[Skibbi]

Package: dhcpcd
Version: 1:10.0.4-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,
I'm using dhcpcd on my raspbian os and it was updated on 31 October to 
latest version 10.0.4. Since then, my raspberrypi started loosing network 
every 24h. After some investigation I found out that my dhcpcd daemon is 
not working in the background.

I believe this is related to this bug:
https://github.com/NetworkConfiguration/dhcpcd/issues/260

It would be nice to downgrade the package version until upstream bug is
fixed.

Best regards

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dhcpcd depends on:
ii  dhcpcd-base1:10.0.4-1
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.08-3

Versions of packages dhcpcd recommends:
ii  wpasupplicant  2:2.10-15

Versions of packages dhcpcd suggests:
pn  dhcpcd-gtk  

-- no debconf information

Bug#1054354: netdata: Anomaly detection (ML)

[Skibbi]

Package: netdata
Version: 1.43.0-1
Severity: wishlist

Dear Maintainer,

Are there any issues to include ML (machine learning) anomaly detection
in netdata debian build? It would be nice to have this feature enabled for
debian package.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages netdata depends on:
ii  netdata-core  1.43.0-1
ii  netdata-plugins-bash  1.43.0-1
ii  netdata-web   1.43.0-1

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.43.0-1

netdata suggests no packages.

-- no debconf information

Bug#1054351: netdata: Missing directory in /etc/netdata

[Skibbi]

Package: netdata
Version: 1.43.0-1
Severity: minor

Dear Maintainer,

When starting netdata following error appears in the logs:
2023-10-22 13:45:16: netdata ERROR : PLUGINSD : cannot open plugins directory 
'/etc/netdata/custom-plugins.d' (errno 2, No such file or directory)

I think this directory should be created automatically when netdata is
installed.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages netdata depends on:
ii  netdata-core  1.43.0-1
ii  netdata-plugins-bash  1.43.0-1
ii  netdata-web   1.43.0-1

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.43.0-1

netdata suggests no packages.

-- no debconf information

Bug#1054349: netdata: debugfs plugin requires setuid flag set to work properly

[Skibbi]

Package: netdata
Version: 1.43.0-1
Severity: normal

Dear Maintainer,
I've got some time to check latest netdata package and I found several
issues. One is related to debugfs plugin. Here is the excerpt from logs:

2023-10-22 12:56:07: debugfs.plugin ERROR : debugfs.plugin : debugfs.plugin 
should either run as root (now running with uid 998, euid 998) or have special 
capabilities. Without these, debugfs.plugin cannot access /sys/kernel/debug. To 
enable capabilities run: sudo setcap cap_dac_read_search,cap_sys_ptrace+ep 
/usr/lib/netdata/plugins.d/debugfs.plugin; To enable setuid to root run: sudo 
chown root:netdata /usr/lib/netdata/plugins.d/debugfs.plugin; sudo chmod 4750 
/usr/lib/netdata/plugins.d/debugfs.plugin;  (errno 13, Permission denied)

I followed the suggestion and added setuid flag to the plugin binary.
After restart the issue is gone. So, perhaps setuid should be set as
defaukt for debugfs plugin?

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages netdata depends on:
ii  netdata-core  1.43.0-1
ii  netdata-plugins-bash  1.43.0-1
ii  netdata-web   1.43.0-1

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.43.0-1

netdata suggests no packages.

-- no debconf information

Bug#1031619: neofetch seems unmaintained, replace with hyfetch

[Skibbi]

Package: neofetch
Version: 7.1.0-4
Severity: wishlist

Dear Maintainer,
It seems neofetch is unmaintained. But there is a fork, that continues
the work of the original developer:
https://github.com/hykilpikonna/hyfetch

Please consider replacing neofetch with hyfetch.

Best regards

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint: flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

neofetch depends on no packages.

Versions of packages neofetch recommends:
pn  caca-utils
pn  chafa 
pn  imagemagick   
pn  jp2a  
pn  libsixel-bin  
ii  pciutils  1:3.9.0-4
pn  w3m-img   

neofetch suggests no packages.

-- no debconf information

Bug#1011051: libssl3: upgrade to libssl3 broke my dovecot setup

[Skibbi]

Package: libssl3
Version: 3.0.3-3
Severity: grave
Justification: renders package unusable

After upgrading to libssl3 broke my dovecot setup with following error:
imap-login: Error: Failed to initialize SSL server context: Can't load SSL 
certificate (ssl_cert setting): error:25066067:DSO support 
routines:dlfcn_load:could not load the shared library: 
filename(libproviders.so): libproviders.so: cannot open shared object file: No 
such file or directory, error:25070067:DSO support routines:DSO_load:could not 
load the shared library, error:0E07506E:configuration file 
routines:module_load_dso:error loading dso: module=providers, path=providers, 
error:0E076071:configuration file routines:module_run:unknown module name: 
module=providers

Commenting out providers = provider_sect in /etc/ssl/openssl.cnf fixes the 
issue.
I guess this is closely related to the following debian bug: #918727

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.17.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libssl3 depends on:
ii  libc6  2.33-7

libssl3 recommends no packages.

libssl3 suggests no packages.

-- no debconf information

Bug#878890: netdata: Debian pachaged netdata fails to detect disks/partitions correctly

[Skibbi]

Hi,
That was it! After commenting out ReadOnlyDirectories=/ netdata started
reporting correct disks/partitions. I guess this issue should be discussed
on netdata github issue tracker.

Thanks for pointig this out.

2017-10-24 14:28 GMT+02:00 Lennart Weller :

> I assume it has something to do with our strict ReadOnly policy applied by
> systemd.
> Try changing the netdata service file (/lib/systemd/system/netdata.service)
> to be more lenient.
> e.g. Change ReadOnlyDirectories=/ to ReadWriteDirectories=/ or remove the
> lines completely. Don't forget to reload the service file after a change
>
> I have honestly no idea why the daemon would need write permissions on
> those directories but it's worth a try as there were some odd cases before.
> If that doesn't help you can remove some of the other security related
> lines and check if it helps.
>
> October 17, 2017 3:48 PM, "Skibbi"  wrote:
> [...]
> > Manually installed netdata (from binaries) displays following partitions
> under
> > Disks menu:
> > sda - i/o stats
> > / - disk space and inodes count
> > /dev - disk space and inodes count
> > /dev/shm - disk space and inodes count
> > /run - disk space and inodes count
> > /run/lock - disk space and inodes count
> >
> > Debian packaged netdata displays completely different partition
> configuration:
> > sda - i/o stats
> > /tmp - disk space and inodes count
> > /var - disk space and inodes count
> > /var/tmp - disk space and inodes count
> >
> > Debian packaged netdata unfortunately fails to detect correctly disks on
> my
> > servers therefore monitoring them is not very reliable and I haven't
> found a way
> > to fix the partitions manually in netdata config.
>

Bug#878890: netdata: Debian pachaged netdata fails to detect disks/partitions correctly

[Skibbi]

Package: netdata
Version: 1.8.0+dfsg-1
Severity: normal

Dear Maintainer,
I've been trying to setup netdata monitoring on several debian servers.
Unfortunately I found out that debian packaged netdata behaves differently 
than manually installed netdata from 
https://github.com/firehol/netdata/wiki/Installation.

I've created a virtual machine and installed latest netdata with default config.
Here are partition details of the virtual machine:

~# cat /proc/self/mountinfo
17 22 0:17 / /sys rw,nosuid,nodev,noexec,relatime shared:7 - sysfs sysfs rw
18 22 0:4 / /proc rw,nosuid,nodev,noexec,relatime shared:12 - proc proc rw
19 22 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs udev 
rw,size=1005780k,nr_inodes=251445,mode=755
20 19 0:18 / /dev/pts rw,nosuid,noexec,relatime shared:3 - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
21 22 0:19 / /run rw,nosuid,noexec,relatime shared:5 - tmpfs tmpfs 
rw,size=203384k,mode=755
22 0 8:1 / / rw,relatime shared:1 - ext4 /dev/sda1 
rw,errors=remount-ro,data=ordered
23 17 0:16 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - 
securityfs securityfs rw
24 19 0:20 / /dev/shm rw,nosuid,nodev shared:4 - tmpfs tmpfs rw
25 21 0:21 / /run/lock rw,nosuid,nodev,noexec,relatime shared:6 - tmpfs tmpfs 
rw,size=5120k
26 17 0:22 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:9 - tmpfs tmpfs 
ro,mode=755
27 26 0:23 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:10 - 
cgroup cgroup 
rw,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd
28 17 0:24 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:11 - pstore 
pstore rw
29 26 0:25 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:13 - cgroup cgroup rw,cpu,cpuacct
30 26 0:26 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:14 - 
cgroup cgroup rw,blkio
31 26 0:27 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:15 - cgroup cgroup rw,net_cls,net_prio
32 26 0:28 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,perf_event
33 26 0:29 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:17 - 
cgroup cgroup rw,pids
34 26 0:30 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:18 - 
cgroup cgroup rw,memory
35 26 0:31 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:19 - 
cgroup cgroup rw,cpuset
36 26 0:32 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:20 - 
cgroup cgroup rw,devices
37 26 0:33 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:21 - 
cgroup cgroup rw,freezer
38 18 0:34 / /proc/sys/fs/binfmt_misc rw,relatime shared:22 - autofs systemd-1 
rw,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=11032
40 17 0:7 / /sys/kernel/debug rw,relatime shared:23 - debugfs debugfs rw
39 19 0:35 / /dev/hugepages rw,relatime shared:24 - hugetlbfs hugetlbfs rw
41 19 0:15 / /dev/mqueue rw,relatime shared:25 - mqueue mqueue rw
188 38 0:39 / /proc/sys/fs/binfmt_misc rw,relatime shared:107 - binfmt_misc 
binfmt_misc rw
221 17 0:41 / /sys/fs/fuse/connections rw,relatime shared:144 - fusectl fusectl 
rw
179 21 0:40 / /run/user/1000 rw,nosuid,nodev,relatime shared:140 - tmpfs tmpfs 
rw,size=203380k,mode=700,uid=1000,gid=1000

Manually installed netdata (from binaries) displays following partitions under 
Disks menu:
sda   - i/o stats
/ - disk space and inodes count
/dev  - disk space and inodes count
/dev/shm  - disk space and inodes count
/run  - disk space and inodes count
/run/lock - disk space and inodes count

Debian packaged netdata displays completely different partition configuration:
sda   - i/o stats
/tmp  - disk space and inodes count
/var  - disk space and inodes count
/var/tmp  - disk space and inodes count

Debian packaged netdata unfortunately fails to detect correctly disks on my 
servers therefore monitoring them is not very reliable and I haven't found a way
to fix the partitions manually in netdata config.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages netdata depends on:
ii  adduser  3.116
ii  init-system-helpers  1.50
ii  libc62.24-17
ii  libcap2-bin  1:2.25-1.1
ii  libuuid1 2.30.2-0.1
ii  lsb-base 9.20170808
ii  netdata-data 1.8.0+dfsg-1
ii  python   2.7.14-1
ii  python-urllib3   1.21.1-1
ii  python-yaml  3.12-1+b1
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages netdata recommends:
ii  curl7.55.1-1
pn  fping   
pn  nodejs  

netdata suggests no packages.

-- Configuration Files:
/etc/netdata/netdata.conf changed [not included]

Bug#858587: fail2ban fails to ban postfix-sasl failed attempts

[Skibbi]

Package: fail2ban
Version: 0.9.6-1
Severity: normal

Dear Maintainer,
There is an issue when enabling postfix-sasl jail in fail2ban.
When there are multiple failed login attempts fail2ban executes following 
command:
iptables -w -I INPUT -p tcp -m multiport --dports 
smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
Unfortunaltely in debian /etc/services does not contain imap3 service anymore
which causes fail2ban to fail with this error:
iptables v1.6.0: invalid port/service `imap3' specified

This is not an issue with fail2ban itself, but rather netbase. Not sure why in 
latest 5.4
version of the package imap3 was removed.

Regards

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.47
ii  lsb-base 9.20161125
pn  python3:any  

Versions of packages fail2ban recommends:
ii  iptables   1.6.0+snapshot20161117-5
ii  python 2.7.13-2
pn  python3-pyinotify  
pn  python3-systemd
ii  whois  5.2.15

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20160123cvs-3
pn  monit
ii  rsyslog [system-log-daemon]  8.24.0-1

-- no debconf information

Bug#851852: netdata: postfix/postdrop Read-only filesystem

[Skibbi]

Package: netdata
Version: 1.4.0+dfsg-3
Severity: normal

Dear Maintainer,
After installing netdata system logs are flooded with following errors:
jan 19 11:40:06 server postfix/postdrop[11512]: warning: mail_queue_enter: 
create file maildrop/770542.11512: Read-only file system

It seems that netdata runs postdrop as netdata user so I've tried to add 
netdtata to postdrop group. Unfortunately it didn't help.
I'm not sure why I'm getting those Read-only filesystem errors. Issue is 
reproducible on two different servers - both have postfix
configured as MTA.

-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages netdata depends on:
ii  adduser  3.115
ii  fonts-font-awesome   4.7.0~dfsg-1
ii  init-system-helpers  1.47
ii  libc62.24-9
ii  libcap2-bin  1:2.25-1
ii  libjs-bootstrap  3.3.7+dfsg-2
ii  libjs-d3 3.5.17-1
ii  libjs-jquery 3.1.1-2
ii  libjs-raphael2.1.0-1
ii  libuuid1 2.29-1
ii  lsb-base 9.20161125
ii  netdata-data 1.4.0+dfsg-3
ii  python   2.7.13-1
ii  zlib1g   1:1.2.8.dfsg-4

netdata recommends no packages.

netdata suggests no packages.

-- no debconf information

Bug#826097: liquidprompt: Default debian theme is incompatible with 1.10 version

[Skibbi]

Package: liquidprompt
Version: 1.10-1
Severity: normal

Dear Maintainer,
After upgrading liquidprompt to latest 1.10 version I started getting following 
warnings:
liquidprompt: LP_COLORMAP_x variables are deprecated. Update your theme to use 
LP_COLORMAP array.

It seems default debian theme still uses LP_COLORMAP_x variables instead of 
array.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

liquidprompt depends on no packages.

liquidprompt recommends no packages.

Versions of packages liquidprompt suggests:
ii  acpi1.7-1
ii  lm-sensors  1:3.4.0-3

-- no debconf information

Bug#767255: fail2ban: Typo in default jail.conf

[Skibbi]

Package: fail2ban
Version: 0.9.1-1
Severity: minor

Dear Maintainer,
There is a typo in default jail.conf. logpath for [apache-shellshock] jail
is defined as $(apache_error_log)s which renders jail unusable.
I'm attaching fixed config file.

Regards

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.21
ii  lsb-base 4.1+Debian13+nmu1
ii  python3  3.4.2-1
pn  python3:any  

Versions of packages fail2ban recommends:
ii  iptables   1.4.21-2
pn  python3-pyinotify  
ii  whois  5.2.1

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20140825cvs-1
pn  python3-systemd  
ii  rsyslog [system-log-daemon]  8.4.2-1

-- Configuration Files:
/etc/fail2ban/action.d/iptables-blocktype.conf
b322783b061a2e3d4412fa2f523fc69c [Errno 2] Nie ma takiego pliku ani
katalogu: u'/etc/fail2ban/action.d/iptables-blocktype.conf
b322783b061a2e3d4412fa2f523fc69c'
/etc/fail2ban/jail.conf changed:
[INCLUDES]
before = paths-debian.conf
[DEFAULT]
ignoreip = 127.0.0.1/8
ignorecommand =
bantime  = 600
findtime  = 600
maxretry = 5
backend = auto
usedns = warn
logencoding = auto
enabled = false
filter = %(__name__)s
destemail = root@localhost
sender = root@localhost
mta = sendmail
protocol = tcp
chain = INPUT
port = 0:65535
banaction = iptables-multiport
action_ = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s",
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
action_mw = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s",
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
%(mta)s-whois[name=%(__name__)s, dest="%(destemail)s",
protocol="%(protocol)s", chain="%(chain)s"]
action_mwl = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s",
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
 %(mta)s-whois-lines[name=%(__name__)s, dest="%(destemail)s",
logpath=%(logpath)s, chain="%(chain)s"]
action_xarf = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s",
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
 xarf-login-attack[service=%(__name__)s, sender="%(sender)s",
logpath=%(logpath)s, port="%(port)s"]
action_blocklist_de  = blocklist_de[email="%(sender)s", service=%(filter)s,
apikey="%(blocklist_de_apikey)s"]
action_badips = badips.py[category="%(name)s", banaction="%(banaction)s"]
action = %(action_)s
[sshd]
port= ssh
logpath = %(sshd_log)s
[sshd-ddos]
port= ssh
logpath = %(sshd_log)s
[dropbear]
port = ssh
logpath  = %(dropbear_log)s
[selinux-ssh]
port = ssh
logpath  = %(auditd_log)s
maxretry = 5
[apache-auth]
port = http,https
logpath  = %(apache_error_log)s
[apache-badbots]
port = http,https
logpath  = %(apache_access_log)s
bantime  = 172800
maxretry = 1
[apache-noscript]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 6
[apache-overflows]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-nohome]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-botsearch]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-modsecurity]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-shellshock]
port= http,https
logpath = %(apache_error_log)s
maxretry = 1
[nginx-http-auth]
ports   = http,https
logpath = %(nginx_error_log)s
[php-url-fopen]
port= http,https
logpath = %(nginx_access_log)s %(apache_access_log)s
[suhosin]
port= http,https
logpath = %(suhosin_log)s
[lighttpd-auth]
port= http,https
logpath = %(lighttpd_error_log)s
[roundcube-auth]
port = http,https
logpath  = /var/log/roundcube/userlogins
[openwebmail]
port = http,https
logpath  = /var/log/openwebmail.log
[horde]
port = http,https
logpath  = /var/log/horde/horde.log
[groupoffice]
port = http,https
logpath  = /home/groupoffice/log/info.log
[sogo-auth]
port = http,https
logpath  = /var/log/sogo/sogo.log
[tine20]
logpath  = /var/log/tine20/tine20.log
port = http,https
maxretry = 5
[guacamole]
port = http,https
logpath  = /var/log/tomcat*/catalina.out
[monit]
filter   = monit
port = 2812
logpath  = /var/log/monit
[webmin-auth]
port= 1
logpath = %(syslog_authpriv)s
[squid]
port =  80,443,3128,8080
logpath = /var/log/squid/access.log
[3proxy]
port= 3128
logpath = /var/log/3proxy.log
[proftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(proftpd_log)s
[pure-ftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(pureftpd_log)s
maxretry = 6
[gssftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(syslog_daemon)s
maxretry = 6
[wuftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(wuftpd_log)s
maxretry = 6
[vsftpd]

Bug#767252: fail2ban: Typo in default jail.conf

[Skibbi]

Package: fail2ban
Version: 0.9.1-1
Severity: minor

Dear Maintainer,
There is a typo in default jail.conf. logpath for [apache-shellshock] jail is 
defined as $(apache_error_log)s which renders jail unusable.
I'm attaching fixed config file.

Regards

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages fail2ban depends on:
ii  init-system-helpers  1.21
ii  lsb-base 4.1+Debian13+nmu1
ii  python3  3.4.2-1
pn  python3:any  

Versions of packages fail2ban recommends:
ii  iptables   1.4.21-2
pn  python3-pyinotify  
ii  whois  5.2.1

Versions of packages fail2ban suggests:
ii  bsd-mailx [mailx]8.1.2-0.20140825cvs-1
pn  python3-systemd  
ii  rsyslog [system-log-daemon]  8.4.2-1

-- Configuration Files:
/etc/fail2ban/action.d/iptables-blocktype.conf b322783b061a2e3d4412fa2f523fc69c 
[Errno 2] Nie ma takiego pliku ani katalogu: 
u'/etc/fail2ban/action.d/iptables-blocktype.conf 
b322783b061a2e3d4412fa2f523fc69c'
/etc/fail2ban/jail.conf changed:
[INCLUDES]
before = paths-debian.conf
[DEFAULT]
ignoreip = 127.0.0.1/8
ignorecommand =
bantime  = 600
findtime  = 600
maxretry = 5
backend = auto
usedns = warn
logencoding = auto
enabled = false
filter = %(__name__)s
destemail = root@localhost
sender = root@localhost
mta = sendmail
protocol = tcp
chain = INPUT
port = 0:65535
banaction = iptables-multiport
action_ = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s", 
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
action_mw = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s", 
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
%(mta)s-whois[name=%(__name__)s, dest="%(destemail)s", 
protocol="%(protocol)s", chain="%(chain)s"]
action_mwl = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s", 
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
 %(mta)s-whois-lines[name=%(__name__)s, dest="%(destemail)s", 
logpath=%(logpath)s, chain="%(chain)s"]
action_xarf = %(banaction)s[name=%(__name__)s, bantime="%(bantime)s", 
port="%(port)s", protocol="%(protocol)s", chain="%(chain)s"]
 xarf-login-attack[service=%(__name__)s, sender="%(sender)s", 
logpath=%(logpath)s, port="%(port)s"]
action_blocklist_de  = blocklist_de[email="%(sender)s", service=%(filter)s, 
apikey="%(blocklist_de_apikey)s"]
action_badips = badips.py[category="%(name)s", banaction="%(banaction)s"]
action = %(action_)s
[sshd]
port= ssh
logpath = %(sshd_log)s
[sshd-ddos]
port= ssh
logpath = %(sshd_log)s
[dropbear]
port = ssh
logpath  = %(dropbear_log)s
[selinux-ssh]
port = ssh
logpath  = %(auditd_log)s
maxretry = 5
[apache-auth]
port = http,https
logpath  = %(apache_error_log)s
[apache-badbots]
port = http,https
logpath  = %(apache_access_log)s
bantime  = 172800
maxretry = 1
[apache-noscript]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 6
[apache-overflows]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-nohome]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-botsearch]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-modsecurity]
port = http,https
logpath  = %(apache_error_log)s
maxretry = 2
[apache-shellshock]
port= http,https
logpath = %(apache_error_log)s
maxretry = 1
[nginx-http-auth]
ports   = http,https
logpath = %(nginx_error_log)s
[php-url-fopen]
port= http,https
logpath = %(nginx_access_log)s %(apache_access_log)s
[suhosin]
port= http,https
logpath = %(suhosin_log)s
[lighttpd-auth]
port= http,https
logpath = %(lighttpd_error_log)s
[roundcube-auth]
port = http,https
logpath  = /var/log/roundcube/userlogins
[openwebmail]
port = http,https
logpath  = /var/log/openwebmail.log
[horde]
port = http,https
logpath  = /var/log/horde/horde.log
[groupoffice]
port = http,https
logpath  = /home/groupoffice/log/info.log
[sogo-auth]
port = http,https
logpath  = /var/log/sogo/sogo.log
[tine20]
logpath  = /var/log/tine20/tine20.log
port = http,https
maxretry = 5
[guacamole]
port = http,https
logpath  = /var/log/tomcat*/catalina.out
[monit]
filter   = monit
port = 2812
logpath  = /var/log/monit
[webmin-auth]
port= 1
logpath = %(syslog_authpriv)s
[squid]
port =  80,443,3128,8080
logpath = /var/log/squid/access.log
[3proxy]
port= 3128
logpath = /var/log/3proxy.log
[proftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(proftpd_log)s
[pure-ftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(pureftpd_log)s
maxretry = 6
[gssftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(syslog_daemon)s
maxretry = 6
[wuftpd]
port = ftp,ftp-data,ftps,ftps-data
logpath  = %(wuftpd_log)s
maxretry =

Bug#737111: Bug seems to be fixed in latest debian samba package

[Skibbi]

Hello,
I've just upgraded samba, and the error seeems to be gone.

Regards

Bug#737111: Probably related to samba bug #10415

[Skibbi]

I have the same issues. It seems to be related to this samba bug:
https://bugzilla.samba.org/show_bug.cgi?id=10415

I would love to test samba with applied patch.

Regards

Bug#705213: tt-rss: Incorrect link to phpqrcode library

[skibbi]

Package: tt-rss
Version: 1.7.8+dfsg-1
Severity: normal

Dear Maintainer,
There is a small issue with latest tt-rss package. There is no link to 
phpqrcode library in the tt-rss/www/lib/ directory.
Instead, there is only empty directory phpqrcode/. This renders QR Code 
functionality of tt-rss unusable. There should
be a symlink to current Debian phpqrcode location /usr/share/phpqrcode.

Regards,

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages tt-rss depends on:
ii  dbconfig-common1.8.47+nmu1
ii  debconf [debconf-2.0]  1.5.49
ii  libapache2-mod-php55.4.4-15
ii  libjs-dojo-core1.7.2+dfsg-1
ii  libjs-dojo-dijit   1.7.2+dfsg-1
ii  libjs-scriptaculous1.9.0-2
ii  libphp-phpmailer   5.1-1
ii  libphp-simplepie   1.2.1-3
ii  php-gettext1.0.11-1
ii  php5   5.4.4-15
ii  php5-cli   5.4.4-15
ii  php5-mysql 5.4.4-15
ii  php5-pgsql 5.4.4-15
ii  phpqrcode  1.1.4-1

Versions of packages tt-rss recommends:
ii  apache2-mpm-prefork [httpd]  2.2.22-13
ii  php5-gd  5.4.4-15

Versions of packages tt-rss suggests:
ii  mysql-client   5.5.30+dfsg-1
ii  mysql-client-5.5 [mysql-client]5.5.30+dfsg-1
ii  mysql-server   5.5.30+dfsg-1
ii  php-apc3.1.13-1
ii  postgresql 9.1+134wheezy3
ii  postgresql-client-9.1 [postgresql-client]  9.1.9-1
pn  sphinxsearch   

-- Configuration Files:
/etc/default/tt-rss changed [not included]
/etc/tt-rss/config.php changed [not included]

-- debconf information excluded


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

Bug#696766: Acknowledgement (linux-image-3.2.0-4-686-pae: System freezes under high I/O load (swap issues))

[Skibbi]

Please close. Duplicate of #696765.

Bug#696765: linux-image-3.2.0-4-686-pae: System freezes under high I/O load (swap issues)

[skibbi]

 used,   428036 free,82496 cached

  PID USER  PR  NI  VIRT  RES  SHR S  %CPU %MEM TIME+ COMMAND
 5663 root  20   0  4636 1376 1008 R   0,7  0,3   0:00.29 top
3 root  20   0 000 S   0,3  0,0   0:00.25 ksoftirqd/0
1 root  20   0  2280  676  580 S   0,0  0,1   0:01.31 init
2 root  20   0 000 S   0,0  0,0   0:00.00 kthreadd
5 root  20   0 000 S   0,0  0,0   0:00.00 kworker/u:0
6 root  rt   0 000 S   0,0  0,0   0:00.01 migration/0
7 root  rt   0 000 S   0,0  0,0   0:00.00 watchdog/0
8 root  rt   0 000 S   0,0  0,0   0:00.01 migration/1
   10 root  20   0 000 S   0,0  0,0   0:00.04 ksoftirqd/1
   11 root  20   0 000 S   0,0  0,0   0:01.11 kworker/0:1
   12 root  rt   0 000 S   0,0  0,0   0:00.04 watchdog/1
   13 root   0 -20 000 S   0,0  0,0   0:00.00 cpuset
   14 root   0 -20 000 S   0,0  0,0   0:00.00 khelper
   15 root  20   0 000 S   0,0  0,0   0:00.00 kdevtmpfs
   16 root   0 -20 000 S   0,0  0,0   0:00.00 netns
   17 root  20   0 000 S   0,0  0,0   0:00.00 sync_supers
   18 root  20   0 000 S   0,0  0,0   0:00.00 bdi-default

iostats:   
Total DISK READ:   0.00 B/s | Total DISK WRITE:   2.41 M/s
  TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
 5517 be/4 root0.00 B/s0.00 B/s  0.00 % 99.78 % rsync -aA~de=/home/*
   23 be/4 root0.00 B/s0.00 B/s  0.00 % 98.60 % [kswapd0]
 5261 be/3 root0.00 B/s   15.19 K/s  0.00 % 93.78 % [jbd2/sdb1-8]
 5519 be/4 root0.00 B/s0.00 B/s  0.00 % 93.30 % python /u~sbin/iotop
 5526 be/4 skibbi  0.00 B/s0.00 B/s  0.00 % 86.87 % sshd: skibbi@pts/3
 5164 be/4 root0.00 B/s0.00 B/s  0.00 % 85.24 % [kworker/1:0]
 5163 be/4 root0.00 B/s0.00 B/s  0.00 % 82.82 % [kworker/0:0]
 2763 be/4 root0.00 B/s0.00 B/s  0.00 % 79.62 % vnstatd -d
  976 be/0 root0.00 B/s   20.17 K/s  0.00 % 78.44 % [loop0]
  194 be/3 root0.00 B/s  243.02 B/s  0.00 % 77.45 % [jbd2/sda1-8]
 5259 be/4 root0.00 B/s0.00 B/s  0.00 % 64.61 % [flush-8:16]
  443 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [flush-8:0]
1 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % init [2]
2 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [kthreadd]
3 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [ksoftirqd/0]
5 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [kworker/u:0]
6 rt/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [migration/0]
7 rt/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [watchdog/0]
8 rt/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [migration/1]
   10 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [ksoftirqd/1]
   11 be/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [kworker/0:1]
   12 rt/4 root0.00 B/s0.00 B/s  0.00 %  0.00 % [watchdog/1]

Any ideas how to debug this further?

Regards

-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 
4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae 
root=UUID=2ae7f68d-ed51-43b5-903c-db9142349068 ro gfxpayload=keep quiet

** Not tainted

** Kernel log:
[ 2250.678549]   .sysctl_sched_wakeup_granularity : 2.00
[ 2250.678552]   .sysctl_sched_child_runs_first   : 0
[ 2250.678554]   .sysctl_sched_features   : 24119
[ 2250.678558]   .sysctl_sched_tunable_scaling: 1 (logaritmic)
[ 2250.678561] 
[ 2250.678562] cpu#0, 2992.669 MHz
[ 2250.678564]   .nr_running: 0
[ 2250.678567]   .load  : 0
[ 2250.678569]   .nr_switches   : 208209
[ 2250.678572]   .nr_load_updates   : 79862
[ 2250.678574]   .nr_uninterruptible: 4294966857
[ 2250.678577]   .next_balance  : 0.487597
[ 2250.678580]   .curr->pid : 0
[ 2250.678583]   .clock : 2250678.222906
[ 2250.678585]   .cpu_load[0]   : 0
[ 2250.678588]   .cpu_load[1]   : 0
[ 2250.678590]   .cpu_load[2]   : 0
[ 2250.678592]   .cpu_load[3]   : 0
[ 2250.678594]   .cpu_load[4]   : 0
[ 2250.678598] 
[ 2250.678599] cfs_rq[0]:/
[ 2250.678601]   .exec_clock: 0.00
[ 2250.678604]   .MIN_vruntime  : 0.01
[ 2250.678607]   .min_vruntime  : 1725711.995307
[ 2250.678610]   .max_vruntime  : 0.01
[ 2250.678612]   .spread: 0.00
[ 2250.678615]   .spread0   : 0.00
[ 2250.678617]   .nr_spread_over: 0
[ 

Bug#652659: sslh: Cannot start sslh daemon - invalid .pid file directory

[Skibbi]

Package: sslh
Version: 1.10-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
After upgrade to latest sslh version, daemon cannot start anymore giving
following error:
Starting ssl/ssh multiplexer: sslh/var/run/sslh.pid: Permission denied

/var/run/sslh/ directory is created, but according to error message, daemon
tries to write to /var/run.
I've checked /etc/init.d/sslh but the pid direcroty there seems to be set
correctly.

Regards

-- System Information:
Debian Release: wheezy/sid
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sslh depends on:
ii  adduser   3.113
ii  debconf   1.5.41
ii  libc6 2.13-23
ii  lsb-base  3.2-28
ii  update-inetd  4.41

Versions of packages sslh recommends:
ii  apache2-mpm-prefork [httpd]  2.2.21-3
ii  openssh-server [ssh-server]  1:5.9p1-2

Versions of packages sslh suggests:
ii  openbsd-inetd [inet-superserver]  0.20091229-1

-- Configuration Files:
/etc/default/sslh changed:
RUN=yes
DAEMON=/usr/sbin/sslh
DAEMON_OPTS="--user sslh --listen 1.2.3.4:443 --ssh 127.0.0.1:22 --ssl
127.0.0.1:443"


-- debconf information:
* sslh/inetd_or_standalone: standalone

Bug#652656: sslh: Cannot start sslh daemon - invalid .pid file directory

[skibbi]

Package: sslh
Version: 1.10-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
After upgrade to latest sslh version, daemon cannot start anymore giving 
following error:
Starting ssl/ssh multiplexer: sslh/var/run/sslh.pid: Permission denied

/var/run/sslh/ directory is created, but according to error message, daemon 
tries to write to /var/run.
I've checked /etc/init.d/sslh but the pid direcroty there seems to be set 
correctly.

Regards

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.1.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sslh depends on:
ii  adduser   3.113
ii  debconf   1.5.41
ii  libc6 2.13-23
ii  lsb-base  3.2-28
ii  update-inetd  4.41

Versions of packages sslh recommends:
ii  apache2-mpm-prefork [httpd]  2.2.21-3
ii  openssh-server [ssh-server]  1:5.9p1-2

Versions of packages sslh suggests:
ii  openbsd-inetd [inet-superserver]  0.20091229-1

-- Configuration Files:
/etc/default/sslh changed:
RUN=yes
DAEMON=/usr/sbin/sslh
DAEMON_OPTS="--user sslh --listen 1.2.3.4:443 --ssh 127.0.0.1:22 --ssl 
127.0.0.1:443"


-- debconf information:
* sslh/inetd_or_standalone: standalone



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

Bug#642357: libapache2-mod-gnutls: TLS returning plaintext when listening on localhost

[skibbi]

Package: libapache2-mod-gnutls
Version: 0.5.10-1
Severity: important

Dear Maintainer,
I used following apache config:

ports.conf:

NameVirtualHost *:443
Listen 127.0.0.1:443


default-ssl:


DocumentRoot /var/www

Options FollowSymLinks
AllowOverride None


Options Indexes FollowSymLinks MultiViews
AllowOverride None
Order allow,deny
allow from all


GnuTLSEnable on
GnuTLSPriorities SECURE:!ANON-DH:!MD5
GnuTLSCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem
GnuTLSKeyFile /etc/ssl/private/ssl-cert-snakeoil.key



But when I tried to access the https page I got SSL_ERROR_RX_RECORD_TOO_LONG.
When I used telnet to access 127.0.0.1:443 I got plaintext data.

But if I configure ports.conf like this:


NameVirtualHost *:443
Listen 443


and try to access web page from remote computer, everything is OK. Unfortunately
I need my apache to listen on localhost.

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libapache2-mod-gnutls depends on:
ii  libc62.13-18 
ii  libgnutls26  2.12.7-8

libapache2-mod-gnutls recommends no packages.

libapache2-mod-gnutls suggests no packages.

-- 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

Bug#596200: sslh fails to bind to specified IP

[Skibbi]

Please mark this bug as duplicate of
#596199.
Sorry for duplication.

Regards

Bug#596200: sslh fails to bind to specified IP

[Skibbi]

Subject: sslh fails to bind to specified IP
Package: sslh
Version: 1.7a-1
Severity: important

*** Please type your report below this line ***
After upgrade to sslh 1.7 the daemon fails to bind to IP provided in
/etc/default/sslh. Instead of that it binds to 0.0.0.0:443.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sslh depends on:
ii  adduser   3.112  add and remove users and groups
ii  debconf   1.5.35 Debian configuration management
sy
ii  libc6 2.11.2-5   Embedded GNU C Library: Shared
lib
ii  libwrap0  7.6.q-19   Wietse Venema's TCP wrappers
libra
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init
scrip
ii  update-inetd  4.37   inetd configuration file
updater

Versions of packages sslh recommends:
ii  apache2-mpm-prefork [httpd]   2.2.16-2   Apache HTTP Server -
traditional n
ii  openssh-server [ssh-server]   1:5.5p1-5  secure shell (SSH) server, for
sec

Versions of packages sslh suggests:
ii  openbsd-inetd [inet-superse 0.20080125-6 The OpenBSD Internet
Superserver

-- Configuration Files:
/etc/default/sslh changed:
RUN=yes
DAEMON_OPTS="-u sslh -p 123.123.123.123:443 -s 127.0.0.1:22 -l 127.0.0.1:443
"


-- debconf information:
* sslh/inetd_or_standalone: standalone

Bug#596199: sslh fails to bind to specified IP

[skibbi]

Package: sslh
Version: 1.7a-1
Severity: important

After upgrade to sslh 1.7 the daemon fails to bind to IP provided in 
/etc/default/sslh. Instead of that it binds to 0.0.0.0:443.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages sslh depends on:
ii  adduser   3.112  add and remove users and groups
ii  debconf   1.5.35 Debian configuration management sy
ii  libc6 2.11.2-5   Embedded GNU C Library: Shared lib
ii  libwrap0  7.6.q-19   Wietse Venema's TCP wrappers libra
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip
ii  update-inetd  4.37   inetd configuration file updater

Versions of packages sslh recommends:
ii  apache2-mpm-prefork [httpd]   2.2.16-2   Apache HTTP Server - traditional n
ii  openssh-server [ssh-server]   1:5.5p1-5  secure shell (SSH) server, for sec

Versions of packages sslh suggests:
ii  openbsd-inetd [inet-superse 0.20080125-6 The OpenBSD Internet Superserver

-- Configuration Files:
/etc/default/sslh changed:
RUN=yes
DAEMON_OPTS="-u sslh -p 83.143.43.152:443 -s 127.0.0.1:22 -l 127.0.0.1:443"


-- debconf information:
* sslh/inetd_or_standalone: standalone



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

Bug#592310: arpon: Arpon daemon won't start

[skibbi]

Package: arpon
Version: 2.0-1
Severity: grave
Justification: renders package unusable


While starting arpon daemon following error occures:
Starting anti ARP poisoning daemon : arpon
/usr/sbin/arpon: option requires an argument -- 'y'

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to pl_PL.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages arpon depends on:
ii  libc6 2.11.2-2   Embedded GNU C Library: Shared lib
ii  libdumbnet1   1.12-3+b1  A dumb, portable networking librar
ii  libnet1   1.1.4-2library for the construction and h
ii  libpcap0.81.1.1-2system interface for user-level pa
ii  lsb-base  3.2-23.1   Linux Standard Base 3.2 init scrip

arpon recommends no packages.

arpon suggests no packages.

-- Configuration Files:
/etc/default/arpon changed:
DAEMON_OPTS="-d -f /var/log/arpon/arpon.log -g -y"
RUN="yes"


-- 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

Bug#588698: cryptsetup: cryptdisks scripts not mounting encrypted volumes

[skibbi]

Package: cryptsetup
Version: 2:1.1.3-1
Severity: important

After the upgrade of the cryptsetup package I'm no longer able to mount/umount 
my encrypted volumes using cryptdisks_start/stop scripts.

:~# cryptdisks_start sdb1_crypt
Starting crypto disk...sdb1_crypt (ignored)...done.

If I use for example 'cryptsetup luksOpen /dev/sdb1 sdb1_crypt' everything
works fine.

-- Package-specific info:
-- /proc/cmdline
root=LABEL=system ro 

-- /etc/crypttab
sda5_crypt /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap
sda6_crypt /dev/sda6 none luks,noauto
sdb1_crypt /dev/sdb1 none luks,noauto

-- /etc/fstab
# /etc/fstab: static file system information.
#
#
proc/proc   procdefaults0   0
# /dev/sda1   /   ext3errors=remount-ro 0   1
LABEL=system   /   ext3errors=remount-ro 0   1
/dev/mapper/sda6_crypt /home   ext3defaults0   0
/dev/mapper/sdb1_crypt /home/data/archive ext3 defaults0   0
/dev/mapper/sda5_crypt noneswapsw  0   0
/dev/scd0   /media/cdrom0   udf,iso9660 user,noauto 0   0

-- lsmod
Module  Size  Used by
parport_pc 15799  0 
ppdev   4058  0 
lp  5570  0 
parport22554  3 parport_pc,ppdev,lp
act_police  2968  0 
cls_flow4840  0 
cls_fw  2737  0 
cls_u32 4706  0 
sch_htb10423  0 
sch_hfsc   13154  0 
sch_ingress 1092  0 
sch_sfq 3874  0 
xt_time 1391  0 
xt_connlimit2323  0 
xt_realm 615  0 
iptable_raw 1471  0 
xt_comment   599  25 
xt_recent   4885  0 
xt_policy   1794  0 
ipt_ULOG4645  0 
ipt_REJECT  1517  4 
ipt_REDIRECT 803  0 
ipt_NETMAP   825  0 
ipt_MASQUERADE  1134  1 
ipt_ECN 1276  0 
ipt_ecn  928  0 
ipt_CLUSTERIP   3982  0 
ipt_ah   749  0 
ipt_addrtype1345  3 
nf_nat_tftp  702  0 
nf_nat_snmp_basic   6381  0 
nf_nat_sip  4440  0 
nf_nat_pptp 1702  0 
nf_nat_proto_gre 869  1 nf_nat_pptp
nf_nat_irc  1002  0 
nf_nat_h323 4395  0 
nf_nat_ftp  1519  0 
nf_nat_amanda828  0 
ts_kmp  1287  5 
nf_conntrack_amanda 1637  1 nf_nat_amanda
nf_conntrack_sane   2672  0 
nf_conntrack_tftp   2321  1 nf_nat_tftp
nf_conntrack_sip   10706  1 nf_nat_sip
nf_conntrack_proto_sctp 4754  0 
nf_conntrack_pptp   3077  1 nf_nat_pptp
nf_conntrack_proto_gre 2835  1 nf_conntrack_pptp
nf_conntrack_netlink11048  0 
nf_conntrack_netbios_ns  914  0 
nf_conntrack_irc2535  1 nf_nat_irc
nf_conntrack_h323  30924  1 nf_nat_h323
nf_conntrack_ftp4272  1 nf_nat_ftp
xt_TPROXY977  0 
nf_tproxy_core  1221  1 xt_TPROXY,[permanent]
xt_tcpmss   1017  0 
xt_pkttype   683  0 
xt_physdev  1228  0 
xt_owner 747  0 
xt_NFQUEUE  1565  0 
xt_NFLOG 718  0 
nfnetlink_log   5644  1 xt_NFLOG
xt_multiport1775  4 
xt_MARK  617  1 
xt_mark  613  0 
xt_mac   675  0 
xt_limit1088  0 
xt_length796  0 
xt_iprange  1049  0 
xt_helper879  0 
xt_hashlimit6157  0 
xt_DSCP 1451  8 
xt_dscp 1123  0 
xt_dccp 1507  0 
xt_conntrack1955  16 
xt_CONNMARK  943  0 
xt_connmark  799  0 
xt_CLASSIFY  617  0 
ipt_LOG 3570  5 
xt_tcpudp   1743  43 
xt_state 927  0 
iptable_nat 3551  1 
nf_nat 10568  12 
ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,nf_nat_tftp,nf_nat_sip,nf_nat_pptp,nf_nat_proto_gre,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,iptable_nat
nf_conntrack_ipv4   7597  19 iptable_nat,nf_nat
nf_defrag_ipv4   779  2 xt_TPROXY,nf_conntrack_ipv4
nf_conntrack   38067  31 
xt_connlimit,ipt_MASQUERADE,ipt_CLUSTERIP,nf_nat_tftp,nf_nat_snmp_basic,nf_nat_sip,nf_nat_pptp,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,nf_conntrack_amanda,nf_conntrack_sane,nf_conntrack_tftp,nf_conntrack_sip,nf_conntrack_proto_sctp,nf_conntrack_pptp,nf_conntrack_proto_gre,nf_conntrack_netlink,nf_conntrack_netbios_ns,nf_conntrack_irc,nf_conntrack_h323,nf_conntrack_ftp,xt_helper,xt_conntrack,xt_CONNMARK,xt_connmark,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
iptable_mangle  2325  1 
nfnetlink   1798  2 nf_conntrack_netlink,nfnetlink_log
iptable_filter  1790  1 
ip_tables   7

Bug#588697: cryptsetup: cryptdisks scripts not mounting encrypted volumes

[Skibbi]

From: skibbi 
To: Debian Bug Tracking System 
Date: Sun, 11 Jul 2010 13:09:21 +0200
Subject: cryptsetup: cryptdisks scripts not mounting encrypted volumes
Package: cryptsetup
Version: 2:1.1.3-1
Severity: important

After the upgrade of the cryptsetup package I'm no longer able to mount/umount 
my encrypted volumes using cryptdisks_start/stop scripts.

:~# cryptdisks_start sdb1_crypt
Starting crypto disk...sdb1_crypt (ignored)...done.

No propmpt for password, no errors. If I use for example 'cryptsetup luksOpen 
/dev/sdb1 sdb1_crypt' everything works fine.

-- Package-specific info:
-- /proc/cmdline
root=LABEL=system ro

-- /etc/crypttab
sda5_crypt /dev/sda5 /dev/urandom cipher=aes-cbc-essiv:sha256,size=256,swap
sda6_crypt /dev/sda6 none luks,noauto
sdb1_crypt /dev/sdb1 none luks,noauto

-- /etc/fstab
# /etc/fstab: static file system information.
#
#
proc/proc   procdefaults0   0
# /dev/sda1   /   ext3errors=remount-ro 0   1
LABEL=system   /   ext3errors=remount-ro 0   1
/dev/mapper/sda6_crypt /home   ext3defaults0   0
/dev/mapper/sdb1_crypt /home/data/archive ext3 defaults0   0
/dev/mapper/sda5_crypt noneswapsw  0   0
/dev/scd0   /media/cdrom0   udf,iso9660 user,noauto 0   0

-- lsmod
Module  Size  Used by
parport_pc 15799  0
ppdev   4058  0
lp  5570  0
parport22554  3 parport_pc,ppdev,lp
act_police  2968  0
cls_flow4840  0
cls_fw  2737  0
cls_u32 4706  0
sch_htb10423  0
sch_hfsc   13154  0
sch_ingress 1092  0
sch_sfq 3874  0
xt_time 1391  0
xt_connlimit2323  0
xt_realm 615  0
iptable_raw 1471  0
xt_comment   599  25
xt_recent   4885  0
xt_policy   1794  0
ipt_ULOG4645  0
ipt_REJECT  1517  4
ipt_REDIRECT 803  0
ipt_NETMAP   825  0
ipt_MASQUERADE  1134  1
ipt_ECN 1276  0
ipt_ecn  928  0
ipt_CLUSTERIP   3982  0
ipt_ah   749  0
ipt_addrtype1345  3
nf_nat_tftp  702  0
nf_nat_snmp_basic   6381  0
nf_nat_sip  4440  0
nf_nat_pptp 1702  0
nf_nat_proto_gre 869  1 nf_nat_pptp
nf_nat_irc  1002  0
nf_nat_h323 4395  0
nf_nat_ftp  1519  0
nf_nat_amanda828  0
ts_kmp  1287  5
nf_conntrack_amanda 1637  1 nf_nat_amanda
nf_conntrack_sane   2672  0
nf_conntrack_tftp   2321  1 nf_nat_tftp
nf_conntrack_sip   10706  1 nf_nat_sip
nf_conntrack_proto_sctp 4754  0
nf_conntrack_pptp   3077  1 nf_nat_pptp
nf_conntrack_proto_gre 2835  1 nf_conntrack_pptp
nf_conntrack_netlink11048  0
nf_conntrack_netbios_ns  914  0
nf_conntrack_irc2535  1 nf_nat_irc
nf_conntrack_h323  30924  1 nf_nat_h323
nf_conntrack_ftp4272  1 nf_nat_ftp
xt_TPROXY977  0
nf_tproxy_core  1221  1 xt_TPROXY,[permanent]
xt_tcpmss   1017  0
xt_pkttype   683  0
xt_physdev  1228  0
xt_owner 747  0
xt_NFQUEUE  1565  0
xt_NFLOG 718  0
nfnetlink_log   5644  1 xt_NFLOG
xt_multiport1775  4
xt_MARK  617  1
xt_mark  613  0
xt_mac   675  0
xt_limit1088  0
xt_length796  0
xt_iprange  1049  0
xt_helper879  0
xt_hashlimit6157  0
xt_DSCP 1451  8
xt_dscp 1123  0
xt_dccp 1507  0
xt_conntrack1955  16
xt_CONNMARK  943  0
xt_connmark  799  0
xt_CLASSIFY  617  0
ipt_LOG 3570  5
xt_tcpudp   1743  43
xt_state 927  0
iptable_nat 3551  1
nf_nat 10568  12 
ipt_REDIRECT,ipt_NETMAP,ipt_MASQUERADE,nf_nat_tftp,nf_nat_sip,nf_nat_pptp,nf_nat_proto_gre,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,iptable_nat
nf_conntrack_ipv4   7597  19 iptable_nat,nf_nat
nf_defrag_ipv4   779  2 xt_TPROXY,nf_conntrack_ipv4
nf_conntrack   38067  31 
xt_connlimit,ipt_MASQUERADE,ipt_CLUSTERIP,nf_nat_tftp,nf_nat_snmp_basic,nf_nat_sip,nf_nat_pptp,nf_nat_irc,nf_nat_h323,nf_nat_ftp,nf_nat_amanda,nf_conntrack_amanda,nf_conntrack_sane,nf_conntrack_tftp,nf_conntrack_sip,nf_conntrack_proto_sctp,nf_conntrack_pptp,nf_conntrack_proto_gre,nf_conntrack_netlink,nf_conntrack_netbios_ns,nf_conntrack_irc,nf_conntrack_h323,nf_conntrack_ftp,xt_helper,xt_conntrack,xt_CONNMARK,xt_connmark,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4
iptable_mangle  

Bug#399471: wodim: No disk / Wrong disk! error

[Skibbi]

Subject: wodim: No disk / Wrong disk! error
Followup-For: Bug #399471
Package: wodim
Version: 9:1.1.6-1

Hello,
I have the same problem that Thomas had. Whenever I try to burn or erase CD-RW 
i get "No disc error". The same CD-RW and burner works flawlesssly in windows. 
Here are some additional informations:

:~# wodim blank=all dev=/dev/hdc
Device type: Removable CD-ROM
Version: 0
Response Format: 2
Capabilities   :
Vendor_info: 'LITE-ON '
Identification : 'CD-RW SOHR-5238S'
Revision   : '4S04'
Device seems to be: Generic mmc CD-RW.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE FORCESPEED
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
Errno: 0 (Success), test unit ready scsi sendcmd: no error
CDB:  00 00 00 00 00 00
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 02 00 00 00 00 0A 00 00 00 00 3A 00 00 00
Sense Key: 0x2 Not Ready, Segment 0
Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
Sense flags: Blk 0 (not valid)
cmd finished after 0.000s timeout 40s
wodim: No disk / Wrong disk!

:~# lspci
00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and Memory 
Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82815 CGC [Chipset 
Graphics Controller] (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 02)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 02)
01:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
01:0e.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)

:~# hdparm /dev/hdc

/dev/hdc:
 IO_support=  0 (default 16-bit)
 unmaskirq =  0 (off)
 using_dma =  1 (on)
 keepsettings  =  0 (off)
 readonly  =  0 (off)
 readahead = 256 (on)
 HDIO_GETGEO failed: Inappropriate ioctl for device

-- System Information:
Debian Release: 4.0 by Linux-Systeme
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages wodim depends on:
ii  libc6 2.5-11 GNU C Library: Shared libraries
ii  libcap1   1:1.10-14  support for getting/setting POSIX.

Versions of packages wodim recommends:
ii  genisoimage   9:1.1.6-1  Creates ISO-9660 CD-ROM filesystem

-- no debconf information

Regards,
Krystian

Bug#424610: NT_STATUS_OBJECT_PATH_NOT_FOUND error

[Skibbi]

Hi,
I've resetted all client's cache so the problem is gone. Please close 
this bug.


Regards


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#424610: NT_STATUS_OBJECT_PATH_NOT_FOUND error

[Skibbi]

>We're missing some information, still.

>What is the host name of your server?
>I suspect "maurycy", but I'd like to be sure.

Yes, that's the hostname.

>What are you doing on the client? Connect a share? If so, what share?
>How do you connect it?

I'am trying to connect a share by typing in explorer:
\\maurycy\movies2
Then I get an error saying that requested share cannot be found on this 
location. But if I type \\10.255.0.16\movies2 I can acces the share.

>Does this happen with all shares?

No, it happens only with movies2 share. Other shares are working without 
problems.

Regards


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#423107: rtorrent fails to start

[Skibbi]

Adeodato Simó pisze:

Uhm, very strange indeed. Particularly because you removed libtorrent.so.10*
before reinstalling the package, which should have overwritten the
broken symlink with the appropriate file.

What does `ls -l /usr/lib/libtorrent.so.10*` say?
  

$ ls -l /usr/lib/libtorrent.so.10*
lrwxrwxrwx 1 root root 20 maj 10 22:00 /usr/lib/libtorrent.so.10 -> 
libtorrent.so.11.0.1

-rw-r--r-- 1 root root 602192 kwi 19 22:34 /usr/lib/libtorrent.so.10.0.4

Problem solved, libtorrent.so.11.0.1 was the cause! I totally forgot 
that few weeks ago I compiled libtorrent and copied it to /usr/lib/.


Thanks!
regards

Bug#423107: rtorrent fails to start

[Skibbi]

Adeodato Simó pisze:

  # dpkg -i libtorrent10_0.11.4-1_i386.deb

  $ md5sum /usr/lib/libtorrent.so.10*
  (this should output, as said before, 3dc81e4136a6ebe4e34bbc5f962dcba7)
  

$ md5sum /usr/lib/libtorrent.so.10*
52cf12ffe7b12174bf354b0dd31d7ae3  /usr/lib/libtorrent.so.10 (it seems I 
checked only symbolic link)

3dc81e4136a6ebe4e34bbc5f962dcba7  /usr/lib/libtorrent.so.10.0.4

Very strange. Maybe some kind of debugging will help?

regards

Bug#423107: rtorrent fails to start

[Skibbi]

Adeodato Simó pisze:

That md5sum does not match the one shipped in the official libtorrent10
0.11.4-1 (i386) package.

Try reinstalling the libtorrent10 package, and check that afterwards the
md5sum of /usr/lib/libtorrent.so.10 is 3dc81e4136a6ebe4e34bbc5f962dcba7.
rtorrent should work then.
  

I've downloaded official debian package, but md5 od the librottent file is:
52cf12ffe7b12174bf354b0dd31d7ae3  /usr/lib/libtorrent.so.10
I've downloaded file from: 
http://http.us.debian.org/debian/pool/main/libt/libtorrent/libtorrent10_0.11.4-1_i386.deb

md5 of the package is OK. Rtorrent still doesn't work.

regards

Bug#423107: rtorrent fails to start

[Skibbi]

$ which rtorrent
/usr/bin/rtorrent

$ md5sum /usr/lib/libtorrent.so.10
52cf12ffe7b12174bf354b0dd31d7ae3  /usr/lib/libtorrent.so.10

$ ldd /usr/bin/rtorrent
   libncurses.so.5 => /lib/libncurses.so.5 (0xb7f93000)
   libcurl.so.3 => /usr/lib/libcurl.so.3 (0xb7f5e000)
   libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb7f36000)
   libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb7eb1000)
   libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb7e8c000)
   libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb7e84000)
   libcom_err.so.2 => /lib/libcom_err.so.2 (0xb7e8)
   libresolv.so.2 => /lib/i686/cmov/libresolv.so.2 (0xb7e6d000)
   libidn.so.11 => /usr/lib/libidn.so.11 (0xb7e3d000)
   libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7e39000)
   libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0xb7df9000)
   libz.so.1 => /usr/lib/libz.so.1 (0xb7de5000)
   libtorrent.so.10 => /usr/lib/libtorrent.so.10 (0xb7d52000)
   libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 
(0xb7c16000)

   libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0xb7c1)
   libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb7b2c000)
   libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb7b05000)
   libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb7afa000)
   libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb79b6000)
   libkeyutils.so.1 => /lib/libkeyutils.so.1 (0xb79b3000)
   /lib/ld-linux.so.2 (0xb7fdc000)

Recently I've changed kernel from 2.6.18 to 2.6.20 and upgraded to libc 
2.5. Maybe there is some incompatibility, because earlier I was able to 
run rtorrent flawleslly.
Another thing. I use patched libc and other libraries (PaX support and 
other minor fixes) from http://debian.linux-systeme.com/. Maybe this 
will help You trace the error.


regards


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#423107: rtorrent fails to start

[Skibbi]

Here it is:
directory = /home/data/incoming
session = ./.rtorrent
schedule = watch_directory,5,5,load_start=/home/data/incoming/*.torrent
port_range = -
use_udp_trackers = yes
encryption = allow_incoming,enable_retry,prefer_plaintext
max_open_sockets = 75

regards


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#423107: rtorrent fails to start

[Skibbi]

Subject: rtorrent fails to start
Package: rtorrent
Version: 0.7.4-1
Severity: grave
Justification: renders package unusable

*** Please type your report below this line ***

rtorrent fails to start with following error:
rtorrent: symbol lookup error: rtorrent: undefined symbol:
_ZN7torrent21max_download_unchokedEv

-- System Information:
Debian Release: 4.0 by Linux-Systeme
Architecture: i386 (i686)

Kernel: Linux 2.6.20-1-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)
Shell: /bin/sh linked to /bin/bash

Versions of packages rtorrent depends on:
ii  libc62.5-7   GNU C Library: Shared libraries
ii  libcomer 1.39+1.40-WIP-2007.04.07+dfsg-2 common error description 
library
ii  libcurl3 7.15.5-1Multi-protocol file 
transfer libra

ii  libgcc1  1:4.1.2-6   GCC support library
ii  libidn11 0.6.5-1 GNU libidn library, 
implementation

ii  libkrb53 1.6.dfsg.1-2MIT Kerberos runtime libraries
ii  libncurs 5.5-5   Shared libraries for 
terminal hand
ii  libsigc+ 2.0.17-2type-safe Signal Framework 
for C++

ii  libssl0. 0.9.8e-5SSL shared libraries
ii  libstdc+ 4.1.2-6 The GNU Standard C++ Library v3
ii  libtorre 0.11.4-1a C++ BitTorrent library
ii  zlib1g   1:1.2.3-13  compression library - runtime

rtorrent recommends no packages.

-- no debconf information


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#401006: libtorrent9: safe_sync errors

[Skibbi]

Package: libtorrent9
Version: 0.10.4-1
Severity: grave
Justification: causes non-serious data loss

Few days ago I've installed linux-image-2.6.18-3-686. Since then
rtorrent/libtorrent started to behave strange. After downloading the
files, when hash check was performed, rtorrent began to display following 
errors:
bad CRC check consider using 'safe_sync'
Turning on safe sync didn't help.

I believe that these errors are caused by the following changes in the kernel 
package:
   * Fix msync() for LSB 3.1 compliance, backport fedora patches from
2.6.19
- mm: tracking shared dirty pages
- mm: balance dirty pages
- mm: optimize the new mprotect() code a bit
- mm: small cleanup of install_page()
- mm: fixup do_wp_page()
- mm: msync() cleanup (closes: #394392)

With linux-image-2.6.18-2 the problem does not occur.

-- System Information:
Debian Release: 4.0 by Linux-Systeme
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)

Versions of packages libtorrent9 depends on:
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-20  GCC support library
ii  libsigc++-2.0-0c2a   2.0.17-2type-safe Signal Framework for C++
ii  libssl0.9.8  0.9.8c-4SSL shared libraries
ii  libstdc++6   4.1.1-20The GNU Standard C++ Library v3

Versions of packages libtorrent9 recommends:
ii  rtorrent  0.6.4-1ncurses BitTorrent client based on

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#340711: (no subject)

[Skibbi]

Subject: wzdftpd: Impossible to upload files
Package: wzdftpd
Version: 0.5.5-4
Severity: important

When I  try to upload files I get following error:
501 nonexistant file or permission denied.
Downgrade to 0.5.5-3 fixes problem.

-- System Information:
Debian Release: unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages wzdftpd depends on:
ii  libc6 2.3.5-9GNU C Library: Shared libraries an
ii  libgcrypt11   1.2.2-2LGPL Crypto library - runtime libr
ii  libgnutls12   1.2.9-2the GNU TLS library - runtime libr
ii  libgpg-error0 1.1-4  library for common error values an
ii  libpam0g  0.79-3 Pluggable Authentication Modules l
ii  libtasn1-20.2.17-1   Manage ASN.1 structures (runtime)
ii  ucf   2.003  Update Configuration File: preserv
ii  zlib1g1:1.2.3-8  compression library - runtime

wzdftpd recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]