taskSavannah Administration - Tasks: task #15227, Submission of PeaFactory

 
 

task #15227: Submission of PeaFactory

Submitted by:  Axel von dem Bruch <beloumix>
Submitted on:  Sat 30 Mar 2019 11:24:22 AM UTC  
 
Should Start On:  Sat 30 Mar 2019 12:00:00 AM UTC Should be Finished on:  Tue 09 Apr 2019 12:00:00 AM UTC
Category:  Project Approval Priority:  5 - Normal
Status:  Cancelled Privacy:  Public
Percent Complete:  0% Assigned to:  Ineiev <ineiev>
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)

Thu 11 Apr 2019 07:16:21 AM UTC, comment #8: 

Thank you, cancelling for now.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 10 Apr 2019 07:40:22 PM UTC, comment #7: 

I'm sorry I haven't answered for so long. I am not able to make all the necessary corrections at the moment. If that's OK, I'd try it again some time later and hopefully be better prepared.

Axel von dem Bruch <beloumix>
Wed 10 Apr 2019 05:00:58 PM UTC, comment #6: 

If there is no further interest, I'll cancel this submission.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 03 Apr 2019 07:45:47 AM UTC, comment #5: 

> Which files need the license notice?


All copyrightable files: text more than 10 lines long and non-text files of equivalent size.

> There are images, translation files (language bundle) and property files for user settings. Is it OK to add the license notice in a README file in that directory for all files?


README is a fallback for formats that don't allow such comments. Text files should contain the notices themselves.

https://savannah.gnu.org/maintenance/ValidNotices/ explains these matters in detail.

>> What about giving the GNU Project due credit?
> How much would the extra effort be?


Sorry for being unclear.  We require that hosted packages use "GNU/Linux" rather than "Linux" for the operating system.  This wasn't always the case in the tarball you submitted.

> The program was developed on OpenJDK (IcedTea)


I see, this must be sufficient.

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Wed 03 Apr 2019 06:58:19 AM UTC, comment #4: 

Hi Ineiev,

 > All files should contain them, not just "source files".

Which files need the license notice? There are images, translation files (language bundle) and property files for user settings. Is it OK to add the license notice in a README file in that directory for all files?

 > What about giving the GNU Project due credit?

How much would the extra effort be? I have no objections to the philosophy of the FSF, but the program does not meet the GNU coding standards yet and it seems that Java programs are a little unpopular in the GNU project.... I could try to meet the most important standards bit by bit, but that would take some time.

 > Also, please include an exact copy of the GPL from gnu.org (in your case, https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt), without re-wrapping the lines.

I just didn't find the text of the GNU license; I'll include the original text.

 > EPL-1.0 is GPL-incompatible; if this is just a compiler, it shouldn't affect the licensing of your code, but you should make sure it doesn't.

The Eclipse compiler is used internally for compiling, I don't know if this is a problem. It will soon be replaced by the OpenJDK compiler anyway. But I would like to move it to the next version, because this modification needs some testing.

The program was developed on OpenJDK (IcedTea), even though it also runs on Oracles JRE. So, the target Java platform does not contain any proprietary components.

Regards
Axel

Axel von dem Bruch <beloumix>
Mon 01 Apr 2019 01:04:31 PM UTC, comment #3: 

> Source files should now contain copyright and license notices.


All files should contain them, not just "source files".

What about giving the GNU Project due credit?

Also, please include an exact copy of the GPL from gnu.org (in your case, https://www.gnu.org/licenses/old-licenses/gpl-2.0.txt), without re-wrapping the lines.

> Which of the dependencies is GPL incompatible?


EPL-1.0 is GPL-incompatible; if this is just a compiler, it shouldn't affect the licensing of your code, but you should make sure it doesn't.

> I thought the Java platform was no longer a problem for the GPL


I'm not an expert in Java, please take a look at https://savannah.gnu.org/maintenance/JavaIssues/ (if that page is outdated, please suggest updates on savannah-hackers-public@gnu.org).

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Mon 01 Apr 2019 06:44:08 AM UTC, comment #2: 

Hi Ineiev,
Source files should now contain copyright and license notices. Which of the dependencies is GPL incompatible? The Eclipse Jar compiler could probably be replaced, the others not.
I thought the Java platform was no longer a problem for the GPL - how do the other Java projects in Savannah solve this?
If the compatibility problem can't be solved: Do you have a tip as an alternative to Savannah?
Regards
Axel

Axel von dem Bruch <beloumix>
Sun 31 Mar 2019 03:28:37 PM UTC, comment #1: 

Hello, Axel!

First, all copyrightable files in your tarball should have valid copyright and license notices.

Then, Savannah is the software forge of the GNU Project; when using our hosting facilities, the packages should call the operating system "GNU/Linux", not "Linux".

One of your dependencies is GPL-incompatible; also, since the Java platform may contain proprietary components, how do you ensure that your package doesn't depend on them?

Ineiev <ineiev>
Site AdministratorIn charge of this item.
Sat 30 Mar 2019 11:24:22 AM UTC, original submission:  

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves
or discards 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):

Registration Details

  • Name: PeaFactory
  • System Name:  peafactory
  • Type: non-GNU software and documentation
  • License: GNU General Public License v2 or later

Description:

PeaFactory is a program for creating small, round, green encryption programs (PEAs) for a certain purpose, such as notes, images, calendars, files.
A PEA is at the same time a program to decrypt a certain selection of files as well as a program to display the content (in case of Image Lock PEA, Calendar Lock PEA and Notebook PEA and therefore holds the plaintext only in RAM) and also a kind of a key file.
To be easily handled, PEAs consist of a single file, a (Java) jar archive. Producing the PEAs offers two advantages: The key file property of the program can be realized by writing a 32 byte randomly chosen value (a salt) inside the byte code of every single PEA, and although you can choose between several cryptographic primitives in the PeaFactory, the PEA itself contains only the chosen ones and is therefore relatively small.
Producing a PEA is a small extra effort that needs to be done only once. The produced PEA can be handled then like any other encryption program.
Programming language: Java

Other Software Required:

Bouncy Castle Crypto API:
https://www.bouncycastle.org/java.html
MIT-like license: https://www.bouncycastle.org/licence.html

Eclipse Jar Compiler:
https://mvnrepository.com/artifact/org.eclipse.jdt.core.compiler/ecj/3.5.1
License: https://www.eclipse.org/org/documents/epl-v10.php

Apache PDF Box:
https://pdfbox.apache.org/
License: https://www.apache.org/licenses/

Other Comments:

First test version was hosted on GitHub:
https://github.com/Beloumi/PeaFactory
I wanna get out of there.

Tarball URL:

https://eck.cologne/peafactory/src/downloads/peafactory/src/peafactory-0.3.0-beta-src.tar.gz

Axel von dem Bruch <beloumix>

 

(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

 

Carbon-Copy List
  • -email is unavailable- added by ineiev (Posted a comment)
  • -email is unavailable- added by beloumix (Submitted the item)
  •  

    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
    2019-04-11 ineiev StatusIn Progress => Cancelled
        Open/ClosedOpen => Closed
    2019-03-31 ineiev StatusNone => In Progress
        Assigned toNone => ineiev

    Back to the top


    Powered by Savane 3.5