Re: creative ssh-agent uses
Dear Ratiu, I am not sure I understand your situation, but maybe this can help? When creating an ssh-key using ssh-keygen, it prompts you for a passphrase. It isn't so obvious, but you can simply hit return at that point to have "no passphrase". This means that the resulting key is unencrypted on your hard drive, so you have to rely on unix (chmod) permissions to protect it from being copied by unauthorized people. As long as you just press enter when asked for a passphrase from ssh-keygen, this will ensure that using that key with ssh-agent and ssh-add will not prompt you for a passphrase. This is one way to use ssh-agent with a script noninteractively. Just eval `ssh-agent`, ssh-add the unencrypted key, then do the ssh commands all without a passphrase prompt. I hope this information is useful to you. Best regards, Rudi -- Give AI a try with Data Compression using http://complearn.org/ today! Ratiu Petru wrote: > On Thu, 07 Dec 2006, Stefan Denker wrote: > > > On Mon, Dec 04, 2006 at 09:25:38PM +0200, Ratiu Petru wrote: > > > What I'm thinking is to provide a static string as a challenge and use the > > > response as the cryptodevice password, but I can't find a program that > > > allows me to manipulate the socket this way. This mechanism might also be > > > used for other purposes, stacking public key authentication in a "normal" > > > password-based login. > > > > I do not think this is a good idea. If the challenge is static, the > > response will be, too. Then you might be vulnerable to replay-Attacks. > > > I perfectly understand. However, I _need_ a static password for cryptsetup, > i just wanted to make it somehow dependent of the agent to skip prompting > for it in the backup script. I am aware of the fact that someone who knows > the password can mount the cryptsetup directly, I can't improve that. > > I found somewhere a script that was supposed to use ssh-agent like I wanted > to (encrypt stuff through it), but all it did was to crash my agent :) > > The gpg-agent is a nice idea too, but we already have an existing ssh > infrastructure and not all guys involved have gpg keys, so I'm trying to > avoid that if possible. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re:
Por favor enviar e-mails para [EMAIL PROTECTED] Please send mail to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Alexander Jäger is out of the office.
Ich werde abwesend sein Startdatum: 09.12.2006. Rückkehrdatum: 15.12.2006. Sehr geehrte Damen und Herren, ich bin vom 08.12.2006 bis einschließlich 15.12.2006 nicht im Büro erreichbar. Ihre E-Mails werde ich nach meiner Rückkehr bearbeiten. In dringenden Fällen wenden Sie sich bitte an [EMAIL PROTECTED] Ganz dringende Fälle können mich mobil erreichen.
Re: Bug#401969: please build using hunspell
On Fri, Dec 08, 2006 at 10:58:11PM +0100, Rene Engelhard <[EMAIL PROTECTED]> wrote: > Mike Hommey wrote: > > On Thu, Dec 07, 2006 at 11:26:34AM +0100, Rene Engelhard <[EMAIL > > PROTECTED]> wrote: > > > There's no big difference in using hunspell and myspell, except that > > > hunspell dictionaries > > > then will also work. And you show that hunspell is used so the security > > > team knows > > > that mozilla needs to be rebuilt (which probably won't happen, no one > > > ever found a security bug > > > in either hunspell or myspell). And in any case, there's already enchant > > > and openoffice.org building > > > with static hunspell (openoffice.org does build far longer than ice*) > > > > How does the security team feel about having to rebuild iceape, > > iceweasel, icedove (you forgot to file a bug on icedove), OOo and enchant > > No, that would have been my next target (the source already is on my > disk) > > > if there happens to be a security bug in hunspell ? > > I am sure there won't be, but if it happens it happens. There's some > static libs in Debian where this is the case, afaik. Of course. not having to > do that is better, but... > > > How do buildds feel to have to rebuild iceape, iceweasel, icedove, OOo > > and enchant for every hunspell upload ? > > You don't have to. So when you fix bugs in hunspell, you want to leave the bugs in the programs that are statically linked to it. How great. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#401969: please build using hunspell
Rene Engelhard wrote: > MySpell is obsolete. > Please build against Hunspell, which is an improved version of MySpell > retaining full backwards compatibility. That also would make the usage > of hunspell-de-* in iceweasel possible. probably not so full backwards compatibility. > [ The Problem is that hunspell-de-* is an improved version of the > MySpell dict for hunspell and it's working in OOo since it uses > Hunspell also Italian dictionary in Debian is a very old release ... so obsolete than a lot of people ask me to correct a lot of errors, errors that are already corrected in the last version. I think that Debian is the last GNU/Linux distro that have a so old Itailian dictionary version. The last Italian dictionary under GPL license can be downloaded from here (2.3 beta 23/07/2006): http://linguistico.sf.net/wiki/doku.php?id=dizionario_italiano I have reported a whishlist for that #329971 at Date: Sat, 24 Sep 2005 23:04:33 +0200 For Italian language there is also a surname dictionary, also it under GPL, that can be found here: http://linguistico.sf.net/wiki/doku.php?id=dizionario_cognomi_italiani I don't see the hurry to have hunspell used on all programs ... if it is so hard or impossible to have recent dictionaries in Debian that are other languages than English or maintainer mother language. Mike Hommey wrote: On Fri, Dec 08, 2006 at 10:58:11PM +0100, Rene Engelhard wrote: Mike Hommey wrote: if there happens to be a security bug in hunspell ? I am sure there won't be, but if it happens it happens. There's some static libs in Debian where this is the case, afaik. Of course. not having to do that is better, but... How do buildds feel to have to rebuild iceape, iceweasel, icedove, OOo and enchant for every hunspell upload ? You don't have to. So when you fix bugs in hunspell, you want to leave the bugs in the programs that are statically linked to it. How great. I have reported some hunspell bugs to László (I don't know if some can be security bugs). I don't know if they are already corrected (László have told me: "I hope, I will solve the problem this month for OOo 2.1"). For example hunspell can generate more strings or more time the same string than myspell starting from the same dictionary. For hunspell there isn't a program that expand all the dictionary, so it is very hard to know if it work as you expected. Ciao Davide
Re: creative ssh-agent uses
On Sat, Dec 09, 2006 at 12:44:54AM -0800, Rudi Cilibrasi wrote: > Dear Ratiu, > > I am not sure I understand your situation, but maybe this can help? > > When creating an ssh-key using ssh-keygen, it prompts you for a > passphrase. It isn't so obvious, but you can simply hit return at that > point to have "no passphrase". This means that the resulting key > is unencrypted on your hard drive, so you have to rely > on unix (chmod) permissions to protect it from being > copied by unauthorized people. As long as you just press enter when > asked for a passphrase from ssh-keygen, this will ensure that using > that key with ssh-agent and ssh-add will not prompt you for > a passphrase. This is one way to use ssh-agent with a script > noninteractively. Just eval `ssh-agent`, ssh-add the unencrypted key, > then do the ssh commands all without a passphrase prompt. Errr, minor point here... but if you haven't got a passphrase on the ssh key, then there is no reason to use ssh-agent or ssh-add, they're non-ops for passphraseless keys. Thanks, -- Brett Parker -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#401969: please build using hunspell
Hi, Mike Hommey wrote: > On Fri, Dec 08, 2006 at 10:58:11PM +0100, Rene Engelhard <[EMAIL PROTECTED]> > wrote: > > Mike Hommey wrote: > > > On Thu, Dec 07, 2006 at 11:26:34AM +0100, Rene Engelhard <[EMAIL > > > PROTECTED]> wrote: > > > > There's no big difference in using hunspell and myspell, except that > > > > hunspell dictionaries > > > > then will also work. And you show that hunspell is used so the security > > > > team knows > > > > that mozilla needs to be rebuilt (which probably won't happen, no one > > > > ever found a security bug > > > > in either hunspell or myspell). And in any case, there's already > > > > enchant and openoffice.org building > > > > with static hunspell (openoffice.org does build far longer than ice*) > > > > > > How does the security team feel about having to rebuild iceape, > > > iceweasel, icedove (you forgot to file a bug on icedove), OOo and enchant > > > > No, that would have been my next target (the source already is on my > > disk) > > > > > if there happens to be a security bug in hunspell ? > > > > I am sure there won't be, but if it happens it happens. There's some > > static libs in Debian where this is the case, afaik. Of course. not having > > to > > do that is better, but... > > > > > How do buildds feel to have to rebuild iceape, iceweasel, icedove, OOo > > > and enchant for every hunspell upload ? > > > > You don't have to. > > So when you fix bugs in hunspell, you want to leave the bugs in the > programs that are statically linked to it. How great. Bullshit. You are intrepreting stuff everytime I didn't say. Not every fix in the package/packaging needs a rebuild, neither does a fix only affecting the hunspell program and not the library. In the library case, you're right. Gr��e/Regards, Ren� -- .''`. Ren� Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 signature.asc Description: Digital signature
Re: Bug#401969: please build using hunspell
Hi, Davide Prina wrote: > > MySpell is obsolete. > > Please build against Hunspell, which is an improved version of MySpell > > retaining full backwards compatibility. That also would make the usage > > of hunspell-de-* in iceweasel possible. > > probably not so full backwards compatibility. Proof? > also Italian dictionary in Debian is a very old release ... so obsolete > than a lot of people ask me to correct a lot of errors, errors that are > already corrected in the last version. > I think that Debian is the last GNU/Linux distro that have a so old > Itailian dictionary version. > > The last Italian dictionary under GPL license can be downloaded from > here (2.3 beta 23/07/2006): > http://linguistico.sf.net/wiki/doku.php?id=dizionario_italiano > > I have reported a whishlist for that #329971 at Date: Sat, 24 Sep 2005 > 23:04:33 +0200 Irrelevant for this discussion. I can't add GPLed stuff to the package because it then would be GPL. The other dictionaries in the OOo source are LGPL, though. You can package it externally or make it build from the ispell one, but I will *not* include it in -dictionaries due it's being GPL. I told that in the bug report that it's G`PL and can't add it. If you don't read it/understand it and then complain, well... > For Italian language there is also a surname dictionary, also it under > GPL, that can be found here: > http://linguistico.sf.net/wiki/doku.php?id=dizionario_cognomi_italiani GPL, too. See above. > I don't see the hurry to have hunspell used on all programs ... if it is I do. There's hunspell dictionaries in Debian which have to conflict against all mozillas... > I have reported some hunspell bugs to Láló don't know if some can > be security bugs). I don't know if they are already corrected (Lálóve > told me: "I hope, I will solve the problem this month for OOo 2.1"). Doubt that, there's no new hunspell release and neither does OOo 2.1 correct a new hunspell AFAIS (or he fixed the OOo h unspell copy and forgot the normal one..) No one claimed hunsppell hasn't got bugs but it's better than myspell overall. And it won't block usage of hunspell dictionaries in OOo. Gr??e/Regards, Ren? -- .''`. Ren? Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 signature.asc Description: Digital signature
Re: Bug#401969: please build using hunspell
On Sat, Dec 09, 2006 at 01:13:27PM +0100, Rene Engelhard <[EMAIL PROTECTED]> wrote: > I do. There's hunspell dictionaries in Debian which have to conflict > against all mozillas... I fail to see why. Are the hunspell dictionaries in /usr/share/myspell/dicts or what ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#401969: please build using hunspell
Rene Engelhard wrote: Davide Prina wrote: MySpell is obsolete. Please build against Hunspell, which is an improved version of MySpell retaining full backwards compatibility. That also would make the usage of hunspell-de-* in iceweasel possible. probably not so full backwards compatibility. Proof? for example this: ---8<--FILE a.aff-8<- SET ISO8859-15 TRY aioertnsclmdpgubzfvhàq'ACMSkBGPLxEyRTVòIODNwFéùèìjUZKHWJYQX SFX B Y 1 SFX B ere ono ere # p SFX p Y 2 SFX p o i o SFX p o e o ---8<-8<- ---8<--FILE a.dic-8<- 1 decidere/B ---8<-8<- ---8<--FILE a.txt-8<- decidere decidono decidoni decidone ---8<-8<- note that "decidere/B" must generate only "decidono" (with myspell), but hunspell generate also "decidoni" and "decidone" that are wrong Italian words. I have see that I can gain the same result with SFX B ere ono ere anystring p also if I write SFX B ere ono ere anystring abcdef than it is the same that write decidono/abcdef also Italian dictionary in Debian is a very old release ... so obsolete than a lot of people ask me to correct a lot of errors, errors that are already corrected in the last version. I think that Debian is the last GNU/Linux distro that have a so old Itailian dictionary version. The last Italian dictionary under GPL license can be downloaded from here (2.3 beta 23/07/2006): http://linguistico.sf.net/wiki/doku.php?id=dizionario_italiano I have reported a whishlist for that #329971 at Date: Sat, 24 Sep 2005 23:04:33 +0200 Irrelevant for this discussion. I can't add GPLed stuff to the package because it then would be GPL. The other dictionaries in the OOo source are LGPL, though. I don't have ask to add it to the OOo source, but to the myspell-it package. You can package it externally or make it build from the ispell one, but I will *not* include it in -dictionaries due it's being GPL. If I don't have mistake I intend -dictionaries as a Debian package interesting ... so you can neither include the German dictionary ... it is under GPL license and non-GPL for package that "support the OASIS Open Document Format for Office Applications and whose PRIMARY format for saving documents is the Open Document Format" I don't think icedove, iceweasel, ... respect this exception, so for all these the German dictionary is only GPL 2.0 or upper I think theare are lot of other dictionaries/thesaurus that have the same problem. I told that in the bug report that it's G`PL and can't add it. If you don't read it/understand it and then complain, well... where? when? querybts tell me: ---8<---8<---8<---8<---8< From: Rene Engelhard Subject: Re: Bug#329971: New Italian dictionary version available Date: Sat, 24 Sep 2005 23:45:45 +0200 [...] Aha. Hmm. And OOo 1.9.x/2.0 also contains only 2.1. Will look. When 1.9.x enters sid myspell-it will become 2.1 anyway and I'll look about updating the copy with 2.2. [...] Grüße/Regards, Rene ---8<---8<---8<---8<---8< note that the 2.2 version is GPL only Also the Italian thesaurus is only GPL and there is a recent version in Debian ... why? I have reported some hunspell bugs to Láló don't know if some can be security bugs). I don't know if they are already corrected (Lálóve told me: "I hope, I will solve the problem this month for OOo 2.1"). Doubt that, there's no new hunspell release and neither does OOo 2.1 correct a new hunspell AFAIS (or he fixed the OOo h unspell copy and forgot the normal one..) you can try the above example to check it Ciao Davide -- Dizionari: http://linguistico.sourceforge.net/wiki Client di posta: http://www.mozilla.org/products/thunderbird GNU/Linux User: 302090: http://counter.li.org Non autorizzo la memorizzazione del mio indirizzo su outlook
Re:
Por favor enviar e-mails para [EMAIL PROTECTED] Please send mail to [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 El 09/12/06 15:53, [EMAIL PROTECTED] escribió: > Por favor enviar e-mails para [EMAIL PROTECTED] > Please send mail to [EMAIL PROTECTED] Wilson: For desuscribirte, you should send to [EMAIL PROTECTED] with a blank message, and then, when receive the message of confirmation, should respond him, so that you of of drop automatically. With sincerity. - -- Slds de Santiago José López Borrazás. Admin de hackindex.com/.es Conocimientos avanzados en seguridad informática. Conocimientos avanzados en redes. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQIVAwUBRXrTX7uF9/q6J55WAQrsaQ/5ASZ10l0BVKGG1C5hF0TEflfUc4ZKFQQM RIwn6u9LR5Zj5mggLdsq/smj02oXNyYsqSDxIsZxi/yCD87j9Xxzt322m8vZNBj2 buGsFfH2CkLKQ61HZHPdm/HXMzY7/dC68JukqKIJQj9fZLUOCeZJ1hI34NKbZlFO BAoAyBu1aN8NPduMK/0Pdc8DY8RpBMz1+joCe6hLHSaDZAxdH5KZY6rMFeM+CwrA 85vVncNNO2XGa7Di6dCCkCSFivu0FnLTtlYeDrOLXVUaqxvoQLWL/rclcsx9X16H RAf5L6PZ5cqGzvHdsFV6yRWXon44ERPJjgxWIKWmhdn0icCZZUbrH8TPuna+dO4S 39VUQTMQRgkPxqAY32M1PhM79PgE8xPskWXi8wwfZIN2YyXUjsvVqP4zYDszXozO rsL27eECzvyBtoN/fVc5xWexlVN5timQaxEUwONr38LqU9F0+WSXepDgkodd7dkQ Tpr9v/7R21kC1L18KOKLyt+4WS02118K2UykcodrkJzJ/vZ3x3kdxAZRg8X0emN6 QpcmSyEODz+jO2D8gykP7HdHMfy6cAcNLp6fNByFFXT+scHJz8wp72SMsuC/7crP ZWjj+Hlel2EQGPzzqPSClZRSdC6kepauwGXgps+UZ6pQ/RJv/8xzc5LAssHxPvIR YRa7UMfcRm4= =GoDv -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 El 09/12/06 16:16, Santiago José López Borrazás escribió: > El 09/12/06 15:53, [EMAIL PROTECTED] escribió: >> Por favor enviar e-mails para [EMAIL PROTECTED] >> Please send mail to [EMAIL PROTECTED] > > Wilson: > > desuscribirte, Unsuscriber. Check traslation... :-) - -- Slds de Santiago José López Borrazás. Admin de hackindex.com/.es Conocimientos avanzados en seguridad informática. Conocimientos avanzados en redes. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQIVAwUBRXrUVruF9/q6J55WAQpKiA//Sm4lmQhV30MjJ3iEbMModdcQEMCuFy27 cLoVRba/Xvc4vOaGmvDp/Kvb1BWnOWvC9Rys7X1Wijyq9jkj6nwEJ5HVrO5qNWeM X3xnccJeWomv49cNgsq4mDepXxT1lzZbR0I3ynSwbaG2ntK9n5U1ANM8Tuf5aRoI 0uWIEGdZixKtDM+zihSXkhZ1IYYPX9c1N14PIrhcfJr1PHkMjKt8hd7Nd4teSG35 tbgZjSNWknSpnfUCfaWJ9PPFZiXTMXW4cZ7NZuG2tOfnkkK1ORckIqzHuvIIbvLW kjGVhb9y/Epp+3wtUG1HetO7KB++zR2179caT+dF0ydyRdlLqzsnvH2kNkfmsSFN UQuzXJBC3EM6ZgoPjiNuP64zZco61bRsUKZlisQK02E6HG12X6cVnhSC+sTYWGnp YYO+wLdQp0NG4ZRXXDtT+zmntPRUTI3DDLoDn4o0n+5hJbyGtYAPYEduCpyWWotV LAZRI4Jiq4l2XTI5XhG91bOXcQq3gCg4sTWI70GTJQ80guHElYKFgpb6+oKXFcov 1aIcO1SutR6wl5aUb8S5g4YhepHyDvmEAH3YekdJIKTOh+AWA+lNL2c5DT38Wn7m ZO5HSLY/uySkGoWkHMZM8GZSqdPSr4OLfrMJSnLNAo6mFxw1KTl1PvXWpJCpc9Vo RWZ5UTmzsyo= =D2im -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#401969: please build using hunspell
On Fri, Dec 08, 2006 at 10:32:50PM +0100, Mike Hommey wrote: > How does the security team feel about having to rebuild iceape, > iceweasel, icedove (you forgot to file a bug on icedove), OOo and enchant > if there happens to be a security bug in hunspell ? In general having multiple packages needing a rebuild for a single security fix is a problem, and not something we'd like to have to deal with. (For a specific example think of the pdf/gs updates we had to make earlier in the year/last year. Lots of different programs with very similar code which didn't always get spotted at the same time.) A more recent example would be the links + elinks updates. Links was updated first then we updated elinks afterwards when we learnt there was shared code .. (Obvious in retrospect, but if there are a lot of packages which would require a rebuild keeping track of all of them can be difficult; especially if we don't know about it in advance.) Steve -- signature.asc Description: Digital signature
Re: [SECURITY] [DSA 1232-1] New clamav packages fix denial of service
On Sat, Dec 09, 2006 at 03:43:33PM +0100, Moritz Muehlenhoff wrote: > Package: clamav > Vulnerability : missing sanity checks > Problem-Type : remote > Debian-specific: no > CVE ID : CVE-2006-5874 [...] > For the upcoming stable distribution (etch) this problem has been > fixed in version 0.86-1. ^^ > For the unstable distribution (sid) this problem has been fixed in > version 0.86-1. ^^ Clamav in testing and unstable is version 0.88.6 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: creative ssh-agent uses
On Sat, 09 Dec 2006, Rudi Cilibrasi wrote: > Dear Ratiu, > > I am not sure I understand your situation, but maybe this can help? > > When creating an ssh-key using ssh-keygen, it prompts you for a > passphrase. It isn't so obvious, but you can simply hit return at that > point to have "no passphrase". This means that the resulting key This is EXACTLY what I want to avoid. I use passphrase-less keys for some backups already, so I know the procedure. However, I'm trying to benefit from having the ssh session signed with my personal key, and somehow use that when mounting the dm-crypt/LUKS device where I backup my files. There are other people besides me that want to backup their laptops (containing personal data) to the same storage server, and we decided we didn't trust each other to the level where we would grant all our data to whoever knows the passwords. But we're lazy so we want to automate this :) I know there are other acceptable solutions (having the password written in a local file, or typing it every time), but they're not as nice. However, I'll go with one of them until I manage to put together a program that does what I want. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [SECURITY] [DSA 1232-1] New clamav packages fix denial of service
This one time, at band camp, Milan P. Stanic said: > On Sat, Dec 09, 2006 at 03:43:33PM +0100, Moritz Muehlenhoff wrote: > > Package: clamav > > Vulnerability : missing sanity checks > > Problem-Type : remote > > Debian-specific: no > > CVE ID : CVE-2006-5874 > [...] > > For the upcoming stable distribution (etch) this problem has been > > fixed in version 0.86-1. > ^^ > > For the unstable distribution (sid) this problem has been fixed in > > version 0.86-1. > ^^ > Clamav in testing and unstable is version 0.88.6 Yes, and the problem was fixed in version 0.86. That was the point of that statement. -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - signature.asc Description: Digital signature
