Your message dated Mon, 12 Apr 2010 17:37:54 +0200
with message-id <[email protected]>
and subject line java-package has been removed from Debian unstable
has caused the Debian Bug report #294995,
regarding java-package: please support unlimited crypto policy files
jce_policy*.zip
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
294995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294995
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: java-package
Version: 0.20
Severity: wishlist
On Sun's download pages, there is a section at the end called Other
Downloads. There, one can download jce_policy-x_y_z.zip (where x_y_z
is the java version number). This zip contains a US_export_policy.jar
and a local_policy.jar that are meant to replace the jars by the same
name in jre/lib/security.
The new jars allow unlimited strength crypto; for example, AES with
256-bit key will not work without these jars.
It would be nice if java-package supported this. I see several
possibilities:
1. Just build it in to the scripts; if the user is building a Sun
package and the script detects an appropriately named jce_policy-* in
the same directory as the .bin file, prompt the user and ask if he'd
like to use it. If so, replace the jars in jre/lib/security with the
new ones before building the .deb.
2. Enhance make-jpkg to build tiny sun-j2{sdk,re}1.{4,5}-jce-policy
.debs from the jce_policy-*.zip files that contain only the two jars,
and dpkg-divert the old jars appropriately.
3. Supply a shell script that will assist the admin in setting up a
local diversion.
I think I like #2 the best. #1 has the problem that it's difficult to
tell whether a given sun-j2sdk* package has the crypto jars or not.
#3 will certainly work but doesn't seem entirely satisfactory.
Thoughts? I can contribute something if that will help.
Thanks,
Steve
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (900, 'unstable'), (890, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-hamachi
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages java-package depends on:
ii coreutils 5.2.1-2 The GNU core utilities
ii debhelper 4.2.30 helper programs for debian/rules
ii fakeroot 1.2.4 Gives a fake root environment
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
the package has been removed. That is why the bugs cannot be fixed anymore.
Cheers,
Torsten
--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers>. Please
use
[email protected] for discussions and questions.
