Sheesh, my bad. Thanks :)
--srs (htc one x)
- Reply message -
From: "C. Meissa"
To: "Suresh Ramasubramanian"
Cc: <732...@bugs.debian.org>
Subject: Bug#732259: Acknowledgement (mutt: Special character in the
recipient's display name overrides my name c
Forgot to addthe relevant bits from my .muttrc -
set reverse_name
set from=sur...@hserus.net
alternates "s...@savitr.info"
srs
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 12-Sep-2013, at 1:18, Florian Weimer wrote:
> I suppose the simplest mitigation would be to avoid ephemeral
> Diffie-Hellman key agreement altogether, that is, remove it from the
> cipher suite default.
By the way this ticket is a dup of #676563
--srs
--
To UNSUBSCRIBE, email to debian-bu
On 12-Sep-2013, at 1:18, Florian Weimer wrote:
> I suppose the simplest mitigation would be to avoid ephemeral
> Diffie-Hellman key agreement altogether, that is, remove it from the
> cipher suite default.
Dispensing with gnutls and using openssl like most other distros do would
possibly make m
Package: exim4
Version: 4.80-7
Followup-For: Bug #684340
This issue is still around in 4.80-7 on wheezy.
Longish thread on postfix-users as well, with an exim developer (Phil Pennock)
discussing this bug with Wietse and Viktor Dukhovni.
66_enlarge-dh-parameters-size.dpatch in gnutls is the issue
Package: exim4
Version: 4.72-6
Severity: normal
Exim wrongly interprets % in a dkim sig, and logs to the paniclog
This issue has been reported upstream to the exim maintainers and a fix pushed
http://bugs.exim.org/show_bug.cgi?id=1106
thanks
--srs
-- Package-specific info:
Exim version 4.72 #
Marc Haber [24/01/10 16:36 +0100]:
It is not necessary to modify the init script to override these
settings, just override them from /etc/default/exim4.
Which I did, already once I remembered. Didnt modify the initscript back to
the default though. Both those files say 15m now.
--
To UNSUBSC
Andreas Metzler [24/01/10 16:11 +0100]:
On 2010-01-12 Suresh Ramasubramanian wrote:
Package: exim4-daemon-heavy
Version: 4.71-3
Severity: important
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy
[...]
Was this a dist-upgrade from lenny?
nope. fresh squeeze install. the
Andreas Metzler [24/01/10 16:18 +0100]:
Ok. Would you mind sending it to the bts, so we have a complete file
when I re-assign to insserv.
Below. Only change is QUEUEINTERVAL was changed to 15m from the default 30m
srs
#! /bin/sh
# /etc/init.d/exim4
#
# Written by Miquel van Smoorenbur
/etc/init.d/exim4 was only modified to make the queue interval 15m instead
of 30m.
What I did next was to execute "update-rc.d exim4 default" and it seems to
have stopped throwing that error. Strange.
Andreas Metzler [24/01/10 15:58 +0100]:
On 2010-01-12 Suresh Ramasubramanian wrote
* Marc Haber [Tuesday, 12 January 2010 3:58 PM]:
> On Mon, Jan 11, 2010 at 10:01:29PM -0800, Suresh Ramasubramanian wrote:
>> Setting up exim4-base (4.71-3) ...
>> Installing new version of config file /etc/cron.daily/exim4-base ...
>> insserv: warning: current start runlevel
Package: exim4-daemon-heavy
Version: 4.71-3
Severity: important
Doing an apt-get dist-upgrade to the latest exim4-daemon-heavy I got these
warnings, and then exim4 did not restart automatically. /etc/init.d/exim4 start
did start it after that.
Setting up exim4-base (4.71-3) ...
Installing new ver
> Having a compromised key in ~/.ssh/authorized_keys (if that's what it
> was) is effectively equivalent to allowing access to that account from
> the entire Internet.
Obviously. Which is why I found it. Removed it. Told him to reupload it.
He seems to have uploaded a new compromised key. Told him
Colin Watson [31/05/08 00:31 +0100]:
Sure, but that's a problem with *their* machine (i.e. it allows access
from unauthorised persons) rather than a problem with your machine. The
sshd blacklisting will prevent this problem on their side - you might
send them an updated key but you won't be able
14 matches
Mail list logo
