Bug#1040979: write_files: defer not working any more

2023-07-15 Thread Sven Strickroth 

Am 14.07.2023 um 23:46 schrieb Noah Meyerhans:

Can you show that write_files works without the defer flag?


Writing files without defer works.

2023-07-15 10:57:15,044 - modules.py[DEBUG]: Running module write-files 
('/usr/lib/python3/dist-packages/cloudinit/config/cc_write_files.py'>) 
with frequency once-per-instance
2023-07-15 10:57:15,045 - handlers.py[DEBUG]: start: 
init-network/config-write-files: running config-write-files with 
frequency once-per-instance
2023-07-15 10:57:15,045 - util.py[DEBUG]: Writing to 
/var/lib/cloud/instances//sem/config_write_files - wb: [644] 24 bytes
2023-07-15 10:57:15,045 - helpers.py[DEBUG]: Running config-write-files 
using lock ('/var/lib/cloud/instances//sem/config_write_files'>)
2023-07-15 10:57:15,045 - util.py[DEBUG]: Writing to /test - wb: [644] 
117 bytes
2023-07-15 10:57:15,045 - util.py[DEBUG]: Changing the ownership of 
/test to 0:0
2023-07-15 10:57:15,046 - handlers.py[DEBUG]: finish: 
init-network/config-write-files: SUCCESS: config-write-files ran 
successfully


Also, I'm curious to see what happens if you invoke the 
write_files_deferred module by hand with a command like


$ sudo cloud-init single --name cc_write_files_deferred \
   --frequency always --report


# cloud-init single --name cc_write_files_deferred \
   --frequency always --report
Cloud-init v. 22.4.2 running 'single' at Sat, 15 Jul 2023 10:59:34 
+. Up 146.09 seconds.


After that the files marked as defer are created.


It should generate messages in /var/log/cloud-init.log.


2023-07-15 10:59:34,786 - util.py[DEBUG]: Cloud-init v. 22.4.2 running 
'single' at Sat, 15 Jul 2023 10:59:34 +. Up 146.09 seconds.
2023-07-15 10:59:34,787 - util.py[DEBUG]: Reading from 
/usr/lib/python3/dist-packages/cloudinit/config/schemas/schema-cloud-config-v1.json 
(quiet=False)
2023-07-15 10:59:34,788 - util.py[DEBUG]: Read 133834 bytes from 
/usr/lib/python3/dist-packages/cloudinit/config/schemas/schema-cloud-config-v1.json
2023-07-15 10:59:34,790 - stages.py[DEBUG]: Using distro class 'cloudinit.distros.debian.Distro'>
2023-07-15 10:59:34,790 - modules.py[DEBUG]: Running module 
cc_write_files_deferred ('cloudinit.config.cc_write_files_deferred' from 
'/usr/lib/python3/dist-packages/cloudinit/config/cc_write_files_deferred.py'>) 
with frequency always
2023-07-15 10:59:34,790 - handlers.py[DEBUG]: start: 
single/cc_write_files_deferred/config-cc_write_files_deferred: running 
config-cc_write_files_deferred with frequency always
2023-07-15 10:59:34,790 - helpers.py[DEBUG]: Running 
config-cc_write_files_deferred using lock (object at 0x7f6fad0c3590>)
2023-07-15 10:59:34,790 - util.py[DEBUG]: Writing to /test-defer - wb: 
[644] 41 bytes
2023-07-15 10:59:34,791 - util.py[DEBUG]: Changing the ownership of 
/51-79p.cnf to 0:0
2023-07-15 10:59:34,791 - handlers.py[DEBUG]: finish: 
single/cc_write_files_deferred/config-cc_write_files_deferred: SUCCESS: 
config-cc_write_files_deferred ran successfully
2023-07-15 10:59:34,791 - util.py[DEBUG]: Reading from /proc/uptime 
(quiet=False)

2023-07-15 10:59:34,791 - util.py[DEBUG]: Read 14 bytes from /proc/uptime
2023-07-15 10:59:34,791 - util.py[DEBUG]: cloud-init mode 'single' took 
0.070 seconds (0.07)
2023-07-15 10:59:34,791 - handlers.py[DEBUG]: finish: 
single/cc_write_files_deferred: SUCCESS: running single module 
cc_write_files_deferred


Best,
 Sven

Bug#1040979: write_files: defer not working any more

2023-07-14 Thread Sven Strickroth 

Am 13.07.2023 um 19:07 schrieb Noah Meyerhans:

I'm not able to reproduce the behavior you describe.  defer seems to
work as expected.  For example:

admin@ip-10-0-0-87:~$ ec2-metadata --ami-id
ami-id: ami-0544719b13af6edc3
admin@ip-10-0-0-87:~$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
write_files:
- content: |
 testing. this file should be owned by the dynamically created user
   path: /test-file
   owner: admin:admin
   defer: true
admin@ip-10-0-0-87:~$ ls -l /test-file
-rw-r--r-- 1 admin admin 67 Jul 13 16:59 /test-file


That example does not work for me on Hetzner.cloud.


I note that your cloud-config attempts to set the locale:


#cloud-config
locale: de_DE.UTF-8


I suspect that that's failing (see #955733) and interfering with
subsequent module execution.  If you remove the `locale` setting, does
your userdata work as expected?


Running without locale does not change anything.

"grep write-files-deferred cloud-init.log" returns nothing.

Best,
 Sven

Bug#1040979: write_files: defer not working any more

2023-07-13 Thread Sven Strickroth 
Package: cloud-init
Version: 22.4.2-1
Severity: important
X-Debbugs-Cc: em...@cs-ware.de

Dear Maintainer,

starting with the shipped version in Debian 12 the write_files feature with 
defer option does not work any more.

Example:
#cloud-config
locale: de_DE.UTF-8
timezone: Europe/Berlin
package_update: true # Implied with `package_upgrade: true`
package_upgrade: true
packages: 
['joe','mariadb-server','aptitude','psmisc','bzip2','fail2ban','postfix','apticron','nagios-nrpe-server','monitoring-plugins','libmariadb3','borgbackup','logwatch']
write_files:
- content: |
[mysqldump]
max_allowed_packet = 60M
  path: /etc/mysql/mariadb.conf.d/51-dump.cnf
  defer: true

The file /etc/mysql/mariadb.conf.d/51-dump.cnf is not created any more 
(compared to Debian 11; 20.4.1-2+deb11) by cloud-init. Nothing can be seen in 
the logs.

This significantly limits how cloud-init can be used to set up new machines.

Providing an updated version as backport etc. does not help as cloud-init is 
particularly used to set up a machine from a plain base image. It would be 
important to get a fix in the next point release.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/3 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 cloud-init depends on:
ii  eject  2.38.1-5+b1
ii  fdisk  2.38.1-5+b1
ii  gdisk  1.0.9-2.1
ii  isc-dhcp-client4.4.3-P1-2
ii  locales2.36-9
ii  lsb-release12.0-1
ii  procps 2:4.0.2-3
ii  python33.11.2-1+b1
ii  python3-configobj  5.0.8-1
ii  python3-jinja2 3.1.2-1
ii  python3-jsonpatch  1.32-2
ii  python3-jsonschema 4.10.3-1
ii  python3-netifaces  0.11.0-2+b1
ii  python3-oauthlib   3.2.2-1
ii  python3-requests   2.28.1+dfsg-1
ii  python3-serial 3.5-1.1
ii  python3-yaml   6.0-3+b2
ii  sysvinit-utils [lsb-base]  3.06-4
ii  util-linux 2.38.1-5+b1

Versions of packages cloud-init recommends:
ii  cloud-guest-utils  0.33-1
ii  eatmydata  130-2
ii  sudo   1.9.13p3-1

Versions of packages cloud-init suggests:
ii  btrfs-progs  6.2-1
ii  e2fsprogs1.47.0-2
ii  xfsprogs 6.1.0-1

-- no debconf information

Bug#966422: bind9utils: dnssec-signzone -N unixtime behaves like increment

2020-07-29 Thread Sven Strickroth 
> Please report this upstream at
> https://gitlab.isc.org/isc-projects/bind9/-/issues . When you have a
> bugid feel free to report back to we can tag this bug accordingly.

Reported upstream: 

Best,
 Sven

Bug#966422: bind9utils: dnssec-signzone -N unixtime behaves like increment

2020-07-28 Thread Sven Strickroth 
Am 28.07.2020 um 17:38 schrieb Bernhard Schmidt:
> I think there is a (new in Buster?) protection against the serial of the
> signed zone being lower than in the unsigned zone.

Thank you for digging into this!

This info helps me a least to quickly fix the issue by lowering the
serial in the zone-template.

> So I'm reasonably sure upstream will see this as a feature.

Then upstream should issue a warning informing the user the requested
option was ignored in order to prevent a lower serial number.

-- 
Best regards,
 Sven Strickroth
 PGP key id F5A9D4C4 @ any key-server

Bug#966422: bind9utils: dnssec-signzone -N unixtime behaves like increment

2020-07-28 Thread Sven Strickroth 
Package: bind9utils
Version: 1:9.11.5.P4+dfsg-5.1+deb10u1
Severity: important

Dear Maintainer,

I recently upgraded from Debian 9.13 to 10.4. Starting from this date 
"dnssec-signzone -N unixtime" does not work any more causing my DNS slaves to 
fail receiving changes.

With Debian 9 "dnssec-signzone -N unixtime" uses the current unix timestamp as 
the serial numer for the generated signed zone, however, with the version 
shipped with Debian 10 the serial number is just incremented from the to be 
signd zone file. As I use a common zone-template for a huge nubmer of zones, 
every further signing of the template will use the very same serial numer 
(template serial number + 1).

I use the following command to sign my zones (using a script):
 /usr/sbin/dnssec-signzone -o ZONE.TLD. -e +1209600 -N unixtime zone.db 
K*.private

I don't get any warning or error. I checked that "-N date" uses the current 
date, however, "date" does not fit the needs of my scenario 8see above). Using 
"-N something" causes an error.

Best,
 Sven

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bind9utils depends on:
ii  libbind9-161  1:9.11.5.P4+dfsg-5.1+deb10u1
ii  libc6 2.28-10
ii  libcap2   1:2.25-2
ii  libcom-err2   1.44.5-1+deb10u3
ii  libdns11041:9.11.5.P4+dfsg-5.1+deb10u1
ii  libfstrm0 0.4.0-1
ii  libgeoip1 1.6.12-1
ii  libgssapi-krb5-2  1.17-3
ii  libisc11001:9.11.5.P4+dfsg-5.1+deb10u1
ii  libisccc161   1:9.11.5.P4+dfsg-5.1+deb10u1
ii  libisccfg163  1:9.11.5.P4+dfsg-5.1+deb10u1
ii  libjson-c30.12.1+ds-2
ii  libk5crypto3  1.17-3
ii  libkrb5-3 1.17-3
ii  liblmdb0  0.9.22-1
ii  libprotobuf-c11.3.1-1+b1
ii  libssl1.1 1.1.1d-0+deb10u3
ii  libxml2   2.9.4+dfsg1-7+b3
ii  python3   3.7.3-1
ii  python3-ply   3.11-3

bind9utils recommends no packages.

bind9utils suggests no packages.

-- no debconf information

Bug#966027: systemd: systemctl failures during upt pgrade due to missing libcryptsetup.so.12

2020-07-25 Thread Sven Strickroth 
Hi,

Am 23.07.2020 um 00:30 schrieb Michael Biebl:
> Those error messages are from systemd-tty-ask-password-agent not systemctl.
> Do you actually encounter any problems or is this mostly cosmetic?

I'm not aware of actual problems. However, I don't know what tasks
should be performed at the specific stages and so I don't know if those
were applied correctly.

> Why does a systemctl call trigger the start of
> systemd-tty-ask-password-agent for you? Do you have a special way to
> start your dist-upgrade?
> Can you provide steps how this issue can be reproduced?

I just had a normal Debian 9.13 installation and ran "apt upgrade".

-- 
Best regards,
 Sven Strickroth
 PGP key id F5A9D4C4 @ any key-server

Bug#966027: systemd: systemctl failures during upt pgrade due to missing libcryptsetup.so.12

2020-07-22 Thread Sven Strickroth 
Package: systemd
Version: 241-7~deb10u4
Severity: important

Dear Maintainer,

I upgraded from stretch (9.13) to buster today and saw a similar issue as 
Bug#897986.

apt upgrade shows me:
...
Preparing to unpack .../1-systemd_241-7~deb10u4_amd64.deb ...
Unpacking systemd (241-7~deb10u4) over (232-25+deb9u12) ...
...
Setting up util-linux (2.33.1-0.1) ...
update-alternatives: warning: alternative /usr/bin/pg (part of link group 
pager) doesn't exist; removing from list of alternatives
/bin/systemd-tty-ask-password-agent: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
Setting up sysvinit-utils (2.93-8) ...
...
(Reading database ... 60937 files and directories currently installed.)
Preparing to unpack .../libpam-runtime_1.3.1-5_all.deb ...
Unpacking libpam-runtime (1.3.1-5) over (1.1.8-3.6) ...
Setting up libpam-runtime (1.3.1-5) ...
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 60985 files and directories currently installed.)
Preparing to unpack .../cron_3.0pl1-134+deb10u1_amd64.deb ...
/bin/systemd-tty-ask-password-agent: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
...
Preparing to unpack .../libsystemd0_241-7~deb10u4_amd64.deb ...
Unpacking libsystemd0:amd64 (241-7~deb10u4) over (232-25+deb9u12) ...
Setting up libsystemd0:amd64 (241-7~deb10u4) ...
...

-- Package-specific info:

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-4
ii  libapparmor1 2.13.2-10
ii  libaudit11:2.8.4-3
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcryptsetup12  2:2.1.0-5+deb10u2
ii  libgcrypt20  1.8.4-5
ii  libgnutls30  3.6.7-4+deb10u4
ii  libgpg-error01.35-1
ii  libidn11 1.33-2.2
ii  libip4tc01.8.2-4
ii  libkmod2 26-1
ii  liblz4-1 1.8.3-1
ii  liblzma5 5.2.4-1
ii  libmount12.33.1-0.1
ii  libpam0g 1.3.1-5
ii  libseccomp2  2.3.3-4
ii  libselinux1  2.8-1+b1
ii  libsystemd0  241-7~deb10u4
ii  mount2.33.1-0.1
ii  util-linux   2.33.1-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-1
ii  libpam-systemd  241-7~deb10u4

Versions of packages systemd suggests:
ii  policykit-10.105-25
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.133+deb10u1
ii  udev 241-7~deb10u4

-- no debconf information

Bug#946354: linux-image-4.19.0-6-amd64: Filesystem access gets stuck when LVM snapshot creation interrupted

2019-12-07 Thread Sven Strickroth 
Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I'm using LVM snapshots for creating consistent backups of ext4 filesystems.
Since a few months I'm experiencing severe problems causing the whole system
to get stuck. First I thought this was a hardware issue, but I found some
ways to reproduce this or a similar issue (even on a different system in a VM).

Steps to reproduce this issue:
Have a LVM set up with one LV (test, size: 2G) formatted with ext4 and
mounted. Do some work on the mounted FS (e.g., using fio) and create a
snapshot while the FS is busy using

lvcreate --snapshot -p r -L 1G --name snap /dev/vg/test

and issue Ctrl+C immediately before the command finishes. Now the system
will get into a broken state (this is especially a problem if you snapshot
/var): All further writes to the mounted LV will be stalled forever as well
as LVM commands such as pvdisplay and lvs.

After a few minutes the are the following errors logged in the kernel ring
buffer:
[  605.032827] INFO: task pvdisplay:878 blocked for more than 120 seconds.
[  605.032926]   Not tainted 4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u2
[  605.033000] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  605.033088] pvdisplay   D0   878543 0x8004
[  605.033094] Call Trace:
[  605.033113]  ? __schedule+0x2a2/0x870
[  605.033119]  ? _cond_resched+0x15/0x30
[  605.033124]  schedule+0x28/0x80
[  605.033130]  schedule_timeout+0x26d/0x390
[  605.033139]  ? __kfifo_from_user_r+0xb0/0xb0
[  605.033144]  ? __percpu_ref_switch_mode+0xd4/0x180
[  605.033149]  wait_for_completion+0x11f/0x190
[  605.033159]  ? wake_up_q+0x70/0x70
[  605.033166]  exit_aio+0xdc/0xe3
[  605.033177]  mmput+0x28/0x130
[  605.033183]  do_exit+0x290/0xb90
[  605.033190]  ? __switch_to_asm+0x41/0x70
[  605.033195]  ? __switch_to_asm+0x41/0x70
[  605.033200]  ? __switch_to_asm+0x35/0x70
[  605.033204]  ? __switch_to_asm+0x41/0x70
[  605.033209]  ? __switch_to+0x115/0x440
[  605.033214]  ? __switch_to_asm+0x41/0x70
[  605.033219]  do_group_exit+0x3a/0xa0
[  605.033226]  get_signal+0x137/0x790
[  605.033231]  do_signal+0x36/0x6c0
[  605.033239]  ? finish_wait+0x80/0x80
[  605.033246]  ? __hrtimer_init+0xb0/0xb0
[  605.033250]  ? do_io_getevents+0x7c/0xc0
[  605.033260]  exit_to_usermode_loop+0x89/0xf0
[  605.033266]  do_syscall_64+0x10d/0x110
[  605.033272]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  605.033278] RIP: 0033:0x7f2ad18a9f59
[  605.033290] Code: Bad RIP value.
[  605.033293] RSP: 002b:7ffca85d4628 EFLAGS: 0246 ORIG_RAX: 
00d0
[  605.033298] RAX: fffc RBX: 7f2ad154a700 RCX: 7f2ad18a9f59
[  605.033299] RDX: 0040 RSI: 0001 RDI: 7f2ad1255000
[  605.033301] RBP: 7f2ad1255000 R08:  R09: 0002a85d46b0
[  605.033303] R10: 7ffca85d46b0 R11: 0246 R12: 0001
[  605.033305] R13:  R14: 0040 R15: 7ffca85d46b0
[  605.033314] INFO: task fio:1010 blocked for more than 120 seconds.
[  605.033385]   Not tainted 4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u2
[  605.033458] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  605.033542] fio D0  1010   1006 0x
[  605.033546] Call Trace:
[  605.033553]  ? __schedule+0x2a2/0x870
[  605.033558]  schedule+0x28/0x80
[  605.033564]  rwsem_down_read_failed+0x111/0x180
[  605.033572]  ? kmem_cache_alloc_trace+0x155/0x1d0
[  605.033581]  call_rwsem_down_read_failed+0x14/0x30
[  605.033587]  __percpu_down_read+0x4f/0x80
[  605.033596]  __sb_start_write+0x5f/0x70
[  605.033603]  mnt_want_write+0x20/0x50
[  605.033609]  path_openat+0xc88/0x1480
[  605.033616]  ? alloc_set_pte+0xf2/0x560
[  605.033624]  ? filemap_map_pages+0x360/0x3a0
[  605.033629]  do_filp_open+0x93/0x100
[  605.033635]  ? __handle_mm_fault+0x1090/0x1270
[  605.033641]  ? __check_object_size+0x15d/0x189
[  605.033647]  do_sys_open+0x186/0x210
[  605.033655]  do_syscall_64+0x53/0x110
[  605.033661]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  605.033664] RIP: 0033:0x7f06d6ea4d0e
[  605.033669] Code: Bad RIP value.
[  605.033671] RSP: 002b:7ffdb6c3df30 EFLAGS: 0293 ORIG_RAX: 
0101
[  605.033675] RAX: ffda RBX: 7f06ca1e9510 RCX: 7f06d6ea4d0e
[  605.033677] RDX: 4042 RSI: 7f06ca1e9690 RDI: ff9c
[  605.033678] RBP:  R08:  R09: 560c2b42dc20
[  605.033680] R10: 0180 R11: 0293 R12: 4042
[  605.033682] R13: 4042 R14: 7f06a9c1d000 R15: 
[  725.866073] INFO: task pvdisplay:878 blocked for more than 120 seconds.
[  725.866161]   Not tainted 4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u2
[  725.866235] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  725.866321] pvdisplay   D0

Bug#856052: postfwd: Allow to configure unix socket using /etc/default/postfwd

2017-02-24 Thread Sven Strickroth 
Package: postfwd
Version: 1.35-3
Severity: wishlist

Dear Maintainer,

right now in /etc/default/postfwd there are specific variables for INET and
PORT which prevents the usage of the default initscript for configuring
postfwd2 to use an unix socket instead of an inet socket.

A solution could be to drop the special INET and PORT variables in
/etc/default/postfwd as well as  "--interface=${INET} --port=${PORT}"
in /etc/init.d/postfwd2 and pass those parameters in ARGS as other
packages such as postgrey do.

-- System Information:
Debian Release: 8.7
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages postfwd depends on:
ii  adduser 3.113+nmu3
ii  libnet-dns-perl 0.81-2+deb8u1
ii  libnet-server-perl  2.008-1
ii  perl5.20.2-3+deb8u6

postfwd recommends no packages.

postfwd suggests no packages.

-- Configuration Files:
/etc/default/postfwd changed [not included]

-- no debconf information

Bug#833111: otrs2: use init system for starting otrs.Daemon.pl

2016-07-31 Thread Sven Strickroth 
Package: otrs2
Version: 5.0.10-1~bpo8+1
Severity: minor

Dear Maintainer,

right now the OTRS daemon (otrs.Daemon.pl) is started using cron. This leads
to restarting issues in combination with the needrestart tool which says that
cron needs to be restarted after perl (security) updates, but restarting it
doesn't help as otrs.Daemon.pl is not restarted. Only killing otrs.Daemon.pl
manually solves the issue and makes sure that the daemon is restarted.

Therefore, why not use the initsystem for starting/stopping the ORTS
daemon?

-- System Information:
Debian Release: 8.5
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

-- Configuration Files:
/etc/apache2/conf-available/otrs2.conf [Errno 13] Permission denied: 
u'/etc/apache2/conf-available/otrs2.conf'

-- debconf information excluded

Bug#784282: davical: Sync not working after upgrading from wheezy to jessie on iOS

2015-05-04 Thread Sven Strickroth 
Package: davical
Version: 1.1.3.1-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***
I just upgraded from wheezy to jessie and now syncing with iOS devices such
as iPhones does not fully work any more.

Creating and removing VEVENTS on the iPhone works. When I delete an event
created on a iPhone on another device, e.g. in Lighning, the event never
vanishes from the iPhone (but on all other Lighning instances).

When I include "$c->hide_TODO = false;" into my existing config, it works
again. However, the old events (created on iPhone, but deleted somewhere
else) stay on the iPhone (I can deleted these manually on the iPhone, but I
think these should "disappear" automatically as those at not in the DB any
more).

-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages davical depends on:
ii  libawl-php 0.55-1
ii  libdbd-pg-perl 3.4.2-1
ii  libyaml-perl   1.13-1
ii  perl   5.20.2-3
ii  php5   5.6.7+dfsg-1
ii  php5-cli   5.6.7+dfsg-1
ii  php5-pgsql 5.6.7+dfsg-1
ii  postgresql-client  9.4+165
ii  postgresql-client-9.4 [postgresql-client]  9.4.1-1

Versions of packages davical recommends:
ii  php5-curl   5.6.7+dfsg-1
ii  postgresql  9.4+165

Versions of packages davical suggests:
ii  php5-ldap  5.6.7+dfsg-1

-- 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#778871: opendkim: /etc/default/opendkim should allow to specify permissions for socket

2015-02-20 Thread Sven Strickroth 
Package: opendkim
Version: 2.6.8-4
Severity: wishlist

Dear Maintainer,

when using a local socket for communication with opendkim milter the
"opendkim" user and "opendkim" group are used as owner and group of the
socket. Other milters such as amavisd-milter allow to configure special
permissions for the socket which are applied in the init-script (e.g.
/etc/init.d/amavid-milter). Right now only the umask can be adjusted
in /etc/opendkim.conf.

Take amavisd-milter which has the following options in 
/etc/default/amavid-milter:

# Set these two options if you want the socket to have
# special permissions (usefull mainly for postfix).
MILTERSOCKETOWNER="postfix:postfix"
MILTERSOCKETMODE="0660"

Having something like this in opendkim would be nice in order to be able
to set permissions to sockets in a more fine-grained manner w/o the need
to add the "postfix" user to other groups or using other workarounds.

PS: This also applies to "unstable: 2.9.2-2"

-- System Information:
Debian Release: 7.8
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages opendkim depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.13-38+deb7u7
ii  libdb5.15.1.29-5
ii  libldap-2.4-2   2.4.31-1+nmu2
ii  liblua5.1-0 5.1.5-4+deb7u1
ii  libmilter1.0.1  8.14.4-4
ii  libopendkim72.6.8-4
ii  libssl1.0.0 1.0.1e-2+deb7u14
ii  libunbound2 1.4.17-3+deb7u2
ii  libvbr2 2.6.8-4
ii  lsb-base4.1+Debian8+deb7u1

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.6.8-4

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

-- 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#706491: awstats: update.sh is not logrotate compatible

2013-04-30 Thread Sven Strickroth 
Package: awstats
Version: 6.9.5~dfsg-5
Severity: normal

/usr/share/awstats/tools/update.sh is automatically executed by cron, but
when the logfiles are rotated the timespan between the last execution time
and the current time is missing in the statistics.

This becomes a major issue if people increase the cron interval.

A possible solution is to use a wrapper script for the logfiles (see
attached getlogs.pl). This script can be used by prepending it to Logfile in
/etc/awstats/awstats.conf (e.g. LogFile="getlogs.pl 
/var/log/apache2/access.log")
and getlogs.pl will use access.log.1 and access.log by default.

The very same script can also be used in order to create stats for all
existing rotated log files by using "all" as a second cli parameter or
setting USELOGFILES='all'. The current behavior can be emulated by using
'current' as the second cli parameter.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
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 awstats depends on:
ii  perl   5.10.1-17squeeze6 Larry Wall's Practical Extraction 

Versions of packages awstats recommends:
ii  coreutils 8.5-1  GNU core utilities
ii  libnet-xwhois-perl0.90-3 Whois Client Interface for Perl5

Versions of packages awstats suggests:
ii  apache2   2.2.16-6+squeeze11 Apache HTTP Server metapackage
ii  apache2-mpm-worker [h 2.2.16-6+squeeze11 Apache HTTP Server - high speed th
pn  libgeo-ipfree-perl (no description available)
pn  libnet-dns-perl(no description available)
pn  libnet-ip-perl (no description available)
pn  liburi-perl(no description available)

-- no debconf information
#!/usr/bin/perl
##
## getlogs.pl, written by Sven Strickroth  (2013)
##
## Provides (possible rotated) logfiles to awstats
##

use strict;
use File::Basename;

if ($#ARGV + 1 < 1 || $#ARGV > 1 || !$ARGV[0]) {
  print "Call this with ".$0." logfilename [CURRENTLAST|CURRENT|ALL|LAST]\n";
  print "\n";
  print "If the second parameter is omitted CURRENTLAST (or the content of the environment\n";
  print "variable USELOGFILES will be used) will be used by default (i.e. logfilename.1 and\n";
  print "logfilename will be printed).\n";
  exit 1;
}

my $path = dirname($ARGV[0]);
my $baselogfilename = basename($ARGV[0]);

die('Logfile path does not exist: ' . $path . "\n") unless (-d $path);

$ARGV[1] = $ENV{'USELOGFILES'} if ($ARGV[1] eq '');

if (lc($ARGV[1]) eq 'last') {
 if (-f $ARGV[0] . '.1') {
   &catFile($ARGV[0] . '.1');
 } elsif (-f $ARGV[0] . '.1.gz') {
   &catFile($ARGV[0] . '.1.gz');
 }
} elsif (lc($ARGV[1]) eq 'all') {
  opendir(my $dirh, $path) or die ("could not list $path\n");
  my @dir = readdir($dirh);
  closedir($dirh);
  @dir = grep {$_ =~ /^$baselogfilename/} @dir;
  my $filenamelen = length($baselogfilename) + 1;
  # order by number reversed
  @dir = reverse sort {substr($a, $filenamelen) <=> substr($b, $filenamelen)} @dir;
  foreach my $entry (@dir) {
&catFile($path . '/' . $entry);
  }
} elsif (lc($ARGV[1]) eq 'current') {
  &catFile($ARGV[0]);
} else {
 if (-f $ARGV[0] . '.1') {
   &catFile($ARGV[0] . '.1');
 }
 elsif (-f $ARGV[0] . '.1.gz') {
   &catFile($ARGV[0] . '.1.gz');
 }
 if (-f $ARGV[0]) {
  &catFile($ARGV[0]);
 }
}
exit 0;

sub catFile() {
  my ($file) = @_;
  if ($file =~ /\.gz$/) {
   open(my $fh, "gunzip < $file |") or die("could not open $file\n");
   while (<$fh>) {
 print $_;
   }
   close($fh);
  } else {
   open(my $fh, "<", $file) or die("could not open $file\n");
   while (<$fh>) {
 print $_;
   }
   close($fh);
  }
}

Bug#706487: patch updated

2013-04-30 Thread Sven Strickroth 
Hi,

find an updated patch attached.

-- 
Best regards,
 Sven Strickroth
 PGP key id F5A9D4C4 @ any key-server
--- orig/buildstatic.sh	2010-12-23 23:59:06.0 +0100
+++ new/buildstatic.sh	2013-04-30 21:35:59.0 +0200
@@ -1,10 +1,39 @@
-#!/bin/sh
+#!/bin/bash
 ##
 ## buildstatic.sh, written by Sergey B Kirpichev 
+## extended by Sven Strickroth 
 ##
 ## Build all static html reports from AWStats data (Debian specific)
 ##
 
+function generateStaticPagesForSpecificMonth {
+	YEAR=$1
+	MONTH=$2
+	for c in `/bin/ls -1 awstats.*.conf 2>/dev/null | \
+			  /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'` awstats
+	do
+	  mkdir -p /var/cache/awstats/$c/$YEAR/$MONTH/
+
+	  if ! nice -n $AWSTATS_NICE $BUILDSTATICPAGES \
+		-config=$c \
+		-year=$YEAR \
+		-month=$MONTH \
+		-lang=$AWSTATS_LANG \
+		-staticlinksext=${AWSTATS_LANG}.html \
+		-dir=/var/cache/awstats/$c/$YEAR/$MONTH/ >$ERRFILE 2>&1
+	  then
+		cat $ERRFILE >&2 # an error occurred
+	  fi
+	done
+}
+
+function generateStaticPages {
+	if [[ `date +%d` == 01 ]]; then
+		generateStaticPagesForSpecificMonth `perl -e '@date = localtime(time()-(24*3600)); $date[5]+=1900; print $date[5];'` `perl -e '@date = localtime(time()-(24*3600)); ++$date[4]; if ($date[4] < 10){$date[4]="0".$date[4];} print $date[5];'`
+	fi
+	generateStaticPagesForSpecificMonth `date +%Y` `date +%m`
+}
+
 set -e
 
 DEFAULT=/etc/default/awstats
@@ -28,19 +57,4 @@
 
 cd /etc/awstats
 
-for c in `/bin/ls -1 awstats.*.conf 2>/dev/null | \
-  /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'` awstats
-do
-  mkdir -p /var/cache/awstats/$c/$YEAR/$MONTH/
-
-  if ! nice -n $AWSTATS_NICE $BUILDSTATICPAGES \
--config=$c \
-	-year=$YEAR \
-	-month=$MONTH \
-	-lang=$AWSTATS_LANG \
-	-staticlinksext=${AWSTATS_LANG}.html \
-	-dir=/var/cache/awstats/$c/$YEAR/$MONTH/ >$ERRFILE 2>&1
-  then
-cat $ERRFILE >&2 # an error occurred
-  fi
-done
+generateStaticPages

Bug#706487: awstats: buildstatic.sh causes incomplete stats for last day of month

2013-04-30 Thread Sven Strickroth 
Package: awstats
Version: 6.9.5~dfsg-5
Severity: normal


Enable AWSTATS_ENABLE_BUILDSTATICPAGES in /etc/defaults/awstats (which is
enabled by default), /usr/share/awstats/tools/buildstatic.sh is executed
every day using cron (for me it's executed at 3:10).

When a new month begins (e.g. May, 1st) stats of the last day of the last
month (e.g. April, 30th) are incomplete (depending on when cron executes
the script). In my case the stats of the last day (April, 30) is only
available up to 3:10 the rest of the day is missing.

I've attached patch fixing this issue.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
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 awstats depends on:
ii  perl   5.10.1-17squeeze6 Larry Wall's Practical Extraction 

Versions of packages awstats recommends:
ii  coreutils 8.5-1  GNU core utilities
ii  libnet-xwhois-perl0.90-3 Whois Client Interface for Perl5

Versions of packages awstats suggests:
pn  apache2 | httpd(no description available)
pn  libgeo-ipfree-perl (no description available)
pn  libnet-dns-perl(no description available)
pn  libnet-ip-perl (no description available)
pn  liburi-perl(no description available)

-- no debconf information
--- /usr/share/awstats/tools/buildstatic.sh.orig2010-12-23 
23:59:06.0 +0100
+++ /usr/share/awstats/tools/buildstatic.sh 2013-04-30 21:20:08.0 
+0200
@@ -1,10 +1,37 @@
-#!/bin/sh
+#!/bin/bash
 ##
 ## buildstatic.sh, written by Sergey B Kirpichev 
 ##
 ## Build all static html reports from AWStats data (Debian specific)
 ##
 
+function generateStaticPagesForSpecificMonth {
+   for c in `/bin/ls -1 awstats.*.conf 2>/dev/null | \
+ /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'` awstats
+   do
+ mkdir -p /var/cache/awstats/$c/$YEAR/$MONTH/
+
+ if ! nice -n $AWSTATS_NICE $BUILDSTATICPAGES \
+   -config=$c \
+   -year=$YEAR \
+   -month=$MONTH \
+   -lang=$AWSTATS_LANG \
+   -staticlinksext=${AWSTATS_LANG}.html \
+   -dir=/var/cache/awstats/$c/$YEAR/$MONTH/ >$ERRFILE 2>&1
+ then
+   cat $ERRFILE >&2 # an error occurred
+ fi
+   done
+}
+
+function generateStaticPages {
+if [[ `date +%d` == 01 ]]; then
+generateStaticPagesForSpecificMonth `perl -e '@date = 
localtime(time()-(24*3600)); $date[5]+=1900; print $date[5];'` `perl -e '@date 
= localtime(time()-(24*3600)); ++$date[4]; if ($date[4] < 
10){$date[4]="0".$date[4];} print $date[5];'`
+fi
+generateStaticPagesForSpecificMonth `date +%Y` `date +%m`
+}
+
+
 set -e
 
 DEFAULT=/etc/default/awstats
@@ -28,19 +55,4 @@
 
 cd /etc/awstats
 
-for c in `/bin/ls -1 awstats.*.conf 2>/dev/null | \
-  /bin/sed 's/^awstats\.\(.*\)\.conf/\1/'` awstats
-do
-  mkdir -p /var/cache/awstats/$c/$YEAR/$MONTH/
-
-  if ! nice -n $AWSTATS_NICE $BUILDSTATICPAGES \
--config=$c \
-   -year=$YEAR \
-   -month=$MONTH \
-   -lang=$AWSTATS_LANG \
-   -staticlinksext=${AWSTATS_LANG}.html \
-   -dir=/var/cache/awstats/$c/$YEAR/$MONTH/ >$ERRFILE 2>&1
-  then
-cat $ERRFILE >&2 # an error occurred
-  fi
-done
+generateStaticPages

Bug#512410: libpam-mount: another segfault with cifs

2009-07-01 Thread Sven Strickroth 
Package: libpam-mount
Version: 0.44-1+lenny3
Followup-For: Bug #512410

In my network ldap is used to resolve groups and users...

taken from /etc/security/pam_mount.conf.xml:


With an up2date system and libpam-mount from lenny the error now is:
sshd[32664]: segfault at cb6ccd44 ip b3925ea9 sp bf1cc804 error 5 in 
libc-2.7.so[b38b7000+155000]
sshd[1692]: segfault at d546151c ip b5e20ea9 sp bf554e04 error 5 in 
libc-2.7.so[b5db2000+155000]
sshd[1688]: segfault at bcba1e04 ip aa17aea9 sp b7d38454 error 4 in 
libc-2.7.so[aa10c000+155000]

After upgrading libpam-mount to 1.10-1 (taken from sid) the bug seems not to 
occour any more. So I assume it is in 0.44-1+lenny3.

The following data is based on the system before the libpam-mount upgrade:

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

Kernel: Linux 2.6.29.4-grsec (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/bash

Versions of packages libpam-mount depends on:
ii  libc6   2.7-18   GNU C Library: Shared libraries
ii  libhx13 1.18-1A library providing queue, tree, I
ii  libpam0g1.0.1-5+lenny1   Pluggable Authentication Modules l
ii  libssl0.9.8 0.9.8g-15+lenny1 SSL shared libraries
ii  libxml2 2.6.32.dfsg-5GNOME XML library
ii  mount   2.13.1.1-1   Tools for mounting and manipulatin

libpam-mount recommends no packages.

Versions of packages libpam-mount suggests:
pn  cryptsetup (no description available)
pn  davfs2 (no description available)
ii  fuse-utils  2.7.4-1.1Filesystem in USErspace (utilities
ii  lsof4.78.dfsg.1-4List open files
pn  ncpfs  (no description available)
ii  openssl 0.9.8g-15+lenny1 Secure Socket Layer (SSL) binary a
ii  psmisc  22.6-1   Utilities that use the proc filesy
ii  smbfs   2:3.2.5-4lenny6  mount and umount commands for the
pn  truecrypt | truecrypt-u(no description available)
pn  xfsprogs   (no description available)

-- debconf information:
* libpam-mount/convert-xml-config: true



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

Bug#512410: openssh-server: sshd segfaults (suppose libc or libpam-mount related)

2009-01-20 Thread Sven Strickroth 
Package: openssh-server
Version: 1:5.1p1-5
Severity: normal

==> /var/log/syslog <==
Jan 20 11:14:36 x2goserver kernel: [12969.745101] sshd[31465]: segfault at 
6fd7cbec ip b7af7ea9 sp bfa5b2e4 error 4 in libc-2.7.so[b7a89000+155000]
Jan 20 11:14:40 x2goserver modprobe: WARNING: Not loading blacklisted module 
ipv6
Jan 20 11:14:52 x2goserver kernel: [12988.077088] sshd[31518]: segfault at 
7126cbec ip b7b16ea9 sp bfa79b04 error 4 in libc-2.7.so[b7aa8000+155000]
Jan 20 11:14:57 x2goserver kernel: [12993.564945] sshd[31532]: segfault at 
715fbbec ip b7acdea9 sp bfc32cb4 error 4 in libc-2.7.so[b7a5f000+155000]
Jan 20 11:15:14 x2goserver kernel: [13011.537760] sshd[31615]: segfault at 
7143bbec ip b7b91ea9 sp bfaf6b74 error 4 in libc-2.7.so[b7b23000+155000]
Jan 20 11:15:36 x2goserver kernel: [13036.492617] sshd[31591]: segfault at 
7007dbec ip b7b71ea9 sp bfcd6d54 error 4 in libc-2.7.so[b7b03000+155000]
Jan 20 11:15:37 x2goserver kernel: [13038.017398] sshd[31713]: segfault at 
70dc8bec ip b7af0ea9 sp bfa53ad4 error 4 in libc-2.7.so[b7a82000+155000]

Jan 20 16:22:16 x2goserver kernel: [33193.561581] sshd[7955]: segfault at 
718a20e4 ip b7b60ea9 sp bffc5fd4 error 4 in libc-2.7.so[b7af2000+155000]
Jan 20 16:22:16 x2goserver kernel: [33193.562936] sshd[7959]: segfault at 
70ee273c ip b7acbea9 sp bfd30d44 error 4 in libc-2.7.so[b7a5d000+155000]



==> /var/log/auth <==
Jan 20 16:32:44 x2goserver sshd[8604]: Closing connection to 192.168.X.Y port 
1944
Jan 20 16:32:44 x2goserver sshd[8590]: debug1: PAM: cleanup
Jan 20 16:32:44 x2goserver sshd[8590]: debug1: PAM: deleting credentials
Jan 20 16:32:44 x2goserver sshd[8590]: debug1: PAM: closing session
Jan 20 16:32:44 x2goserver sshd[8590]: pam_unix(sshd:session): session closed 
for user test

==> /var/log/syslog <==
Jan 20 16:32:44 x2goserver kernel: [33878.085181] sshd[8590]: segfault at 
7171de1c ip b7b05ea9 sp bf86a8f4 error 4 in libc-2.7.so[b7a97000+155000]

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

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

Versions of packages openssh-server depends on:
ii  adduser   3.110  add and remove users and groups
ii  debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii  dpkg  1.14.24Debian package management system
ii  libc6 2.7-18 GNU C Library: Shared libraries
ii  libcomerr21.41.3-1   common error description library
ii  libkrb53  1.6.dfsg.4~beta1-5 MIT Kerberos runtime libraries
ii  libpam-modules1.0.1-5Pluggable Authentication Modules f
ii  libpam-runtime1.0.1-5Runtime support for the PAM librar
ii  libpam0g  1.0.1-5Pluggable Authentication Modules l
ii  libselinux1   2.0.65-5   SELinux shared libraries
ii  libssl0.9.8   0.9.8g-15  SSL shared libraries
ii  libwrap0  7.6.q-16   Wietse Venema's TCP wrappers libra
ii  lsb-base  3.2-20 Linux Standard Base 3.2 init scrip
ii  openssh-blacklist 0.4.1  list of default blacklisted OpenSS
ii  openssh-client1:5.1p1-5  secure shell client, an rlogin/rsh
ii  procps1:3.2.7-9  /proc file system utilities
ii  zlib1g1:1.2.3.3.dfsg-12  compression library - runtime

Versions of packages openssh-server recommends:
ii  openssh-blacklist-extra   0.4.1  list of non-default blacklisted Op
ii  xauth 1:1.0.3-2  X authentication utility

Versions of packages openssh-server suggests:
pn  molly-guard(no description available)
pn  rssh   (no description available)
pn  ssh-askpass(no description available)

-- debconf information:
  ssh/vulnerable_host_keys:
  ssh/new_config: true
* ssh/use_old_init_script: true
  ssh/encrypted_host_key_but_no_keygen:
  ssh/disable_cr_auth: false



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