[EMAIL PROTECTED] (Brian F. Feldman) writes:
> It's "out with the bad, in with the good." Pidentd code is pretty terrible.
> The only security concerns with my code were wrt FAKEID, and those were
> mostly fixed (mostly meaning that a symlink _may_ be opened, but it won't
> be read.) If anyone w
On Tue, 13 Jul 1999, Daniel C. Sobral wrote:
> Jon Ribbens wrote:
> >
> > "Daniel C. Sobral" wrote:
> > > That's *not* abomination. How about pre-allocating over 100 Mb for X
> > > Free, for instance?
> >
> > What about it? If an application does not need 100MB, it should not
> > malloc it. If
On Tue, 13 Jul 1999, Daniel C. Sobral wrote:
> Jon Ribbens wrote:
> >
> > "Daniel C. Sobral" <[EMAIL PROTECTED]> wrote:
> > > That's *not* abomination. How about pre-allocating over 100 Mb for X
> > > Free, for instance?
> >
> > What about it? If an application does not need 100MB, it should no
On Tue, 13 Jul 1999, Greg Lehey wrote:
> In fact, the most interesting thing about this (rather large) document
> is that it's the best documentation I've seen on klds. I don't know
> why anybody would want to use it for compromising security, since it's
> a *lot* of work, and to even get as far
On Tue, 13 Jul 1999, Greg Lehey wrote:
> In fact, the most interesting thing about this (rather large) document
> is that it's the best documentation I've seen on klds. I don't know
> why anybody would want to use it for compromising security, since it's
> a *lot* of work, and to even get as far
People, how much attention are you going to get to this topic with a
subject line like "(forw)"?
On Monday, 12 July 1999 at 12:28:03 +, crypt0genic wrote:
>
> Have you all seen this?
> To: bugt...@securityfocus.com
>
> Hi folks,
>
> THC released a new article dealing with FreeBSD 3.x
> Kernel
>
> I like this suggestion. I worry about a trend I'm seeing, with more and
> more people keen to replace existing code with their own virgin code
> which hasn't had any serious field time behind it.
I'm actually more worried about the opposing trend that you espouse,
where the seniority of a co
Ollivier Robert wrote:
>
> Oh I forgot the one about having a veto system for I don't remember what...
Veto based locking for the fs.
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org
I'm one of those bad things that happen to good people.
To Unsubsc
Jon Ribbens wrote:
>
> > If you're not prepared to do that, the long and the short of it is that
> > FreeBSD _does_ overcommit, we like it that way and neither of these two
> > facts is likely to change.
>
> I can add it to the list of reasons I don't use it then I guess ;-).
Whatever. The opera
Jon Ribbens wrote:
>
> "Daniel C. Sobral" wrote:
> > That's *not* abomination. How about pre-allocating over 100 Mb for X
> > Free, for instance?
>
> What about it? If an application does not need 100MB, it should not
> malloc it. If it does need it, it should malloc it and know that it
> is ava
People, how much attention are you going to get to this topic with a
subject line like "(forw)"?
On Monday, 12 July 1999 at 12:28:03 +, crypt0genic wrote:
>
> Have you all seen this?
> To: [EMAIL PROTECTED]
>
> Hi folks,
>
> THC released a new article dealing with FreeBSD 3.x
> Kernel modules
>
> I like this suggestion. I worry about a trend I'm seeing, with more and
> more people keen to replace existing code with their own virgin code
> which hasn't had any serious field time behind it.
I'm actually more worried about the opposing trend that you espouse,
where the seniority of a c
This is typically symptomatic of poor CPU cooling; all of a sudden you
are running the CPU at full power 100% of the time, rather than sitting
in an HLT instruction. It can be further exacerbated if you're
overclocking.
> Is it just me/my machine or has 3.2-STABLE become rather unstable and
>
Ollivier Robert wrote:
>
> Oh I forgot the one about having a veto system for I don't remember what...
Veto based locking for the fs.
--
Daniel C. Sobral(8-DCS)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
I'm one of those bad things that happen to good people.
To Unsu
Jon Ribbens wrote:
>
> > If you're not prepared to do that, the long and the short of it is that
> > FreeBSD _does_ overcommit, we like it that way and neither of these two
> > facts is likely to change.
>
> I can add it to the list of reasons I don't use it then I guess ;-).
Whatever. The oper
Jon Ribbens wrote:
>
> "Daniel C. Sobral" <[EMAIL PROTECTED]> wrote:
> > That's *not* abomination. How about pre-allocating over 100 Mb for X
> > Free, for instance?
>
> What about it? If an application does not need 100MB, it should not
> malloc it. If it does need it, it should malloc it and k
> > Yuck. That's a complete abomination. What's the point of it? It's turning
>
> Paging Terry Lambert, Terry Lambert - do you read me? It's time for
> your annual rant on the topic of memory overcommit. :-)
It's not overcommit so much as it is what happens to a process that gets a
page fault wh
According to Warner Losh:
> I thought it was time for his annual rant about how the current
> FreeBSD development model is going to have problems scaling...
No no, I think you're thinking of the write-lock read-lock we should use on
CVS in order to have the Hamiltonian graph without cycle to solve
On Tue, 13 Jul 1999 00:20:27 +0100, Jon Ribbens wrote:
> I'd love to, could you please be more specific? I can't find anything
> relevant searching for 'malloc' or 'overcommit'.
My apologies. It was the current mailing list. Search for "malloc AND
NULL AND kill", and pick out the "swap-related
This is typically symptomatic of poor CPU cooling; all of a sudden you
are running the CPU at full power 100% of the time, rather than sitting
in an HLT instruction. It can be further exacerbated if you're
overclocking.
> Is it just me/my machine or has 3.2-STABLE become rather unstable and
Sheldon Hearn wrote:
> You're rehashing stuff that's been discussed to death. Please look at
> the mailing list archives for this mailing list.
I'd love to, could you please be more specific? I can't find anything
relevant searching for 'malloc' or 'overcommit'.
> If you're not prepared to do th
On Mon, 12 Jul 1999 23:56:29 +0100, Jon Ribbens wrote:
> What about it? If an application does not need 100MB, it should not
> malloc it. If it does need it, it should malloc it and know that it
> is available if the malloc succeeds.
You're rehashing stuff that's been discussed to death. Please
> > Yuck. That's a complete abomination. What's the point of it? It's turning
>
> Paging Terry Lambert, Terry Lambert - do you read me? It's time for
> your annual rant on the topic of memory overcommit. :-)
It's not overcommit so much as it is what happens to a process that gets a
page fault w
"Daniel C. Sobral" wrote:
> That's *not* abomination. How about pre-allocating over 100 Mb for X
> Free, for instance?
What about it? If an application does not need 100MB, it should not
malloc it. If it does need it, it should malloc it and know that it
is available if the malloc succeeds.
> Ba
According to Warner Losh:
> I thought it was time for his annual rant about how the current
> FreeBSD development model is going to have problems scaling...
No no, I think you're thinking of the write-lock read-lock we should use on
CVS in order to have the Hamiltonian graph without cycle to solv
On Tue, 13 Jul 1999 00:20:27 +0100, Jon Ribbens wrote:
> I'd love to, could you please be more specific? I can't find anything
> relevant searching for 'malloc' or 'overcommit'.
My apologies. It was the current mailing list. Search for "malloc AND
NULL AND kill", and pick out the "swap-related
Sheldon Hearn <[EMAIL PROTECTED]> wrote:
> You're rehashing stuff that's been discussed to death. Please look at
> the mailing list archives for this mailing list.
I'd love to, could you please be more specific? I can't find anything
relevant searching for 'malloc' or 'overcommit'.
> If you're n
Ok, got another hang in "siobi" state (this time after it
successfully completed the script). Here is the trace:
(gdb) file /usr/sbin/amd
Reading symbols from /usr/sbin/amd...done.
(gdb) attach 155
Attaching to program: /usr/sbin/amd, process 155
0x8063dc4 in open ()
(gdb) where
#0 0x8063
On Mon, 12 Jul 1999 23:56:29 +0100, Jon Ribbens wrote:
> What about it? If an application does not need 100MB, it should not
> malloc it. If it does need it, it should malloc it and know that it
> is available if the malloc succeeds.
You're rehashing stuff that's been discussed to death. Pleas
"Daniel C. Sobral" <[EMAIL PROTECTED]> wrote:
> That's *not* abomination. How about pre-allocating over 100 Mb for X
> Free, for instance?
What about it? If an application does not need 100MB, it should not
malloc it. If it does need it, it should malloc it and know that it
is available if the ma
On 10 Jul 1999 12:56:41 -0400, R. Matthew Emerson wrote:
> I thought that it was almost never proper to soft-mount rw filesytems.
> Am I mistaken about this?
I must admit, it sounds like sensible advice. The only NFS exports which
I have to rely on are read-only mounts. The only time I soft-mou
Ok, it's now wedged in a different state (using the same perl
script to wedge it). According to top:
317 root2 0 648K 456K STOP 0 0:00 0.00% 0.00% amd
I also managed to attach to the running process this time:
(gdb) file /usr/sbin/amd
Reading symbols from /u
Warner Losh wrote:
>
> In message <378987f5.8d53...@softweyr.com> Wes Peters writes:
> : It shouldn't be all that hard to read the register and set the voltages
> : appropriately. Table 5-1 on p. 54 has the PC Card register values for
> : CVS[2:1] and what they mean.
>
> Agreed...
>
> : Quatech
Ok, got another hang in "siobi" state (this time after it
successfully completed the script). Here is the trace:
(gdb) file /usr/sbin/amd
Reading symbols from /usr/sbin/amd...done.
(gdb) attach 155
Attaching to program: /usr/sbin/amd, process 155
0x8063dc4 in open ()
(gdb) where
#0 0x806
On Fri, 9 Jul 1999, Jake Burkholder wrote:
> Nvidia cards are already supported. The GL xlock savers look awesome.
Really? Wow. The xscreensaver GL savers looked like crap, the xlockmore
ones worked for about oh two seconds, before slowing down to unaccelerated
speeds. This at 640x480x16 too.
On 10 Jul 1999 12:56:41 -0400, R. Matthew Emerson wrote:
> I thought that it was almost never proper to soft-mount rw filesytems.
> Am I mistaken about this?
I must admit, it sounds like sensible advice. The only NFS exports which
I have to rely on are read-only mounts. The only time I soft-mo
Ok, it's now wedged in a different state (using the same perl
script to wedge it). According to top:
317 root2 0 648K 456K STOP 0 0:00 0.00% 0.00% amd
I also managed to attach to the running process this time:
(gdb) file /usr/sbin/amd
Reading symbols from /
Whatever you do with identd, just make it work through NAT. That's
the #1 request from folks where this is concerned.
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Wes Peters writes:
> : It shouldn't be all that hard to read the register and set the voltages
> : appropriately. Table 5-1 on p. 54 has the PC Card register values for
> : CVS[2:1] and what they mean.
>
> Agreed...
>
> : Quatech or Socket
On Mon, 12 Jul 1999, Doug Rabson wrote:
> On Mon, 12 Jul 1999, Karl Pielorz wrote:
>
> >
> >
> > Mark Newton wrote:
> > >
> > > Karl Pielorz wrote:
> > >
> > > > Yes, a nice, effective - and simply way of replacing syscall's on
> > > FreeBSD...
> > > > Some might say a little too 'simple'
On Fri, 9 Jul 1999, Doug wrote:
> In my continuing efforts to get this freebsd box into shape for
> web hosting at my company (where it relies exclusively on NFS for
> retrieving customer data) I've been making progress thanks to some recent
> commits by Peter. Now I can run the heavy duty N
I would suggest that a version of this document be incorporated into our
docs.
It's not like it says anythign new, but it's a really good introduction
to KLD modules and maybe it's be better to have those documents around to
remind people how easy it is to hack a system once root is broken.
julia
On Fri, 9 Jul 1999, Jake Burkholder wrote:
> Nvidia cards are already supported. The GL xlock savers look awesome.
Really? Wow. The xscreensaver GL savers looked like crap, the xlockmore
ones worked for about oh two seconds, before slowing down to unaccelerated
speeds. This at 640x480x16 too.
Whatever you do with identd, just make it work through NAT. That's
the #1 request from folks where this is concerned.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, 12 Jul 1999, Karl Pielorz wrote:
>
>
> Mark Newton wrote:
> >
> > Karl Pielorz wrote:
> >
> > > Yes, a nice, effective - and simply way of replacing syscall's on
> > FreeBSD...
> > > Some might say a little too 'simple'?
> >
> > Garbage. You can do this on any OS, whether it suppo
On Mon, 12 Jul 1999, Doug Rabson wrote:
> On Mon, 12 Jul 1999, Karl Pielorz wrote:
>
> >
> >
> > Mark Newton wrote:
> > >
> > > Karl Pielorz wrote:
> > >
> > > > Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
> > > > Some might say a little too 'simple'?
> >
On Fri, 9 Jul 1999, Doug wrote:
> In my continuing efforts to get this freebsd box into shape for
> web hosting at my company (where it relies exclusively on NFS for
> retrieving customer data) I've been making progress thanks to some recent
> commits by Peter. Now I can run the heavy duty
Okay, slowly getting somewhere, I think...
We setup the .Xdefaults file, as follows, on the remote server and are
starting an xterm to the client machine, which is "acceptable", but I must
be missing something:
XTerm*vt100*translations: #override \n\
Shift F1:string(0x1B) string(0x5B) s
I would suggest that a version of this document be incorporated into our
docs.
It's not like it says anythign new, but it's a really good introduction
to KLD modules and maybe it's be better to have those documents around to
remind people how easy it is to hack a system once root is broken.
juli
On Mon, 12 Jul 1999, Sheldon Hearn wrote:
>
>
> On Sun, 11 Jul 1999 12:47:30 MST, Doug wrote:
>
> > Finally, Brian might want to search the bugtraq archives before
> > he commits anything. There have been quite a few identd related
> > discussions, and it would be points in our favor if w
Perfect, slowly putting it together. One thing that I didn't find in the
man page, and am wondering if its just somethign I did wrong, but does
ordering matter?
I put in, first time through:
F1: ...
Shift F1: ...
And it Shift-F1 and F1 both gave the same answers...
But, if I
On Mon, 12 Jul 1999, Karl Pielorz wrote:
>
>
> Mark Newton wrote:
> >
> > Karl Pielorz wrote:
> >
> > > Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
> > > Some might say a little too 'simple'?
> >
> > Garbage. You can do this on any OS, whether it supports
Okay, slowly getting somewhere, I think...
We setup the .Xdefaults file, as follows, on the remote server and are
starting an xterm to the client machine, which is "acceptable", but I must
be missing something:
XTerm*vt100*translations: #override \n\
Shift F1:string(0x1B) string(0x5B)
On Mon, 12 Jul 1999, Sheldon Hearn wrote:
> On Mon, 12 Jul 1999 15:04:43 -0300, The Hermit Hacker wrote:
>
> > Hopefully this makes a bit more sense?
>
> What doesn't make sense is the fact that a FreeBSD developer, who should
> know better, is mailing this sort of thing to freebsd-hackers.
In message
The Hermit Hacker writes:
: I need to build a keyboard map such that:
:
: F1 == ESC OP
: F2 == ESC OQ
: Shift-F1 == ESC [31~
: Shift-F2 == ESC [32~
Why not do this with Xterm translations? Generally speaking xmodmap
and friends are poor choices to even think about
On Mon, 12 Jul 1999, Sheldon Hearn wrote:
>
>
> On Sun, 11 Jul 1999 12:47:30 MST, Doug wrote:
>
> > Finally, Brian might want to search the bugtraq archives before
> > he commits anything. There have been quite a few identd related
> > discussions, and it would be points in our favor if
In message <1336.931774...@zippy.cdrom.com> "Jordan K. Hubbard" writes:
: Paging Terry Lambert, Terry Lambert - do you read me? It's time for
: your annual rant on the topic of memory overcommit. :-)
I thought it was time for his annual rant about how the current
FreeBSD development model is goin
On Mon, 12 Jul 1999 15:04:43 -0300, The Hermit Hacker wrote:
> Hopefully this makes a bit more sense?
What doesn't make sense is the fact that a FreeBSD developer, who should
know better, is mailing this sort of thing to freebsd-hackers.
Sheldon.
To Unsubscribe: send mail to majord...@
Perfect, slowly putting it together. One thing that I didn't find in the
man page, and am wondering if its just somethign I did wrong, but does
ordering matter?
I put in, first time through:
F1: ...
Shift F1: ...
And it Shift-F1 and F1 both gave the same answers...
But, if
Morning...
Got a couple of suggestions, and have tried both, with the
xkeycaps appearing to be the more practical for what I'm trying to get
done, I think.
From reading the xkeycaps man page, its a frontend for xmodmap,
but reading *its* man page pretty much got me nowhere fast,
On Mon, 12 Jul 1999, Sheldon Hearn wrote:
> On Mon, 12 Jul 1999 15:04:43 -0300, The Hermit Hacker wrote:
>
> > Hopefully this makes a bit more sense?
>
> What doesn't make sense is the fact that a FreeBSD developer, who should
> know better, is mailing this sort of thing to freebsd-hackers.
In message <[EMAIL PROTECTED]>
The Hermit Hacker writes:
: I need to build a keyboard map such that:
:
: F1 == ESC OP
: F2 == ESC OQ
: Shift-F1 == ESC [31~
: Shift-F2 == ESC [32~
Why not do this with Xterm translations? Generally speaking xmodmap
and friends are poor choices
In message <[EMAIL PROTECTED]> "Jordan K. Hubbard" writes:
: Paging Terry Lambert, Terry Lambert - do you read me? It's time for
: your annual rant on the topic of memory overcommit. :-)
I thought it was time for his annual rant about how the current
FreeBSD development model is going to have pr
On Mon, 12 Jul 1999 15:04:43 -0300, The Hermit Hacker wrote:
> Hopefully this makes a bit more sense?
What doesn't make sense is the fact that a FreeBSD developer, who should
know better, is mailing this sort of thing to freebsd-hackers.
Sheldon.
To Unsubscribe: send mail to [EMAIL PR
In message <378987f5.8d53...@softweyr.com> Wes Peters writes:
: It shouldn't be all that hard to read the register and set the voltages
: appropriately. Table 5-1 on p. 54 has the PC Card register values for
: CVS[2:1] and what they mean.
Agreed...
: Quatech or Socket Communications? I don't se
Morning...
Got a couple of suggestions, and have tried both, with the
xkeycaps appearing to be the more practical for what I'm trying to get
done, I think.
From reading the xkeycaps man page, its a frontend for xmodmap,
but reading *its* man page pretty much got me nowhere fast,
> On Sun, 11 Jul 1999 22:34:09 +0200, Mark Murray wrote:
>
> > As long as the documentation is _clear_ that this is not a front-line
> > security tool, but rather a thing to marginally augment logs with
> > user-supplied info, then I'll buy it.
>
> This is why I put forward a motion to move piden
On Mon, 12 Jul 1999 18:37:13 GMT, Niall Smart wrote:
> The patch appended seems to fix this, I'd like someone familiar
> with sh to review it though, since this may be symptomatic of
> a general problem with command substitution.
As I understand your patch, you're saying "we should fork off a c
Sheldon Hearn wrote:
> cd /tmp
> echo .`cd /`.
> pwd
>
> Any takers?
The patch appended seems to fix this, I'd like someone familiar
with sh to review it though, since this may be symptomatic of
a general problem with command substitution.
> PS: And no, this is not an invitation to chat about t
In message <[EMAIL PROTECTED]> Wes Peters writes:
: It shouldn't be all that hard to read the register and set the voltages
: appropriately. Table 5-1 on p. 54 has the PC Card register values for
: CVS[2:1] and what they mean.
Agreed...
: Quatech or Socket Communications? I don't see one right
Beautiful...thanks :) Infocmp doesn't exist under FreeBSD, but Solaris
has it :)
On Mon, 12 Jul 1999, Dominic Mitchell wrote:
> On Mon, Jul 12, 1999 at 11:50:33AM -0300, The Hermit Hacker wrote:
> > Attached is the output of 'tconv -b vt221' on our Solaris machine
> > where this map'ng is r
> On Sun, 11 Jul 1999 22:34:09 +0200, Mark Murray wrote:
>
> > As long as the documentation is _clear_ that this is not a front-line
> > security tool, but rather a thing to marginally augment logs with
> > user-supplied info, then I'll buy it.
>
> This is why I put forward a motion to move pide
On Mon, 12 Jul 1999 18:37:13 GMT, Niall Smart wrote:
> The patch appended seems to fix this, I'd like someone familiar
> with sh to review it though, since this may be symptomatic of
> a general problem with command substitution.
As I understand your patch, you're saying "we should fork off a
Sheldon Hearn wrote:
> cd /tmp
> echo .`cd /`.
> pwd
>
> Any takers?
The patch appended seems to fix this, I'd like someone familiar
with sh to review it though, since this may be symptomatic of
a general problem with command substitution.
> PS: And no, this is not an invitation to chat about
Beautiful...thanks :) Infocmp doesn't exist under FreeBSD, but Solaris
has it :)
On Mon, 12 Jul 1999, Dominic Mitchell wrote:
> On Mon, Jul 12, 1999 at 11:50:33AM -0300, The Hermit Hacker wrote:
> > Attached is the output of 'tconv -b vt221' on our Solaris machine
> > where this map'ng is
Hi folks,
I'm hoping someone here is interested in tracking down a bug in our
/bin/sh . Changing directory within a backtick (``) subshell in sh
taints the parent's working directory. The following sample code gives
the expected result for /bin/csh, but breaks for /bin/sh
cd /tmp
echo .`cd /`.
p
On Mon, Jul 12, 1999 at 11:50:33AM -0300, The Hermit Hacker wrote:
> Attached is the output of 'tconv -b vt221' on our Solaris machine
> where this map'ng is required, but the output doesn't look anything like
> /etc/termcap :(
Try doing "infocmp -C vt221" to get termcap output. What you ha
Morning...
Last week, at work, I talked one of the guys in IS into switching
from using Win98 to using FreeBSD 3.2/X, and all has gone well so far,
except that we've hit a snag that I'm not sure how to rectify...
Under Win98, they use CRT, with a special set of keyboard map'ngs
f
Hi folks,
I'm hoping someone here is interested in tracking down a bug in our
/bin/sh . Changing directory within a backtick (``) subshell in sh
taints the parent's working directory. The following sample code gives
the expected result for /bin/csh, but breaks for /bin/sh
cd /tmp
echo .`cd /`.
Does anyone feel strongly about the small patch in misc/3237 to add support
for handling installation of script files in bsd.prog.mk?
I can certainly see how this could be useful.
Kris
-
"Never criticize anybody until you have walked a mile in their shoes,
because by that time you will be a
On Mon, Jul 12, 1999 at 11:50:33AM -0300, The Hermit Hacker wrote:
> Attached is the output of 'tconv -b vt221' on our Solaris machine
> where this map'ng is required, but the output doesn't look anything like
> /etc/termcap :(
Try doing "infocmp -C vt221" to get termcap output. What you h
Morning...
Last week, at work, I talked one of the guys in IS into switching
from using Win98 to using FreeBSD 3.2/X, and all has gone well so far,
except that we've hit a snag that I'm not sure how to rectify...
Under Win98, they use CRT, with a special set of keyboard map'ngs
Does anyone feel strongly about the small patch in misc/3237 to add support
for handling installation of script files in bsd.prog.mk?
I can certainly see how this could be useful.
Kris
-
"Never criticize anybody until you have walked a mile in their shoes,
because by that time you will be a
Mark Newton wrote:
>
> Karl Pielorz wrote:
>
> > Yes, a nice, effective - and simply way of replacing syscall's on
> FreeBSD...
> > Some might say a little too 'simple'?
>
> Garbage. You can do this on any OS, whether it supports loadable
> modules or not, if you've managed to win sufficie
Mark Newton wrote:
>
> Karl Pielorz wrote:
>
> > Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
> > Some might say a little too 'simple'?
>
> Garbage. You can do this on any OS, whether it supports loadable
> modules or not, if you've managed to win sufficient
Karl Pielorz wrote:
> Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
> Some might say a little too 'simple'?
Garbage. You can do this on any OS, whether it supports loadable
modules or not, if you've managed to win sufficient privileges through
some other means.
Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
Some might say a little too 'simple'?
-Kp
crypt0genic wrote:
>
> Have you all seen this?
>
> From: Anonymous
> To: bugt...@securityfocus.com
>
> Hi folks,
>
> THC released a new article dealing with FreeBSD 3.x
> Ker
Have you all seen this?
--
Reverse engineering, the most phun and usually the most effective way to tackle
a problem or learn something new.
Public PGP key: http://www.ecad.org/crypt0genic_pgp_key
Website:http://www.ecad.org/
--- Begin Message ---
Hi folks,
THC release
Karl Pielorz wrote:
> Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
> Some might say a little too 'simple'?
Garbage. You can do this on any OS, whether it supports loadable
modules or not, if you've managed to win sufficient privileges through
some other means.
Yes, a nice, effective - and simply way of replacing syscall's on FreeBSD...
Some might say a little too 'simple'?
-Kp
crypt0genic wrote:
>
> Have you all seen this?
>
> From: Anonymous <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
>
> Hi folks,
>
> THC released a new article dealing with FreeB
Have you all seen this?
--
Reverse engineering, the most phun and usually the most effective way to tackle a
problem or learn something new.
Public PGP key: http://www.ecad.org/crypt0genic_pgp_key
Website:http://www.ecad.org/
Hi folks,
THC released a new article de
> Yuck. That's a complete abomination. What's the point of it? It's turning
Paging Terry Lambert, Terry Lambert - do you read me? It's time for
your annual rant on the topic of memory overcommit. :-)
- Jordan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers"
I have a WaveLAN ISA adaptor.
I am trying to run it in a machine equiped with an AMD K6-2 350
processor running at 66mhz bus speed.
I am getting the following error while ifconfiging the card.
ifconfig wl0 192.168.10.1
ifconfig: ioctl (SIOCAIFADDR): File exists
cray100 /root 2% Jul 12 03:43:23 cr
Some hacking group has written an introduction to using KLDs under
FreeBSD. It's not supposed to be a "normal" tutorial, but it may be
appreciated by a few people on this list.
http://thc.pimmel.com/files/thc/bsdkern.html
--
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator
> Yuck. That's a complete abomination. What's the point of it? It's turning
Paging Terry Lambert, Terry Lambert - do you read me? It's time for
your annual rant on the topic of memory overcommit. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in
I have a WaveLAN ISA adaptor.
I am trying to run it in a machine equiped with an AMD K6-2 350
processor running at 66mhz bus speed.
I am getting the following error while ifconfiging the card.
ifconfig wl0 192.168.10.1
ifconfig: ioctl (SIOCAIFADDR): File exists
cray100 /root 2% Jul 12 03:43:23 c
Some hacking group has written an introduction to using KLDs under
FreeBSD. It's not supposed to be a "normal" tutorial, but it may be
appreciated by a few people on this list.
http://thc.pimmel.com/files/thc/bsdkern.html
--
Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator
On Sun, 11 Jul 1999 22:00:04 EST, Chris Costello wrote:
>As usual, it's at http://www.calldei.com/~chris/rtfm.tar.gz
Can I suggest that you make a port of your little project so that you
don't have to announce updates to hackers every few days?
Those who're interested will see CVS commit m
On Sun, 11 Jul 1999 12:47:30 MST, Doug wrote:
> Finally, Brian might want to search the bugtraq archives before
> he commits anything. There have been quite a few identd related
> discussions, and it would be points in our favor if we didn't come out
> with anything that had known exploits
Jon Ribbens wrote:
>
> Yuck. That's a complete abomination. What's the point of it? It's turning
> an out-of-memory situation from an easily-detected recoverable temporary
> resource shortage which can be worked-around or waited out, into an
> unrecoverable fatal error. Do a significant number of
1 - 100 of 106 matches
Mail list logo
