taskSavannah Administration - Tasks: task #4862, Submission of Gnu Forensic Zip

 
 

task #4862: Submission of Gnu Forensic Zip

Submitter:  Rob J Meijer <capibara>
Submitted:  Mon 24 Oct 2005 08:53:48 AM UTC
   
 
Should Start On:  Sun 23 Oct 2005 10:00:00 PM UTC Should be Finished on:  Wed 02 Nov 2005 11:00:00 PM UTC
Category:  Project Approval Priority:  * 5 - Normal
Status:  Done Privacy:  Public
Assigned to:  kickino Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Thu 16 Feb 2006 10:56:10 PM UTC, comment #8: 

Hello.
Don't see any problems for us.


I have approved your project as non-GNU.


You will receive an automated e-mail containing detailed information about the approval.

If you would like to offer your project to the GNU project,
please contact the GNU Eval team, following the instructions at
http://www.gnu.org/help/evaluation.html .


Regards.

Sebastian Wieseler <kickino>
Mon 13 Feb 2006 06:44:39 PM UTC, comment #7: 

Yes, absolutely.
Further, if the project gets aproved I would further like to know what the project needs to realize to be a viable candidate to become an officiel GNU project in the future.

Rob J Meijer <capibara>
Mon 13 Feb 2006 12:48:25 PM UTC, comment #6: 

Sorry for the long delay, are you still interested in hosting your project on Savannah?

Sebastian Wieseler <kickino>
Wed 23 Nov 2005 09:48:31 PM UTC, comment #5: 

I now again have a compiling version and hava I think got all
the issues resolved.

http://www.xs4all.nl/~rmeijer/gfzip/gfzip_0.0.6.tar.bz2

I have the interface files of the libraries defined and one of the libraries up and working (file creation) and have the tool working with respect to this library. The second library (random file access) is now still a stub that althoug it compiles does not do anything yet, but I hope this state would be sufficient to show you where the project is going and if it can be aproved as a project. As stated before the 'Gnu' part of the projectname could change to 'Generic' (in order to keep the gfzip/gfz names for the tool/lib). If the project gets aproved I would further like to know what the project needs to realize to be a viable candidate to become an officiel GNU project.

T.I.A.

Rob

Rob J Meijer <capibara>
Wed 16 Nov 2005 09:41:23 PM UTC, comment #4: 

Although the code is at this moment not in a working stage, I think I have adressed the issues with regard to registration.
I have the new tarbal at:

http://www.xs4all.nl/~rmeijer/gfzip/

I hope to have a first working version at this location within two to four weeks from now.

Rob J Meijer <capibara>
Wed 16 Nov 2005 11:22:49 AM UTC, comment #3: 

I have recently moved out all the openssl code and as you requested am now working to get stuff working using gnutls for the x509/p12 stuff.
It seems to be moving into the right direction, but I have not yet completed the efford. I've already replaced the sha1/md5 parts used by my code by libgcrypt, but the x509/p12 is work in progress.

With respect to the name 'Gnu Forensic Zip', maybe for the time being it could be changed to 'Generic Forensic Zip', that way I could call the tool 'gfzip' and give the files the extention '.gfz', and these would remain if my code gets upto the standards required to be accepted as a gnu project.

Further I have descidded to take out the idea of taking care of mountability in this project. The third part, that was defined as the NBD based server may come in a later 'gfzip-utils' project, but in order to cleanly define the boundaries of this project, I think that keeping this project to just the tool and the library would be best. That way I could keep the descission of using NBD, or other teqniques like kernel modules, fuse modules etc that may
have issues being part of a gnu based project concerned with them outside of the core project I think.

There is no more openssl in the code at this moment, but the code does not yet now again compile to a working tool. I hope you could wait a litle longer for me to be able to get the code to again compile to a usable be it alpha grade tool in order to suply you with the requested updated tarbal.
If you prefer I could also just now fix the licence notes and make a tarbal now from the not yet working code?



Rob J Meijer <capibara>
Mon 14 Nov 2005 04:09:05 PM UTC, comment #2: 

Hi,

I am waiting for an answer from you.

If within one week I still do not get a reply, I will remove your project. You will still be able to register it again once you have the time to deal with the registration issues.

Are you still willing to host your project at Savannah? If not, please tell us - we don't bite, and it will make us gain time.

Regards.

Davidlohr Bueso <unixoz>
Mon 24 Oct 2005 03:26:46 PM UTC, comment #1: 

Hi,

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

Your project is not yet part of the GNU project, so we cannot accept its current name. So please change the projects full name, mainly eliminating the GNU part.

While there are non-GNU programs with names that include 'gnu', such as gnuplot and gnuboy, they are not hosted on Savannah.
We want to maintain the distinction between GNU and non-GNU projects.

When your project is accepted into the GNU project you may change its name. You can do this by asking us.

It's not valid to link code released under the GNU GPL and
code under the license used by OpenSSL. Please read
http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs
I recommend you change to GNUTLS.

In order to release your project properly and unambiguously under the GNU 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.

If some of your files cannot carry such notices (e.g. binary files), then you can add a README file in the same directory containing the copyright and license notices. Check http://www.gnu.org/prep/maintain/html_node/Copyright-Notices.html for further information.

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.

To help us better keep track of your registration, please use the tracker's web interface following the link below.
Do not reply directly, the registration process is not driven by e-mail, and we will not receive such replies.

If you are willing to make the changes mentioned above, please provide us with an URL to an updated tarball of your project. 
Upon review, we will reconsider your project for inclusion in Savannah.


Regards.

Davidlohr Bueso <unixoz>
Mon 24 Oct 2005 08:53:48 AM 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.gnu.org/admin/groupedit.php?group_id=8062>


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

Full Name:
----------
  Gnu Forensic Zip

System Group Name:
-----------------
  gfzip

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

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

Description:
------------
  This project consists of 3 distinct parts, aimed at the forensic complete, compressed and signed storage and random access read only access to disk image data. The first part will be a simple tool, usable to create, check and retreive the original data to/from the files using a dd image as input or output and specifying compression method, digest algoritm, signing method and enviroment source. The second part of the project would be a simple library for read only checked random access to the files. The third part of the project will be a simple NBD server
build on top of the library, that allows filesystems to be mounted that
reside on the data file.

The current url of the preliminary code is http://www.xs4all.nl/~rmeijer/fdic/


Other Software Required:
------------------------
  libbz2, zlib, openssl and a library for access to pgp pki, this could be
pgpme or the low level library but I am not sure about that one yet.

Other Comments:
---------------
  Please note the fdic name will not be the final name for the project, its just a temporary working name



Rob J Meijer <capibara>

 

(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

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 8 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-02-16 kickino StatusWait reply Done
    Open/ClosedOpen Closed
2006-02-13 kickino StatusPing-ed Wait reply
    Assigned tounixoz kickino
2005-11-16 capibara Carbon-Copy- Added -email is unavailable-
2005-11-14 unixoz StatusWait reply Ping-ed
2005-10-24 unixoz StatusNone Wait reply
    Assigned toNone unixoz

Back to the top

Powered by Savane 3.13-f8d8.
Corresponding source code