According to Marco van de Voort:
gcc -nostdlib empty.c /usr/lib/crti.o /usr/lib/crt0.o -o empty
You mean crt1.o instead of crt0.o here right? crt0.o is the a.out version...
Yup, my fault.
grep exit *.o
nm(1) is your Dear Friend® here.
Grep and gcc -S also :-)
Anyway I manually
Hi folks
I'd like to propse a simple guard against stack overflow attack.
The idea is very simple: just prevent system call from writable
user area (i.e. data bss area) except SYS_sigreturn.
It has few performance penalty and can prevent trivial stack
overflow attack such as simply
I think this will break dynamically loaded code. Also, library
fixups may be writable and even if we don't embed jump instructions
in them now who knows what might be done in the future. Even if
we enforced this all it would accomplish is to make the cracks a
little more
I know this is not meant as a bug reporting list, but since I'm on it
for other purposes, I thought I could sent it in anyway.
I trashed a FreeBSD (probably 3.4, I get the exact version mailed
next week) by creating a bash script that contained
ping xxx.yyy.zzz.vvv
line 15 times, and
Ugh, I should have brought this up before the code freeze but...
Maybe we could make 4.0 the transition point for adding locking
structures to FILE and DIR structures instead of the hackish
way it's done now (maintaining a seperate structure).
Does anyone agree or have time for this?
It would
On Sat, Feb 05, 2000 at 03:16:28PM -0800, Alfred Perlstein wrote:
Ugh, I should have brought this up before the code freeze but...
Maybe we could make 4.0 the transition point for adding locking
structures to FILE and DIR structures instead of the hackish
way it's done now (maintaining a
This message was sent from Geocrawler.com by "Alex" [EMAIL PROTECTED]
Be sure to reply to that address.
Hello
When I run my script,sometimes I receive next
message:
"/usr/sbin/wanrouter: line 5 288 Broken pipe
ls $ROUTER_LOCK_DIR/ 289 Exit 1 | grep -q
wanpipe*"
I use bash-2.03 shell.
Marco van de Voort wrote:
I know this is not meant as a bug reporting list, but since I'm on it
for other purposes, I thought I could sent it in anyway.
I trashed a FreeBSD (probably 3.4, I get the exact version mailed
next week) by creating a bash script that contained
ping
Ugh, I should have brought this up before the code freeze but...
I think that pretty much says it all, and reflects my own opinion
on the matter.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On 05-Feb-00 Warner Losh wrote:
In msdosfs_vfsops.c we have:
|| !pmp-pm_Heads || pmp-pm_Heads 255
#ifdef PC98
|| !pmp-pm_SecPerTrack || pmp-pm_SecPerTrack 255) {
#else
|| !pmp-pm_SecPerTrack || pmp-pm_SecPerTrack 63) {
On Sat, 5 Feb 2000, Wes Peters wrote:
Next time, just become root and ping -f that Win98 machine. Running
lots of pings isn't going to get you what you're trying for, even if
you don't crash your FreeBSD machine.
Another great program for offing Windows boxes is spray.
A spray on a
11 matches
Mail list logo
