Package: ipmitool
Version: 1.8.19-4
Severity: normal
Tags: patch upstream
Dear Maintainer,
Upstream version of ipmitool contains an unresolved issue:
https://github.com/ipmitool/ipmitool/issues/388
Personally seen this on an iLo4 BMC:
~# ipmitool -v lan print
Loading IANA PEN Registry...
IANA
Stan,
> did you change it in "ldap.conf" on client machine or within application
> settings? I've tried with
>
> TLS_CIPHER_SUITE -SECURE256
>
> in "/etc/ldap/ldap.conf" on client, but it ends with calltrace:
> http://paste.debian.net/396314/
We changed it in the application settings. In our
Hi Stan,
> are there any news how to fix this problem? I've added "TLSCipherSuite
> NORMAL:!ARCFOUR-128:!3DES-CBC:-VERS-SSL3.0" to my slapd.conf on LDAP server,
> but it didn't change a
> thing.
In our case, we had to allow more ciphers on the client side. Not on
the server side. The client
On Wed, Jan 20, 2016 at 11:10 AM, Frederic Van Espen
<frederic.van.es...@escaux.com> wrote:
> I should add that running ldapsearch works fine though:
Also, we have this in our configuration file:
tls_cipher_suite = SECURE256
When I comment that it seems to work fine. Before the upgrade
On Wed, Jan 20, 2016 at 10:59 AM, Frederic Van Espen
<frederic.van.es...@escaux.com> wrote:
> We're connecting to LDAP from postfix. Here's the postmap debugging output:
> postmap: dict_ldap_debug: TLS: can't connect: The signature algorithm is not
> supported..
&
Hi,
On Thu, 14 Jan 2016 23:49:54 0100 Christoph Schindler
wrote:
> The problem seems to have to do with a self-signed root certificate that
uses MD5 (as the root cert from cacert.org does) for its signature.
Started getting this same issue yesterday after upgrading gnutls on
Package: openvpn-auth-ldap
Version: 2.0.3-5.1
Severity: normal
Tags: upstream patch
Dear Maintainer,
I stumbled accross this issue while setting up ldap authentication for
openvpn:
https://code.google.com/p/openvpn-auth-ldap/issues/detail?id=7
I have included a patch that fixes this issue for
Hi,
We hit this as well today. We upgraded from squeeze to wheezy. Windows
clients were still able to print normally, but samba clients were not,
failing with the error message NT_STATUS_ACCESS_DENIED opening remote
spool
Adding use client drivers = yes to smb.conf fixed the issue for samba
On 08/07/2013 08:01 PM, Guillem Jover wrote:
I tested now with 1.14.x just to confirm my suspicion, and there it
does not work either, so I don't really see how this has ever worked
for you. Lowering to wishlist.
Sorry, the part where it says it worked before was added automatically
by
Package: dpkg-dev
Version: 1.16.10
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
I have a package that has the following content in the
debian/source/include-binaries
debian/extra/foo.so
However, when running dpkg-source this
On 07/05/2013 10:40 AM, Roger Leigh wrote:
Could you possibly let me know where that needs putting (probably
somewhere in 05lvm) and I'll look at adding this.
I actually just applied the patch proposed by Daniel who created this
bugreport.
dmsetup resume is necessary when the bug is
Package: schroot
Version: 1.6.4-4
Followup-For: Bug #674682
Dear Maintainer,
I also see this on a clean installed wheezy system. It randomly happens
when a build has completed.
It seems to be related to
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659762
I can indeed get out of the
We are seeing this as well on a build server where the LVM volumes are
managed by sbuild. Randomly the snapshots cannot be removed by sbuild
when the build is done and all the lv* commands hang forever. This
happens several times per day so it is quite easily reproducible
The only way around this
On Mon, Oct 14, 2012 at 12:43:43 +0200, Kees de Jong wrote:
In the attachment is a messages log, the system froze right after I
logged into the Gnome-shell. Maybe you see something out of the
ordinary? The Xorg logs don't show anything, to me it seems that the
logging just stops when it
Package: debconf-doc
Version: 1.5.46
Severity: normal
Hi,
The debconf documentation does not specify how to correctly use multiple
capabilities in the protocol. I figured out by trial and error that when
using the perl ConfModule, they should be separated by spaces:
my $capb=capb('backup
firmware files for
my wireless card.
Removing the line above from /etc/fstab resolved the issue for me.
Plugging in an external usb drive automatically mounts now.
Hope this helps someone else out.
Cheers,
Frederic
On 02/10/2011 06:19 PM, Frederic Van Espen wrote:
I seem to be running
I seem to be running into the same issue as Christian. Upon plugging in
a ntfs usb disk I get the same gnome window that pops up:
Error mounting: mount exited with exit code 1: helper failed with:
Error opening '/dev/sdb1': Permission denied
Failed to mount '/dev/sdb1': Permission denied
Please
17 matches
Mail list logo