Re: [SM-USERS] Compromised Accounts

2007-11-22 Thread Alan in Toronto
On Wed, November 21, 2007 10:00 am, Vernon A. Fort wrote: > Chris Hilts wrote: >> Well if they have the password as you indicated above, there isn't a >> whole lot to "compromising" the account, is there? >> >> > This is TRUE - it appears they did have the password but I am trying to > find any kn

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Bill Landry
Paul Lesniewski wrote the following on 11/21/2007 2:17 PM -0800: > On Nov 21, 2007 9:10 AM, Fredrik Jervfors <[EMAIL PROTECTED]> wrote: > > I also saw 10 - 20 attempts to log in and then we had a successful > login on a users account. We have implemented sender_restriction and > wil

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Bill Landry
Chris Hilts wrote the following on 11/21/2007 2:01 PM -0800: > [EMAIL PROTECTED] wrote: > > > I already have fail2ban running to protect a ssh server. Until > > now ( just 1 day ), it is running ok. > > > I will use your rules to protect squirrelmail too. :-) I already > > use squirrel_lo

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread David Guntner
Chris Hilts grabbed a keyboard and wrote: > > [EMAIL PROTECTED] wrote: > > > I already have fail2ban running to protect a ssh server. Until > > now ( just 1 day ), it is running ok. > > > I will use your rules to protect squirrelmail too. :-) I > > already use squirrel_logger. :-) > >

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Paul Lesniewski
On Nov 21, 2007 9:10 AM, Fredrik Jervfors <[EMAIL PROTECTED]> wrote: > >>> I also saw 10 - 20 attempts to log in and then we had a successful > >>> login on a users account. We have implemented sender_restriction and > >>> will implement CAPTCHA after Thanksgiving. > > > > Maybe not effective or g

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Paul Lesniewski
> > I already have fail2ban running to protect a ssh server. Until > > now ( just 1 day ), it is running ok. > > > I will use your rules to protect squirrelmail too. :-) I already > > use squirrel_logger. :-) > > I would recommend using fail2ban to protect the underlying SMTP and IMAP > s

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Chris Hilts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > I already have fail2ban running to protect a ssh server. Until > now ( just 1 day ), it is running ok. > I will use your rules to protect squirrelmail too. :-) I already > use squirrel_logger. :-) I would recomme

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread [EMAIL PROTECTED]
Hi Bill, > > I have never tested fail2ban before, even with sshd, so I don't > > know if it is a good solution. > > Fail2ban is a very good solution server side solution. I posted this > info to the SM list awhile back regarding using fail2ban with SquirrelMail: > > http://marc.info/?l=s

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Paul Lesniewski
On Nov 21, 2007 7:17 AM, Rob Wright <[EMAIL PROTECTED]> wrote: > > On Wednesday 21 November 2007 09:06, Vernon A. Fort wrote: > > Rob Wright wrote: > > > On Wednesday 21 November 2007 08:27, Vernon A. Fort wrote: > > >> To all, > > >> I run a large webmail server, 19k + accounts. Lately, just th

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Bill Landry
[EMAIL PROTECTED] wrote the following on 11/21/2007 8:54 AM -0800: > Hi, > > >>> I also saw 10 - 20 attempts to log in and then we had a successful login >>> on a users account. We have implemented sender_restriction and will >>> implement CAPTCHA after Thanksgiving. >>> > > Maybe n

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Fredrik Jervfors
>>> I also saw 10 - 20 attempts to log in and then we had a successful >>> login on a users account. We have implemented sender_restriction and >>> will implement CAPTCHA after Thanksgiving. > > Maybe not effective or good solution, but I am testing > fail2ban.org, with sshd, and I saw a reference

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread [EMAIL PROTECTED]
Hi, > > I also saw 10 - 20 attempts to log in and then we had a successful login > > on a users account. We have implemented sender_restriction and will > > implement CAPTCHA after Thanksgiving. > Maybe not effective or good solution, but I am testing fail2ban.org, with sshd, and I saw a re

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Tomas Kuliavas
> We have been through the exact issue about two weeks ago. We had to route > entire blocks of IP to null0 in my router and also killed them in the > firewall. But I have seen a renewed "attack" from new ranges of IP's. Of > course, the results of these attacks are that we have been blacklisted

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Ken A
Rob Wright wrote: > On Wednesday 21 November 2007 09:06, Vernon A. Fort wrote: >> Rob Wright wrote: >>> On Wednesday 21 November 2007 08:27, Vernon A. Fort wrote: To all, I run a large webmail server, 19k + accounts. Lately, just this month, i have had three different email accoun

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Marc Powell
On Nov 21, 2007, at 9:00 AM, Vernon A. Fort wrote: > Chris Hilts wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Vernon A. Fort wrote: > > > > > This is TRUE - it appears they did have the password but I am trying > to > find any know exploit in the authentication method.

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Zack Odell
iction and will implement CAPTCHA after Thanksgiving. Zack From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Rob Wright [EMAIL PROTECTED] Sent: Wednesday, November 21, 2007 9:17 AM To: Squirrelmail User Support Mailing List Subject: Re: [SM-USERS] Compromis

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Rob Wright
On Wednesday 21 November 2007 09:06, Vernon A. Fort wrote: > Rob Wright wrote: > > On Wednesday 21 November 2007 08:27, Vernon A. Fort wrote: > >> To all, > >> I run a large webmail server, 19k + accounts. Lately, just this > >> month, i have had three different email account send out spam email

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Vernon A. Fort
Rob Wright wrote: > On Wednesday 21 November 2007 08:27, Vernon A. Fort wrote: > >> To all, >> I run a large webmail server, 19k + accounts. Lately, just this >> month, i have had three different email account send out spam email. >> Basically, the accounts have their personal information cha

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Vernon A. Fort
Chris Hilts wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Vernon A. Fort wrote: > > >> amount of spam email. It appears the exploiter obtained the password >> and then compromised the account. The actual email user is completely >> unaware of the compromise - meaning they did

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Rob Wright
On Wednesday 21 November 2007 08:27, Vernon A. Fort wrote: > To all, > I run a large webmail server, 19k + accounts. Lately, just this > month, i have had three different email account send out spam email. > Basically, the accounts have their personal information changed to a > different name an

Re: [SM-USERS] Compromised Accounts

2007-11-21 Thread Chris Hilts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Vernon A. Fort wrote: > amount of spam email. It appears the exploiter obtained the password > and then compromised the account. The actual email user is completely > unaware of the compromise - meaning they did NOT send this spam email. > When l

[SM-USERS] Compromised Accounts

2007-11-21 Thread Vernon A. Fort
To all, I run a large webmail server, 19k + accounts. Lately, just this month, i have had three different email account send out spam email. Basically, the accounts have their personal information changed to a different name and reply to address. Then they send out quite a large amount of