taskSavannah Administration - Tasks: task #5011, Submission of Sticker - System...

 
 

task #5011: Submission of Sticker - System call spy

Submitted by:  Mayank Jain <makuchaku>
Submitted on:  Sun 04 Dec 2005 06:13:44 PM UTC  
 
Should Start On:  Sun 04 Dec 2005 12:00:00 AM UTC Should be Finished on:  Wed 14 Dec 2005 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Done Privacy:  Public
Percent Complete:  0% Assigned to:  Sebastian Wieseler <kickino>
Open/Closed:  Closed Effort:  0.00

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Sun 18 Dec 2005 10:44:13 PM UTC, comment #6: 

Hi,

I have approved your project.  You will receive an automated e-mail containing detailed information about the approval.

Regards.

Sebastian Wieseler <kickino>
Project MemberIn charge of this item.
Thu 08 Dec 2005 10:30:35 AM UTC, comment #5: 

Hi Sebastian,

Just to add, the docs i've put up on my website are temporary. They are there, just to make a visitor comfortably view the code, crossreference the function calls with its source. That is not the final documentation i intend to make for this project.

Hence I originally did not included the FDL statements in any of them.

Regards,
Mayank

Mayank Jain <makuchaku>
Thu 08 Dec 2005 07:33:41 AM UTC, comment #4: 

Hi Sebastian,

I'm apologise for the code files not having viewable permissions. I've rectified the permissions.
Please have another look at http://makuchaku.info/stuff/projects/sticker/
http://makuchaku.info/stuff/projects/sticker/docs/html/index.html

I dont want to release a tarball yet as the code is not even 10% complete. I'm working on the new code & will update it this Saturday.

As for the documentation, again, it was a temporary documentation, generated with the help of Doxygen. This will also change this Saturday with the new codebase. I'll certainly add a COPYING file to the docs directory, mentioning the FDL & all the files under this directory are covered under FDL. But, adding FDL statements in all files produced by Doxygen would not be possible as the files are so many...

Regards,
Mayank

Mayank Jain <makuchaku>
Wed 07 Dec 2005 06:20:00 PM UTC, comment #3: 

Hello.

Can you please provide us with a tarball of your project (at least your COPYING is 503 compatible ;))

Then for your documentation:

In order to release your project properly and unambiguously under the FDL,
please place copyright notices and permission-to-copy statements after the title page of each work.

In addition, if you haven't already, please add a copy of the FDL
(available from http://www.gnu.org/licenses/fdl.html in various formats)
as a section of your works , and as plain text in a file named 'COPYING' (http://www.gnu.org/licenses/fdl.txt).

For more information, see http://www.gnu.org/licenses/fdl.html#SEC4

http://www.gnu.org/licenses/fdl-howto.html also covers additional points,
including a smaller notice that you can use in auxiliary files.

Regards,

Sebastian Wieseler <kickino>
Project MemberIn charge of this item.
Mon 05 Dec 2005 06:04:48 PM UTC, comment #2: 

Hi Sebastian,

I've added the GPL & copyrights statements at the starting of every file and included the COPYING file ad indicated.

regards,
Mayank

PS: I wish to do a bit of rework on documentation, once the projectis 15-20% complete.

Mayank Jain <makuchaku>
Mon 05 Dec 2005 05:34:57 PM UTC, comment #1: 

Hi,
I'm evaluating the project you submitted for approval in Savannah.

In order to release your project properly and unambiguously under the GPL,
please place copyright notices and permission-to-copy statements at the beginning of every file of source code.

In addition, if you haven't already, please include a copy of the plain text version of the GPL,
available from http://www.gnu.org/licenses/gpl.txt, into a file named "COPYING".

For more information, see http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explains why these procedures must be followed.
To learn why a copy of the GPL must be included with every copy of the code, for example,
see http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude.

Regards,

Sebastian Wieseler <kickino>
Project MemberIn charge of this item.
Sun 04 Dec 2005 06:13:44 PM UTC, original submission:  

A new project has been registered at Savannah
The project account will remain inactive until a site admin approve or discard the registration.

######### REGISTRATION ADMINISTRATION #########

While this item will be useful to track the registration process, approving or discarding the registration must be done using the specific "Group Administration" page, accessible only to site administrators, effectively logged as site administrators (superuser):

  <https://savannah.nongnu.org/admin/groupedit.php?group_id=8180>

######### REGISTRATION DETAILS #########

Full Name:
----------
  Sticker - System call spy

System Group Name:
-----------------
  sticker

Type:
-----
  non-GNU software &amp; documentation

License:
--------
  GNU Lesser General Public License

Description:
------------
  |-------------------|
|---+| Sticker |+---|
|-------------------|

  • Temporary source code URL...

Doxygen docs - http://makuchaku.info/stuff/projects/sticker/docs/html/index.html
Code - http://makuchaku.info/stuff/projects/sticker/

Abstract
--------
Sticker is a system call spy utility, running in user mode.
It can spy on any program(victim) and produce a log of the system calls it makes & their agruments. The spying activity will remain transparent to the victim.

Working
-------
*) Initiation modes
Sticker can initialize itself to spy on a program using
- Outproc Spying
+ PID of the victim will be used
+ The victim must be already running in this case
- Inproc Spying
+ Executable name (command line) of the victim will be used
+ The victim will be forked from the sticker driver
- Self Spying
+ Sticker is capable of spying on itself
+ Perfect mode for programs of which source code is available

*) Sticker will consist of an API, using which, an end user will apply Sticker to a victim (Stick to a victim). Such a driver will be called as "Sticker Driver"

Future
------
-> Programable API returning system call names to a driver, or perhaps invoking certain callbacks as and when the system call to which it was registered occurs.
-> Other TODO's

Other Software Required:
------------------------
  Sticker heavily relies on ptrace() system call. Any operating system that can support ptrace() as in original form (GNU/Linux) or as an emulation (cygwin) will be able to use Sticker & its API's.

Other Comments:
---------------
  I've just started the project. The source code is not even 5% complete. I would require Savannah services specially for version management & collaboration perposes. I hope in to rope 2 more developers/testers in the project.

Mayank Jain <makuchaku>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

 

 

Follow 4 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2005-12-18 kickino StatusWait reply => Done
    Open/ClosedOpen => Closed
2005-12-05 kickino StatusNone => Wait reply
    Assigned toNone => kickino

Back to the top


Powered by Savane 3.5