On Mon, 7 Feb 2005, Matthew Palmer wrote:
> On Sun, Feb 06, 2005 at 10:52:50PM -0800, Alvin Oga wrote:
> > it's best when you can call the fbi (on the phone) and say, they're
> > back, trace um "NOW"
>
> Obviously you've never done this.
and obviously you seem too lazy to catch the cracker ??
On Sun, Feb 06, 2005 at 11:53:50PM -0800, Alvin Oga wrote:
>
> On Mon, 7 Feb 2005, Matthew Palmer wrote:
>
> > On Sun, Feb 06, 2005 at 10:52:50PM -0800, Alvin Oga wrote:
> > > it's best when you can call the fbi (on the phone) and say, they're
> > > back, trace um "NOW"
> >
> > Obviously you've
hi ya matt
On Mon, 7 Feb 2005, Matthew Palmer wrote:
> Three step program for you, bub.
>
> 1) Place your feet on your shoulders;
> 2) Push hard;
> 3) Take your first breath of arse-free air in a long time.
sounds like you should do the same ... or more like too late for you
> I have reporte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow you guys,
thank you very much for all your input.
I'll sit down with the manager and we'll discuss which route to take.
My first instinct was to warm up those drives and get the tapes .. but
I may want to
find out more as you guys have suggested! (
-- Forwarded Message --
Subject: [USN-74-1] Postfix vulnerability
Date: Sunday 06 February 2005 23:55
From: Wietse Venema <[EMAIL PROTECTED]>
To: Postfix announce <[EMAIL PROTECTED]>
Cc: Postfix users <[EMAIL PROTECTED]>
In a recent announcement on the Full-Disclosure mailing li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Already read this link:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267837
Jan Wagner wrote:
| -- Forwarded Message --
|
| Subject: [USN-74-1] Postfix vulnerability
| Date: Sunday 06 February 2005 23:55
| From: Wietse Venema <[EMA
On Sun, Feb 06, 2005 at 11:53:50PM -0800, Alvin Oga wrote:
don't accuse others ( me ) of what you haven't done yourself,
or dont want to do, as it only makes you look like the script kiddie
If anyone in this thread sounds like a kiddie it's you.
Mike Stone
--
To UNSUBSCRIBE, email to [EMAIL PROTE
> "Matthew" == Matthew Palmer <[EMAIL PROTECTED]> writes:
Matthew> I have reported intruders to the relevant authorities in
Matthew> the past, and have encountered an apathy field the size
Matthew> of a small continent. The only way they will even
Well, I think it may depend on w
On Mon, Feb 07, 2005 at 12:35:45AM +0100, martin f krafft wrote:
> Once an attacker is on the system, you cannot be sure anymore that
> you can track his/her actions down. Sophisticated root kits exist to
> cover all (!) traces.
I co-administer a system with ~ 250 users, a significant part of them
Hi -
Has anyone any advice on using grsecurity on a server running Debian
(testing) - I'm thinking about patching my new kernel with the
grsecurity stuff and starting to use it but I'm unsure of what I can
expect. Are the defaults going to break (or stop from functioning)
anything obvious (name
In article <[EMAIL PROTECTED]> you wrote:
> I co-administer a system with ~ 250 users, a significant part of them I
> don't know very well personally, and really, I don't rule out some of
> them might try to do some cracking, of, more likely, has such a shoddy
> password policy or infected windows
In article <[EMAIL PROTECTED]> you wrote:
>- works great across the usa, even if the cracked
>box they came from was offshore, they can trace it
>back to somebody's bedroom or colo
is that first hand knowledge or just some usual urband legend?
Greetings
Bernd
--
To UNS
Hi,
You should start with grsec low and proc restricions set customly. Hardening your kernel is always a
option. The grsec default high settings, and PaX break Jetty (java server container) in two, so it
simply won't start, gradm won't help as I know. After the grsec default low settings you shou
On Mon, 7 Feb 2005, Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> >- works great across the usa, even if the cracked
> >box they came from was offshore, they can trace it
> >back to somebody's bedroom or colo
>
> is that first hand knowledge or just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 6 Feb 2005, Scott Edwards wrote:
> 1. Your box gets compromised
> 2. You sue them
> 3. And then collect damages
>
> You'll quickly loose a case if there is any demonstration of
> negligence (that tail between your legs about the backup account
Greetings,..
Am Montag, 7. Februar 2005 14:10 schrieb Andras Got:
> Hi,
>
> You should start with grsec low and proc restricions set customly.
> Hardening your kernel is always a option. The grsec default high settings,
> and PaX break Jetty (java server container) in two, so it simply won't
> sta
On Mon, Feb 07, 2005 at 02:10:07PM +0100, Andras Got wrote:
> You should start with grsec low and proc restricions set customly.
> Hardening your kernel is always a option.
Running grsec isn't a problem, I use on both clients and servers.
Dont start with grsec low but with the custom option,
CON
Hi,
That's it, the chpax. I tried these things almost a year ago with JSP thingy. I googled and the
like, but chpax didn't help.
I meant that I selected high settings, then selected custom, then did some
changes. :)
A.
Thomas Sjögren írta:
On Mon, Feb 07, 2005 at 02:10:07PM +0100, Andras Got wro
Geoff Crompton wrote:
So can you be really sure that there was no root kit that succesfully
exploited your system? Have you rebooted off a trusted kernel, and
cryptographically checked every single file involved in booting? (Such
as the grub/lilo, kernel, all modules, init), and visually or
cry
On Mon, Feb 07, 2005 at 06:32:12PM +0200, Ognyan Kulev wrote:
> Another thing he doesn't like is that check is based on signed MD5 hash of
> content instead of based on signed content. Is it true that signed MD5 is
> weaker than signed content?
assymetric crypto ops are very slow, so you wouldn
On Mon, Feb 07, 2005 at 06:32:12PM +0200, Ognyan Kulev wrote:
He said that after signed Fedora package is installed (by default, only
signed packages are installed), you can boot from some CD and then check
signatures of each file of each package. Thus, only having key Red Hat's
fingerprint, yo
On Mon, Feb 07, 2005 at 06:25:19PM +1100, Matthew Palmer wrote:
> Obviously you've never done this. Good luck finding someone who even knows
> what TCP/IP is, let alone sufficient knowledge to be able to track a cracker
> in real time with no warning.
How smart they are can be seen at:
http://www
On Mon, Feb 07, 2005 at 07:26:43PM +0100, Milan P. Stanic wrote:
> On Mon, Feb 07, 2005 at 06:25:19PM +1100, Matthew Palmer wrote:
> > Obviously you've never done this. Good luck finding someone who even knows
> > what TCP/IP is, let alone sufficient knowledge to be able to track a cracker
> > in
On Monday 07 February 2005 at 16:17, Andras Got wrote:
> Hi,
>
> That's it, the chpax. I tried these things almost a year ago with JSP
> thingy. I googled and the like, but chpax didn't help.
>
> I meant that I selected high settings, then selected custom, then did some
> changes. :)
>
> A.
>
Estarei ausente do escritório a partir de 02/05/2005 e não retornarei até
02/27/2005.
I'll be out of the office from 5 to 27, Feb, and will answer no messages
during this period. If this is urgent maater, please forward to Mr. Evaldo
Mundim ([EMAIL PROTECTED]).
When I got back I'll answer the mes
hi ya
On Mon, 7 Feb 2005, James Renken wrote:
..
> The summary in legal terms: contributory negligence is not a defense to an
> intentional (or reckless) tort. The first major case I found with an
> offhand search is:
>
> Schellhouse v. Norfolk & W. Ry. Co., 575 N.E.2d 453, 456 (Ohio 1991)
t
Do I really have to check all .deb files of Packages files if I have
already checked all Packages' files themselves and they do check? AFAIK
apt-get always check if md5 (from Packages files it downloads) does not
match and warns/forbids the user of intalling such a "dirty" package. I
mean, what
hi,
I use Grsecurity with High level for over 2 years now on 2.4.X without
any problems running debian woody. These daemons works fine:
ssh
postfix
courier-imap (with and without ssl)
courier-pop (with and without ssl)
apache
apache-ssl
mysql
snort
and a view other ...
The best way would be for y
28 matches
Mail list logo
