Paul Iadonisi wrote:
On Thu, 2002-05-23 at 16:45, Kenny Donahue wrote:
Ok, here's one for all you bash experts out there.
I have a line in a script that does this:
lspci -d1134:1 | /usr/bin/wc -l
The idea of course is to get the number of our boards in the
system. the funny thing
PROTECTED]
kennyd Date: Fri, 24 May 2002 09:09:56 -0400
kennyd Subject: Re: bash question (Solved!)
kennyd
kennyd Paul Iadonisi wrote:
kennyd
[... snip ...]
kennyd Okay, do I get a case of [root] beer for figuring this out?
kennyd ;-)
kennyd Check the setting of your POSIXLY_CORRECT environment
Ok, here's one for all you bash experts out there.
I have a line in a script that does this:
lspci -d1134:1 | /usr/bin/wc -l
The idea of course is to get the number of our boards in the
system. the funny thing is, if I log in as root I get
2/* Note the 6 blank spaces before the 2 */
Kenny Donahue said:
Ok, here's one for all you bash experts out there.
I have a line in a script that does this:
lspci -d1134:1 | /usr/bin/wc -l
The idea of course is to get the number of our boards in the
system. the funny thing is, if I log in as root I get
2/* Note the 6 blank
In a message dated: Thu, 23 May 2002 16:45:47 EDT
Kenny Donahue said:
Ok, here's one for all you bash experts out there.
I have a line in a script that does this:
lspci -d1134:1 | /usr/bin/wc -l
[...snip...]
/* Note the 6 blank spaces before the 2 */
if I log in as my self or ssh into the
On Thu, 23 May 2002, Kenny Donahue wrote:
lspci -d1134:1 | /usr/bin/wc -l
The idea of course is to get the number of our boards in the
system. the funny thing is, if I log in as root I get
2/* Note the 6 blank spaces before the 2 */
if I log in as my self or ssh into the
It's got to be somewhere in my environment. Like I said,
The problem is solved it's just messing up my head that it works
differently for me and others than it does for root.
I was just hoping for someone to say
export SET_THIS_DUMMY=get_spaces
and get the spaces in my environment.
Thanks,
nope. TERM=xterm on both
which xterm
/usr/bin/X11/xterm
on both
Ken Ambrose wrote:
On Thu, 23 May 2002, Kenny Donahue wrote:
lspci -d1134:1 | /usr/bin/wc -l
The idea of course is to get the number of our boards in the
system. the funny thing is, if I log in as root I get
2
[PLEASE DON'T TOPQUOTE]
Kenny Donahue [EMAIL PROTECTED] writes:
Ken Ambrose wrote:
On Thu, 23 May 2002, Kenny Donahue wrote:
lspci -d1134:1 | /usr/bin/wc -l
The idea of course is to get the number of our boards in the
system. the funny thing is, if I log in as root I get
On Thu, 3 Jan 2002, Michael O'Donnell wrote:
Also, if there's a perl/networking guru, I'm looking to re-write
the trojan to look like it's working, but instead be logging the
intruder's actions, IP, etc. It's a simple backdoor (only about 2.5
pages printed), so I might even be able to
If anyone wants to make this into a trap for
the cracker, let me know and I'll test it.
My understanding is that such traps don't
pay off very often - you typically find
that the dirtbags have simply connected
from another compromised system. But I
confess that I'd probably get a voyeuristic
BTW, here's (what appears to be) some info
about another break-in by that same dirtbag:
http://www.netsys.com/bsdi-users/2001-07/msg00268.html
*
To unsubscribe from this list, send mail to [EMAIL PROTECTED]
with the text
On Fri, 4 Jan 2002, Michael O'Donnell wrote:
My understanding is that such traps don't pay off very often - you
typically find that the dirtbags have simply connected from another
compromised system.
Worse still, if you do something wrong, you risk discovery and/or further
compromise of the
On Fri, 4 Jan 2002, Benjamin Scott wrote:
Worse still, if you do something wrong, you risk discovery and/or further
compromise of the system, including the attacker doing something nasty, like
zeroing your partition table.
True...
But I just want to see something like this scroll past his
[EMAIL PROTECTED] said:
The only safe way to create a honey pot or fly trap is by
creating a
duplicate system, with all important data removed or replaced, and
isolated
from other systems.
True... but I don't have the hardware for that.
You don't need more hardware. User-mode
On Thu, 3 Jan 2002, Brian Chabot [EMAIL PROTECTED] wrote:
Is there an easy way to tee the $HISTFILE to more than one location?
What I want is a mirror of .bash_history stored elsewhere in case the
It's probably not be the best way to proceed, but I have an LD_PRELOAD
hack that tees writing
Is there an easy way to tee the $HISTFILE to more than one location?
I believe that BASH history is only updated when
the session ends rather than continuously during the
session, so any session in which somebody messes with
history logging will likely not be recorded.
That being said, it
I'd prefer if the exploit wasn't posted on the mailing list or the web
pages.
We'd be accused of promoting that sort of thing, which I don't want to do
-
especially in the current political climate.
He can mail it to the individuals who really want to see it.
--Bruce
Michael O'Donnell wrote:
At http://news.gnhlug.org/article.php?sid=257 is:
I''m assuming the cracker is coming in from the net. What about just
running tcpdump against the port he''s coming in through (telnet?) and
capture everything?
*
To unsubscribe
19 matches
Mail list logo
