[MailServer Notification]Attachment Blocking Notification
The crypt-decrypt.pl has been blocked, and Quarantine entire message has been taken on 14/03/2006 20:43:18. Message details: Server:CORREO Sender: [EMAIL PROTECTED]; Recipient:[EMAIL PROTECTED];debian-security@lists.debian.org; Subject:Serious bug in security update for Crypt::CBC Attachment name:crypt-decrypt.pl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Re: Re: Clear screen question
For the benefit of the readers, I found the original thread that I had replied to. And, I suppose my text appeared twice because that's how microsoft likes it. ;) I did try to set this email to plain text, hopefully it will only appear once now. Of all the days, it was on Sun, Jan 28, 2001 at 09:00:07AM -0600 that wes schreiner quoth: > "Sander Smeenk (CistroN Medewerker)" wrote: > > > > Quoting wes schreiner ([EMAIL PROTECTED]): > > > > > Not that I can see, though I'd love to know of a clean way to clear the > > > scroll-back buffer. I agree it's a bit hackish. Can anyone come up > > > with something better? > > > > Ehm.. I did this: > > > > knopje# echo -e "\033[2J\033[1;1H" > issue.new > > knopje# cat /etc/issue >> issue.new > > knopje# mv issue.new /etc/issue > > > > And now when i log out from consoles the screen clears and the scrollback > > buffer is empty.. The \0332J is ANSI for Clear Screen and \033[1;1H is ANSI > > for place cursor on x1 y1... > > > > Works for me... > > Tried it, but this only clears the immediately visible screen for me, > not the scroll-back buffer. I'm using mgetty, are you using mingetty or > some other *getty? Maybe that's the difference. If so, then Ethan's vt > switching method is better because it doesn't depend on the getty. > > These ANSI codes do only clear the screen when the user logs out, > which was the original question. At some point somebody interpreted it > to be about clearing the scrollback buffer, and things have been going > off on that tangent ever since. FWIW, I posted these ANSI codes about > two days ago and also noted that they don't work at all if you don't > have an ANSI terminal. I know this post is from 2001, but I figured out a way to do it in case someone reads it. do the lines that were suggested on knopje, but then vi /etc/issue or use your favorite editor and insert a ton of newlines before it. the filesize isn't very big and it clears the buffer. You may have to experiment with just how many newlines you need.
Re: No suitable pubkey ?
Thanks Mike :) 2006/3/14, Mike Hommey <[EMAIL PROTECTED]>: > On Tue, Mar 14, 2006 at 10:32:55PM +0100, DeMZed <[EMAIL PROTECTED]> wrote: > > Hi, > > > > When I launch apt-get update using http://ftp2.fr.debian.org, I get this > > since a while : > > > > W: GPG error: http://ftp2.fr.debian.org testing Release: Les signatures > > suivantes n'ont pas pu être vérifiées car la clé publique n'est pas > > disponible : NO_PUBKEY 010908312D230C5F > > W: GPG error: http://etc.inittab.org ./ Release: Les signatures suivantes > > n'ont pas pu être vérifiées car la clé publique n'est pas disponible : > > NO_PUBKEY C514AF8E4BA401C3 > > W: GPG error: http://security.debian.org stable/updates Release: Les > > signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est > > pas disponible : NO_PUBKEY 010908312D230C5F > > W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. > > > > If I translate, it says that public keys cannot be found. > > > > So if I do > > > > gpg --recv-keys 010908312D230C5F > (...) > > apt-get install debian-archive-keyring > > Mike >
Re: No suitable pubkey ?
On Tue, Mar 14, 2006 at 10:32:55PM +0100, DeMZed <[EMAIL PROTECTED]> wrote: > Hi, > > When I launch apt-get update using http://ftp2.fr.debian.org, I get this > since a while : > > W: GPG error: http://ftp2.fr.debian.org testing Release: Les signatures > suivantes n'ont pas pu être vérifiées car la clé publique n'est pas > disponible : NO_PUBKEY 010908312D230C5F > W: GPG error: http://etc.inittab.org ./ Release: Les signatures suivantes > n'ont pas pu être vérifiées car la clé publique n'est pas disponible : > NO_PUBKEY C514AF8E4BA401C3 > W: GPG error: http://security.debian.org stable/updates Release: Les > signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est > pas disponible : NO_PUBKEY 010908312D230C5F > W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. > > If I translate, it says that public keys cannot be found. > > So if I do > > gpg --recv-keys 010908312D230C5F (...) apt-get install debian-archive-keyring Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
No suitable pubkey ?
Hi, When I launch apt-get update using http://ftp2.fr.debian.org, I get this since a while : W: GPG error: http://ftp2.fr.debian.org testing Release: Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 010908312D230C5F W: GPG error: http://etc.inittab.org ./ Release: Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY C514AF8E4BA401C3 W: GPG error: http://security.debian.org stable/updates Release: Les signatures suivantes n'ont pas pu être vérifiées car la clé publique n'est pas disponible : NO_PUBKEY 010908312D230C5F W: Vous pouvez lancer « apt-get update » pour corriger ces problèmes. If I translate, it says that public keys cannot be found. So if I do gpg --recv-keys 010908312D230C5F I get this message : gpg: requête de la clé 2D230C5F du serveur hkp subkeys.pgp.net gpg: clé 2D230C5F: clé publique « Debian Archive Automatic Signing Key (2006) <[EMAIL PROTECTED]> » importée gpg: aucune clé de confiance ultime n'a été trouvée gpg:Quantité totale traitée: 1 gpg: importée: 1 Which says in summary that the imported key cannot be used because no "ultim trust key" cannot be found ; I've got the same kind for C514AF8E4BA401C3. Have you got any idea why it does this ? I saw something like, it this mailing list, on January. Is it linked ? Thanks a lot. DeMZed Here is my APT deb http://security.debian.org/ stable/updates main deb http://ftp2.fr.debian.org/debian/ stable main deb-src http://ftp2.fr.debian.org/debian/ stable main deb http://ftp2.fr.debian.org/debian/ testing main deb-src http://ftp2.fr.debian.org/debian/ testing main deb http://ftp2.fr.debian.org/debian/ unstable main deb-src http://ftp2.fr.debian.org/debian/ unstable main #DVD::RIP deb ftp://ftp.nerim.net/debian-marillat sarge main deb ftp://ftp.nerim.net/debian-marillat etch main deb ftp://ftp.nerim.net/debian-marillat sid main #libapache2-mod-security deb http://etc.inittab.org/~agi/debian/libapache-mod-security ./ #PHP5 deb http://people.debian.org/~dexter/ php5.1 sarge and my preferences : Package: * Pin: release a=testing Pin-Priority: 990 Package: * Pin: release a=unstable Pin-Priority: 99 ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international. Téléchargez sur http://fr.messenger.yahoo.com
Serious bug in security update for Crypt::CBC
Dear Martin,
From: Martin Schulze <[EMAIL PROTECTED]>
Reply-To: debian-security@lists.debian.org
To: Debian Security Announcements
Subject: [SECURITY] [DSA 996-1] New Crypt::CBC packages fix cryptographic
weakness
For the stable distribution (sarge) this problem has been fixed in
version 2.12-1sarge1.
I'm afraid this new package introduces some serious errors in software
that depends on this package. I have tested the new package on three
different Sarge machines with the following results. Please reproduce
using attached perl script.
It is the simplest of perl scripts and it functions correctly with
libcrypt-cbc-perl version 2.12-1:
[EMAIL PROTECTED]:~$ dpkg -l libcrypt-cbc-perl | grep '^ii'
ii libcrypt-cbc-p 2.12-1 Implementation of cipher block
[EMAIL PROTECTED]:~$ perl crypt-decrypt.pl
allard
[EMAIL PROTECTED]:~$
After the upgrade to libcrypt-cbc-perl version 2.12-1sarge1:
[EMAIL PROTECTED]:~$ sudo apt-get install libcrypt-cbc-perl=2.12-1sarge1
[..]
[EMAIL PROTECTED]:~$ dpkg -l libcrypt-cbc-perl | grep '^ii'
ii libcrypt-cbc-p 2.12-1sarge1 Implementation of cipher block
[EMAIL PROTECTED]:~$ perl crypt-decrypt.pl
[EMAIL PROTECTED]:~$
Please remove the update from the security archive.
Regards,
Allard Hoeve#!/usr/bin/perl
use strict;
use warnings;
use Crypt::CBC;
my $cbc = new Crypt::CBC({ key => "abcdefghi", cipher => "Blowfish" });
my $encrypted = $cbc->encrypt("allard");
undef $cbc;
$cbc = new Crypt::CBC({ key => "abcdefghi", cipher => "Blowfish" });
my $decrypted = $cbc->decrypt($encrypted);
print "$decrypted\n";
Re: Idea to secure ssh [was: howto block ssh brute-force]
On Mon, Mar 13, 2006 at 11:06:38PM -0500, Neal Murphy wrote:
The point is to obscure the ssh server from everyone, including those who are
authorized to access it remotely. The point is to reduce brute-forace attacks
to the point of nearly total ineffectiveness.
No more so than simply configuring ssh with decent passwords or public
key auth. These "brute force attacks" are succeeding with passwords like
"password" or "guest", not "[EMAIL PROTECTED](". IMO, it's a lot more
sensible to spend a little time preventing obviously poor system
configuration than to erect complicated workarounds for same.
You seem to have this belief that someone contacting an ssh server is,
in itself, bad. That's silly. At any rate, you seem enamoured of your
scheme. Have fun with it, but don't expect it to take of.
Are you saying that anyone can generate a data packet that will correctly
decode with *my* public key?
It doesn't matter for an attack aimed at your decryption routine.
Assuming that there are, and will never be, any vulnerability in the
crypto itself you've done nothing more than reimplement ssh's public key
auth in a byzantine fashion.
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Thank you for contacting Mcafee Technical Support.
* STARCH: > I have a Compaq 9.0 Security Edition SE XP 2000 and my firewall is blocking > my CallWave and some other items I attempt to download. What can I do to > correct this problem? debian-security@lists.debian.org is the wrong mailbox for this kind of question. We do not do Windows, and our products are not related to the CallWave service, either, despite what a popular search engine thinks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Idea to secure ssh [was: howto block ssh brute-force]
Neal Murphy said: > The point is to obscure the ssh server from everyone, including those who > are authorized to access it remotely. You're right, this is just the old idea of "security by obscurity". > The point is to reduce brute-forace attacks to the point of nearly total > ineffectiveness. The point is to require a small amount of > pre-authentication before the server acknowledges the client's attempt > to connect. How small can any _reliable_ authentication protocol be? Either it's at risk by brute-force or by denial-of-service. Michel -- $ rpm -q --whatrequires linux no package requires linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
