unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@goebel-consult.de>
To: guix-devel <guix-devel@gnu.org>
Subject: src.zip, demos and samples in java idk
Date: Sat, 3 Sep 2016 08:52:14 +0200	[thread overview]
Message-ID: <57CA731E.3060900@goebel-consult.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1170 bytes --]

Hi,

I discovered that the "jdk" of icedtea includes "demos", "samples" and
even a "src.zip" file. These are as big as 50 MB, where the src.zip
contributes by 43 MB. Thee 50MB are ca. 12% of the whole jdk.

IMHO, all of these should not be there since they are rarely needed.
Also it is common security best-practice to *not* include any demo code
on production systems - which should at least followed by such large
packages. The reasoning is that demos and examples are often prone to
errors and offering attack points.

Shall I move these to "doc" or to a new output (e.g. "examples").

We should use the same scheme later for all packages where the examples
will get a package by their own.

-- 
Schönen Gruß
(Please mind Hartmut Goebel
Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer
Information Security Management, Security Governance, Secure Software
Development

Goebel Consult, Landshut
http://www.goebel-consult.de

Blog:
http://www.goebel-consult.de/blog/bewertung-pgp-verschlusselung-bei-web.de-und-gmx

Kolumne:
http://www.cissp-gefluester.de/2011-09-kommerz-uber-recht-fdp-die-gefaellt-mir-partei



[-- Attachment #1.2: Type: text/html, Size: 2279 bytes --]

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2430 bytes --]

             reply	other threads:[~2016-09-03  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03  6:52 Hartmut Goebel [this message]
2016-09-03 12:25 ` src.zip, demos and samples in java idk Vincent Legoll
2016-09-03 14:04 ` Ludovic Courtès
2016-09-16 14:47   ` Hartmut Goebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57CA731E.3060900@goebel-consult.de \
    --to=h.goebel@goebel-consult.de \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).