Re: Trojan

2023-08-27 Thread Brad Rogers
On Sun, 27 Aug 2023 11:20:37 +0100 Alain D D Williams wrote: Hello Alain, >Sorry if I came across as overly cynical. You didn't. The same can't be said for me, though. ;-) >It would be nice if they also went after the perps/crims behind >phishing emails‡‡ Not the job of government. Not di

Re: Trojan

2023-08-27 Thread Alain D D Williams
On Sun, Aug 27, 2023 at 10:23:06AM +0100, Brad Rogers wrote: > On Sun, 27 Aug 2023 09:36:02 +0100 > Alain D D Williams wrote: > > Hello Alain, > > >They will look at it and do something - or so they claim, > > Most likely that 'something' will be to compile statistics about > phishing attacks.

Re: Trojan

2023-08-27 Thread Brad Rogers
On Sun, 27 Aug 2023 09:36:02 +0100 Alain D D Williams wrote: Hello Alain, >They will look at it and do something - or so they claim, Most likely that 'something' will be to compile statistics about phishing attacks. Maybe produce a leaflet, or update the advice given on a web page somewhere.

Re: Trojan

2023-08-27 Thread Alain D D Williams
On Sun, Aug 27, 2023 at 10:31:55AM +0200, to...@tuxteam.de wrote: > If you feel like you'd like to learn a bit, study the mail > headers. Ponder about which ones the sender could have faked > and which ones not. Things like that. If you live in the UK you can forward it to here: rep...@phishing.g

Re: Trojan

2023-08-27 Thread tomas
On Sun, Aug 27, 2023 at 01:02:29AM -0600, William Torrez Corea wrote: > I am being threatened for this account: > > femor...@schlangenbad.de > > I receive the following message: > > I am a professional hacker and have successfully managed to hack your > operating system. I receive one of those

Re: Trojan Detected by Kaspersky in One Debian DVD

2012-11-02 Thread Jochen Spieker
Alan Feuerbacher: > > Last night Kaspersky anti-virus detected a Trojan in one of the files: Apparently you have missed the excellent answers you have already received on-list. If you want to be CC'ed, you should specifiy this in your e-mails (preferrably using appropriate headers). If you are n

Re: Trojan Detected by Kaspersky in One Debian DVD

2012-11-01 Thread Darac Marjal
On Wed, Oct 31, 2012 at 08:17:52PM -0400, Alan Feuerbacher wrote: > A couple of weeks ago I downloaded to my Windows 7 machine 10 DVD > iso files for debian-6.0.6-amd64. I have not yet installed Debian to > this machine. > > Last night Kaspersky anti-virus detected a Trojan in one of the files: >

Re: Trojan Detected by Kaspersky in One Debian DVD

2012-11-01 Thread Jon Dowland
On Wed, Oct 31, 2012 at 08:17:52PM -0400, Alan Feuerbacher wrote: > A couple of weeks ago I downloaded to my Windows 7 machine 10 DVD > iso files for debian-6.0.6-amd64. I have not yet installed Debian to > this machine. > > Last night Kaspersky anti-virus detected a Trojan in one of the files: >

Re: Trojan Detected by Kaspersky in One Debian DVD

2012-10-31 Thread John Hasler
-- John Hasler -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87fw4uf5e9@thumper.dhh.gt.org

Re: Trojan installed?

2006-04-07 Thread Csanyi Pal
On Fri, Apr 07, 2006 at 05:20:24PM +0200, Brent Clark wrote: > Csanyi Pal wrote: > > > >Tiger automatic auditor at debian-csp citation: > >---> > ># Running chkrootkit (/usr/sbin/chkrootkit) to perform further > >checks... > >NEW: --WARN-- [rootkit004w] Chkrootkit has detected a possib

Re: Trojan installed?

2006-04-07 Thread Brent Clark
Csanyi Pal wrote: Hello! My system is Debian GNU/Linux Sarge, with kernel 2.6.8. I get the e-mail from tiger. Tiger automatic auditor at debian-csp citation: ---> # Running chkrootkit (/usr/sbin/chkrootkit) to perform further checks... NEW: --WARN-- [rootkit004w] Chkrootkit has d

Re: trojan code in tcpdump/libpcap

2002-11-14 Thread Colin Watson
On Thu, Nov 14, 2002 at 09:45:22PM +, p wrote: > debs (et al.), > > apparently, there's trojan code in > tcpdump & libpcap. > > woody is okay, right? but those apps > in sarge/sid could be effected? No, Debian is apparently safe. (At least, so members of the security team have been saying.)