Your message dated Mon, 13 Oct 2008 23:14:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Most likely fixed, closing
has caused the Debian Bug report #234613,
regarding samba: smbd quits with "operation is not possible without initialized 
secure memory"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
234613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=234613
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: samba
Version: 3.0.2a-1
Severity: normal


Since last update each new forked smbd quits after successful
authentication without even closing connection. The client side smbmount
reports:

20081: session setup failed: Call returned zero bytes (EOF)
SMB connection failed

And the log contains just two lines:

[2004/03/18 23:58:44, 3] smbd/sec_ctx.c:push_sec_ctx(256)
  push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1
[2004/03/18 23:58:44, 3] smbd/uid.c:push_conn_ctx(287)
  push_conn_ctx(0) : conn_ctx_stack_ndx = 0
[2004/03/18 23:58:44, 3] smbd/sec_ctx.c:set_sec_ctx(288)
  setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
[2004/03/18 23:58:44, 5] auth/auth_util.c:debug_nt_user_token(486)
  NT user token: (NULL)
[2004/03/18 23:58:44, 5]
  auth/auth_util.c:debug_unix_user_token(505)
  UNIX token of user 0
  Primary group is 0 and contains 0 supplementary groups
operation is not possible without initialized secure memory
(you may have used the wrong program for this task)

Actually, libcrypt libraries contain this error message:

# strings /usr/lib/libgcrypt.so.7 | grep withou
operation is not possible without initialized secure memory
# strings /usr/lib/libgcrypt.so.1 | grep withou
operation is not possible without initialized secure memory
# 

But it seems it's a samba's task to initialize ths library properly. No
other package depending on libgcrypt1 or libgcrypt7 seems to be broken.

Please also note, that smbd is linked with both libgcrypt1 and
libgcrypt7:

# ldd /usr/sbin/smbd | grep gcrypt
 libgcrypt.so.1 => /usr/lib/libgcrypt.so.1 (0x40379000)
 libgcrypt.so.7 => /usr/lib/libgcrypt.so.7 (0x403dc000)
# 

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4-custom
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R

Versions of packages samba depends on:
ii  debconf [debconf-2.0]     1.4.16         Debian configuration management sy
ii  libacl1                   2.2.23-1       Access control list shared library
ii  libc6                     2.3.2.ds1-11   GNU C Library: Shared libraries an
ii  libcomerr2                1.35-3         The Common Error Description libra
ii  libcupsys2                1.1.20final-16 Common UNIX Printing System(tm) - 
ii  libgnutls7                0.8.12-5       GNU TLS library - runtime library
ii  libkrb53                  1.3.2-2        MIT Kerberos runtime libraries
ii  libldap2                  2.1.26-1       OpenLDAP libraries
ii  libpam-modules            0.76-15        Pluggable Authentication Modules f
ii  libpam-runtime            0.76-15        Runtime support for the PAM librar
ii  libpam0g                  0.76-15        Pluggable Authentication Modules l
ii  libpopt0                  1.7-4          lib for parsing cmdline parameters
ii  logrotate                 3.6.5-2        Log rotation utility
ii  netbase                   4.16           Basic TCP/IP networking system
ii  samba-common              3.0.2a-1       Samba common files used by both th

-- debconf information:
  samba/nmbd_from_inetd: 
  samba/log_files_moved: 
  samba/tdbsam: false
* samba/generate_smbpasswd: true
* samba/run_mode: daemons


--- End Message ---
--- Begin Message ---
As this report did not see any action for years and the last question by a 
maintainer for Debugger output was not replied to, I am closing this bug. 

Greetings, Torsten


--- End Message ---

Reply via email to