Re: Questions on intercepting execve syscall

2003-11-17 Thread Samy Al Bahra
Quoting Murat Balaban <[EMAIL PROTECTED]>:
 
> It might be that you have some bad address in the execve index of sysent
> array.

This is likely. He could add a printf statement before calling the
original execve just to be sure.

> See http://www.enderunix.org/murat/linux_subexec/linux_subexec.c for a simple
> example.

This is 4.X specific (proc usage). I would just like to note that there is an 
execve symbol which you can reference in your code directly (rather than 
creating your own pointer for deinitialization).

EX:
-sysent[SYS_execve].sy_call = (sy_call_t *)oldexecve;
+sysent[SYS_execve].sy_call = (sy_call_t *)execve;

On Sun, Nov 16, 2003 at 07:53:30AM -0800, Kai Zhu wrote:
[...]

> > As you can see, I first just want to make sure that my_execve won't affect
> the original execve, then I will add some new logic in my_execve before
> returning to execve().

How exactly are you modifying the system call entry table? Are you modifying 
sysent even?

-- 
+---+
| Samy Al Bahra | [EMAIL PROTECTED] |
|---|
| B3A7 F5BE B2AE 67B1 AC4B  |
| 0983 956D 1F4A AA54 47CB  |
|---|
| http://www.kerneled.com   |
+---+

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Observations on make release process?

2003-11-17 Thread Dag-Erling Smørgrav
"Daniel O'Connor" <[EMAIL PROTECTED]> writes:
> but the way I do it is not 'normal' - I don't use the CVS repo
> because I can't commit into that tree

Be careful what you wish for :)

DES
-- 
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Questions on intercepting execve syscall

2003-11-17 Thread Pawel Jakub Dawidek
On Mon, Nov 17, 2003 at 11:02:10AM +0300, Samy Al Bahra wrote:
+> > See http://www.enderunix.org/murat/linux_subexec/linux_subexec.c for a simple
+> > example.
+> 
+> This is 4.X specific (proc usage). I would just like to note that there is an 
+> execve symbol which you can reference in your code directly (rather than 
+> creating your own pointer for deinitialization).
+> 
+> EX:
+> -sysent[SYS_execve].sy_call = (sy_call_t *)oldexecve;
+> +sysent[SYS_execve].sy_call = (sy_call_t *)execve;

And if there are two modules that intercept execve(2)?

Storing old value in dedicated pointer is correct.
There still will be a problem when modules are loaded and unloaded
in random order. Unload order have to be reverse load order, if not,
invalid pointer (of module that was already unloaded) will be stored
in sysent table.

-- 
Pawel Jakub Dawidek   [EMAIL PROTECTED]
UNIX Systems Programmer/Administrator http://garage.freebsd.pl
Am I Evil? Yes, I Am! http://cerber.sourceforge.net


pgp0.pgp
Description: PGP signature


Re: Observations on make release process?

2003-11-17 Thread Daniel O'Connor
On Monday 17 November 2003 21:42, Dag-Erling Smørgrav wrote:
> "Daniel O'Connor" <[EMAIL PROTECTED]> writes:
> > but the way I do it is not 'normal' - I don't use the CVS repo
> > because I can't commit into that tree
>
> Be careful what you wish for :)

Heheh..
I predict great bike sheds ahoy if I committed all my local patches 8-)

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 9A8C 569F 685A D928 5140  AE4B 319B 41F4 5D17 FDD5

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


MAJOR number #2

2003-11-17 Thread Roman Kurakin
 Original Message 
Subject:MAJOR number
Date:   Fri, 14 Nov 2003 22:12:37 +0300
From:   Roman Kurakin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Hi,

I need a new  MAJOR number for our new device.
How can I get it?
I've read that FreeBSD doesn't use them any more.
But we may need it to not interfere with other device
drivers in previous releases of FreeBSD.
???   ce   Cronyx Tau-32 E1 adapter
___
Best regars,
   Roman Kurakin
Cronyx Engineering
http://www.cronyx.ru
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"




___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: MAJOR number #2

2003-11-17 Thread Daniel Eischen
On Mon, 17 Nov 2003, Roman Kurakin wrote:

>  Original Message 
> Subject:  MAJOR number
> Date: Fri, 14 Nov 2003 22:12:37 +0300
> From: Roman Kurakin <[EMAIL PROTECTED]>
> To:   [EMAIL PROTECTED]
> 
> 
> Hi,
> 
> I need a new  MAJOR number for our new device.
> How can I get it?
> 
> I've read that FreeBSD doesn't use them any more.
> But we may need it to not interfere with other device
> drivers in previous releases of FreeBSD.
> 
> ???   ce   Cronyx Tau-32 E1 adapter

You don't need them in -current.

You might want to send this to -stable or -arch if
noone responds.

-- 
Dan Eischen

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


CVSUP error...

2003-11-17 Thread Brett L. Brown
Hey!

I'm looking for help on with a CVSUP problem.

I'm trying to run CVSUP with a supfile, I'm typing:

cvsup ports-supfile

and receiving the following:

Cannot get IP address of my own host -- is its hostname correct?

I'm using the host cvsup7.FreeBSD.org (129.250.31.140). I've have 
also included this information in my /etc/hosts file.

No worky. Any help would be great!

brett

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"