amd64 3.0.17+dfsg-1.1
2020-12-17 14:14:33 status installed freeradius-ldap:amd64 3.0.17+dfsg-1.1
--
Harald Hannelius | harald.hannelius/a\arcada.fi | +358 50 594 1020
On Mon, 21 Dec 2020, Bernhard Schmidt wrote:
Am 21.12.20 um 10:21 schrieb Harald Hannelius:
Hi Harald,
I have a recursive diff of both config dirs, but haven't been
able to see what has done what. I still have a test-server so
I can help with providing more info is so needed.
P
On Fri, 18 Dec 2020, Bernhard Schmidt wrote:
Earlier Harald Hannelius wrote:
I have a recursive diff of both config dirs, but haven't been
able to see what has done what. I still have a test-server so
I can help with providing more info is so needed.
Please attach the diff to thi
bug report.
I will, I have to sanitize it a bit first.
--
Harald Hannelius | harald.hannelius/a\arcada.fi | +358 50 594 1020
Package: freeradius
Version: 3.0.17+dfsg-1.1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I upgraded debian 9 to debian 10, this upgrading freeradius-3.0.12 to
freeradius-3.0.17
at the
he user doesn't know the correct name for the interface at
that stage, it might be ens3, eth0, wlan0, eno1, wlp1s3 or something else.
I can't remember when I have had to add the interface name to the gateway
since this configuration is usually added in the context of the interface
being
Package: debian-installer
Version: Debian 10.6
Severity: normal
Dear Maintainer,
I needed to enter an IPv6-address in the installer. When entering
fe80::1 as a gateway the installer stops with an error that the
address isn't reachable. The address fe80::1 is indeed a valid
address for a gateway.
Package: iftop
Version: 1.0~pre4-4
Severity: minor
Dear Maintainer,
When running iftop on a server with serveral IPv6-connections ongoing,
iftop seems to resolve the ip-addresses to the same hostname. This is a
bit confusing. By pressing 'n' to get numerical output everything looks
correct.
--
It seems like a restart of mimedefang was needed after an upgrade of
spamassassin (and spamd). It might be the spamassassin package's
responsibility to do that?
--
Harald Hannelius | harald.hannelius/a\arcada.fi | +358 50 594 1020
Package: mimedefang
Version: 2.79-2
Severity: grave
Justification: causes non-serious data loss
Dear Maintainer,
There was an update on spamassassin two days ago, that updated to
3.4.2-1~deb9u2 on both
our incoming gateways. Both are debian 9, and both are also using mimedefang.
Both now
cau
On Mon, 29 Apr 2019, Frederic Peters wrote:
Harald Hannelius wrote:
I forgot to mention that installing of liblasso3 from stretch backports also
fixes the problem and I can operate as an SP and sign requests.
Good to know as there's an important diff between 2.5.0 and 2.6.0
On Mon, 29 Apr 2019, Frederic Peters wrote:
fixed 928164 2.6.0-2
thanks
Will this dribble down to Debian Stretch?
--
Harald Hannelius | har...@iki.fi | +358505941020
I forgot to mention that installing of liblasso3 from stretch backports
also fixes the problem and I can operate as an SP and sign requests.
--
Harald Hannelius | har...@iki.fi | +358505941020
Package: liblasso3
Version: 2.5.0-5+b1
Severity: important
Dear Maintainer,
I installed liblasso3 (a requirement for mod_auth_mellon). Configured to use
ADFS
as authsource. When signing of claims is enabled liblasso3 dies with signal 11
sigsegv.
If I disable signing of claims everything wor
A record
Many thanks to Stuart D. Gathman for pointing this out to me.
--
Harald Hannelius | harald.hannelius/a\arcada.fi | +358 50 594 1020
A record
Many thanks to Stuart D. Gathman for pointing this out to me.
--
Harald Hannelius | harald.hannelius/a\arcada.fi | +358 50 594 1020
Package: spf-milter-python
Version: 0.8.18-2
Severity: grave
Tags: ipv6
Justification: causes non-serious data loss
Dear Maintainer,
I noted that when someone at mdh.se tries to send e-mail to us, and the
connection is from
an IPv6-address (almost all connections are these days), spf-milter-pyt
Package: spfquery
Version: 1.2.10-7+b2
Severity: grave
Tags: ipv6
Justification: causes non-serious data loss
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I got notified that another organization was unable to
I was about to file a bug as well, since I just got a lot of e-mail from
different cron-daemons. The normal convention would be to not say anything
if there isn't anything to tell, wouldn't it?
At the very least don't output a single newline.
--
A: Top Posters!
This bug is still present in a freshly installed squeeze 64bit 6.0.4 at
7th Mar 2012.
The line-number has changed, but the typo it still there.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or
On Fri, 7 Mar 2008, Steve Langasek wrote:
On Thu, Mar 06, 2008 at 10:38:51AM +0200, Harald Hannelius wrote:
Windows XP SP2 client, logged on to samba domain. When copying a file
from the Samba-server download speed is terrible, estimate 10-15 minutes
for a ~150MB file.
Connectivity
Package: samba
Version: 3.0.24-6etch9
Severity: important
Etch server running samba (amd64) as domain member. SMP.
Windows XP SP2 client, logged on to samba domain. When copying a file
from the Samba-server download speed is terrible, estimate 10-15 minutes
for a ~150MB file.
Connectivity be
22 matches
Mail list logo
