igital-random-number-generator-drng-software-implementation-guide
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Wednesday, November 23, 2016 3:36 AM
To: Commons Developers List
Subject: Re: [CRYPTO] Feedback from ApacheCON Europe
Hello Dapeng,
Sun, Dapeng schr
Thank Benedikt for the minutes! And thank Xianda for the presentation.
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Saturday, November 19, 2016 7:49 PM
To: Commons Developers List
Subject: [CRYPTO] Feedback from ApacheCON Europe
Hi,
Xianda Ke held a nice p
the package level. A per-class scan is
warranted IMO.
Gary
On Mon, Nov 7, 2016 at 5:32 PM, Sun, Dapeng wrote:
> I think it should be access level should be protected, not
> package-protected.
>
> Is the ivars in CryptoInputStream? Some fields are also needed by its
> subclas
I think it should be access level should be protected, not package-protected.
Is the ivars in CryptoInputStream? Some fields are also needed by its subclass
(not only for the classes in the package), such as CtrCryptoInputStream.
Regards,
Dapeng
-Original Message-
From: Gary Gregory [ma
Hi Gary,
>> I see ivars left at the package access level. This must be an oversight,
>> right?
Thank you for the suggestion, I will fix it.
>> We can only fix that in 2.0 and a new package. What a bummer!
I'm agreed with you, the new package could also contain the recent fixes. Thank
you :)
Re
u set the redirects up initially.
Regards,
Benedikt
Sun, Dapeng schrieb am Fr., 5. Aug. 2016 um
11:34 Uhr:
> Hello
>
> The following link cannot redirect. Anyone know the reason about it?
> https://commons.apache.org/crypto/download_crypto.cgi
> It should redirect to
> htt
/3f6e5499
>
> Branch: refs/heads/master
> Commit: 3f6e549948fbb6584a21c2350e410cb834f28502
> Parents: d94c719
> Author: Sun Dapeng
> Authored: Wed Aug 17 09:37:08 2016 +0800
> Committer: Sun Dapeng
> Committed: Wed Aug 17 09:37:08 2016 +0800
>
> ---
, Sun, Dapeng wrote:
> Hello
>
> Is there anyone can help add Crypto to the reporter?
>
> https://reporter.apache.org/addrelease.html?commons
> Full version name: CRYPTO-1.0.0
> Date of release: 2016-08-09
Done.
Mark
---
Hello
Is there anyone can help add Crypto to the reporter?
https://reporter.apache.org/addrelease.html?commons
Full version name: CRYPTO-1.0.0
Date of release: 2016-08-09
Thanks,
Dapeng
The Apache Commons Crypto team is pleased to announce the release of Apache
Commons Crypto 1.0.0, The release is available for download at
http://commons.apache.org/proper/commons-crypto/download_crypto.cgi
Apache Commons Crypto is a cryptographic library optimized with AES-NI
(Advanced Enc
Hello
The following link cannot redirect. Anyone know the reason about it?
https://commons.apache.org/crypto/download_crypto.cgi
It should redirect to
https://commons.apache.org/proper/commons-crypto/download_crypto.cgi
Sites for other components could redirect. But some download_*cgi redirect
ct: Re: [VOTE] Release CRYPTO 1.0.0 based on RC1
On Tue, Aug 2, 2016 at 7:19 PM, Sun, Dapeng wrote:
> Hi Gary,
>
> >>Where are the instructions to actually build the same jar contained
> >>in
> the bin-zip with ALL of the native libraries for Windows, Mac, and Linux?
s.
Where are the instructions to actually build the same jar contained in the
bin-zip with ALL of the native libraries for Windows, Mac, and Linux?
Gary
On Mon, Jul 25, 2016 at 8:25 PM, Sun, Dapeng wrote:
> Hi all,
>
>
>
> Apache Commons CRYPTO was established at May 9, 2016, There
CRYPTO 1.0.0 based on RC1
+1 (non-binding)
Verified locally, UT passed.
Regards,
Xianda
-Original Message-
From: Sun, Dapeng [mailto:dapeng@intel.com]
Sent: Tuesday, July 26, 2016 11:25 AM
To: Commons Developers List
Subject: [VOTE] Release CRYPTO 1.0.0 based on RC1
Hi all,
Apache
Thank Jörg for the testing.
>>I am building crypto with my compiler zoo on Gentoo Linux with OpenSSL 1.02h
>>installed.
I don't have environment with Gentoo Linux, I just tested the library with
OpenJDK on pure Ubuntu OS: OpenJDK 7 on Ubuntu 14.04 and OpenJDK 8 on Ubuntu
16.04, All of them are
ontents/Home/jre
Default locale: de_DE, platform encoding: UTF-8 OS name: "mac os x", version:
"10.11.6", arch: "x86_64", family: "mac"
And it works perfectly fine.
Since the build failure is probably related to my environment:
+1
Regards,
Benedikt
Sun, Dape
Hi all,
Apache Commons CRYPTO was established at May 9, 2016, There are presently
numbers of resolved issues fix in CRYPTO. We also fix the legal issue.
Apache Commons CRYPTO 1.0.0 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/crypto
(rev 14538)
The tag is
-SNAPSHOT/commons-crypto-1.0.0-20160722.085755-6.jar
Thanks & Regards
Dapeng
-Original Message-
From: Sun, Dapeng [mailto:dapeng@intel.com]
Sent: Tuesday, July 19, 2016 6:48 PM
To: Commons Developers List
Subject: RE: [CRYPTO]1.0.0 Release Plan
Thank Dennis for your suggestion, bu
h respect to
native support.
- Dennis
> -Original Message-
> From: sebb [mailto:seb...@gmail.com]
> Sent: Tuesday, July 12, 2016 09:09
> To: Commons Developers List
> Subject: Re: [CRYPTO]1.0.0 Release Plan
>
> On 12 July 2016 at 14:54, sebb wrote:
> &g
wrote:
> On 12 July 2016 at 14:20, Sun, Dapeng wrote:
>> Separating artifacts for each native library, I think it should be same as
>> copying the native binary files. We also need to collect the artifacts for
>> unpacking and bundling.
>
> Yes.
>
>> About us
Separating artifacts for each native library, I think it should be same as
copying the native binary files. We also need to collect the artifacts for
unpacking and bundling.
About using the 'all' artifact, users may be confused about downloading the
artifacts for all the different platforms, es
...@gmail.com]
Sent: Monday, July 11, 2016 5:35 PM
To: Commons Developers List
Subject: Re: [CRYPTO]1.0.0 Release Plan
On 11 July 2016 at 09:02, Sun, Dapeng wrote:
> About the native binaries, I think we should put them in the same jar
> finally. CRYPTO is library, user shouldn't need
About the native binaries, I think we should put them in the same jar finally.
CRYPTO is library, user shouldn't need to specify Platform in theory. I just
checked the jars of JNA and SNAPPY at maven, the jar contains native for all
the platform their support. For the first release of CRYPTO, I
07:03, Sun, Dapeng wrote:
> Thank Sebb for your great work!
>
> About the Properties instance, I have some personal opinions.
>
> I think properties provide a flexible configuration mechanism. Config values
> could be added and read/written without too much limitation, we also p
+1 for keeping them consistent.
I prefer "OpenSslCipher"
Regards
Dapeng
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Thursday, June 30, 2016 9:35 AM
To: Commons Developers List
Subject: Re: [crypto] Camel case for names
On Wed, Jun 29, 2016 at 5:33 PM, se
could you tell me more detail?
Regards
Dapeng
-Original Message-
From: sebb [mailto:seb...@gmail.com]
Sent: Sunday, June 26, 2016 7:53 AM
To: Commons Developers List
Subject: Re: [CRYPTO]1.0.0 Release Plan
On 24 June 2016 at 11:17, sebb wrote:
> On 24 June 2016 at 10:08, Sun, Dapeng
-
From: Sun, Dapeng [mailto:dapeng@intel.com]
Sent: Monday, June 06, 2016 5:14 PM
To: Commons Developers List
Subject: [CRYPTO]1.0.0 Release Plan
Hello,
Apache Commons CRYPTO was established at May 9, 2016[1], There are presently
numbers of resolved issues fix in CRYPTO[2]. Recently, we
t...@apache.org]
Sent: Saturday, June 18, 2016 12:43 AM
To: Commons Developers List
Subject: Re: [crypto] Logging dependency
Hello Dapeng,
Sun, Dapeng schrieb am Mi., 15. Juni 2016 um
11:22 Uhr:
> Thank all for your input!
>
> I will try to remove the log dependence.
>
> About
+1, thank Sebb for adding these comments.
Regards
Dapeng
-Original Message-
From: sebb [mailto:seb...@gmail.com]
Sent: Thursday, June 16, 2016 9:40 PM
To: CommonsDev
Subject: [CRYPTO] JIRA fix comments should please link to the Git change
When fixing a JIRA issue, it's very helpful if t
1.7 as soon as possible, but if the API is
>> > > ready
>> for a
>> > > 1.0 release already, we could wait for 1.1 or 1.2 before going
>> > > full
>> 1.7.
>> > >
>> > > On 14 June 2016 at 06:16, Stian Soiland
Thank all for your input!
I will try to remove the log dependence.
About the logging of native library failure, users of CRYPTO could get the
information about whether native is enabled or native failure reason from
org.apache.commons.crypto.utils.NativeCodeLoader#isNativeCodeLoaded() or
org.a
you mean?
If there are no potential users looking for JDK 1.6, dropping now should be
good idea IMO.
I also remembered that we wanted to mark 1.0.0 release as Alpha right?
(just a question)
Regards,
Uma
On 6/14/16, 12:27 AM, "Sun, Dapeng" wrote:
>Thank Gary, Benedikt, Marcelo, seb
Thank Gary, Benedikt, Marcelo, sebb, James, Jochen, ecki, Ralph and Matt for
all your input.
How about make a conservative decision: regarding the first release(1.0.0), we
keep the JDK version as 1.6, and we wouldn't support JDK 1.6 for the releases
after 1.0.0.
Regards
Dapeng
-Original
Thank Bernd, it seems "mvn verify" can't cover creating binary distribution, I
think we can add it to Jenkins.
Regards
Dapeng
-Original Message-
From: e...@zusammenkunft.net [mailto:e...@zusammenkunft.net]
Sent: Tuesday, June 07, 2016 10:40 AM
To: Commons Developers List
Subject: Re: [c
Thank Gary for pointing it out, The reason sounds good to me, and running tests
didn't cost too much time, I think we can remove " -DskipTests "
Regards
Dapeng
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Tuesday, June 07, 2016 10:37 AM
To: Commons Develop
y" or something like that.
>
> Gary
> On Jun 6, 2016 2:49 AM, "Benedikt Ritter" wrote:
>
>> Hello Dapeng
>>
>> Sun, Dapeng schrieb am Mo., 6. Juni 2016 um
>> 11:13 Uhr:
>>
>> > Hello,
>> >
>> > Apache Commons CRYPTO
on rolling an RC and Friday" or something like that.
Gary
On Jun 6, 2016 2:49 AM, "Benedikt Ritter" wrote:
> Hello Dapeng
>
> Sun, Dapeng schrieb am Mo., 6. Juni 2016 um
> 11:13 Uhr:
>
> > Hello,
> >
> > Apache Commons CRYPTO was established at May
Thank Benedikt.
Regards
Dapeng
-Original Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Monday, June 06, 2016 5:50 PM
To: Commons Developers List
Subject: Re: [CRYPTO]1.0.0 Release Plan
Hello Dapeng
Sun, Dapeng schrieb am Mo., 6. Juni 2016 um
11:13 Uhr:
> He
Hello,
Apache Commons CRYPTO was established at May 9, 2016[1], There are presently
numbers of resolved issues fix in CRYPTO[2]. Recently, we also fixed the legal
issue[3].
With the first release, we can begin to promote CRYPTO to other Apache
components, like Apache Hadoop, Apache Spark, so t
th ControlledSource href=https://www.apache.org/dist/commons/crypto/ - you
would need to duplicate the OpenSSL and JavaSE for that. See
other examples in the XML file.
In the second Version you can say 1.0.0 and later - is it 1.0.0
we're targeting for the first Commons Crypto release?
Thank Stian and Haifeng, I have updated the file at my cms workspace. If the
change is okay for you, I will try to commit it to
http://www.staging.apache.org/licenses/exports/
Index: trunk/content/licenses/exports/index.page/eccnmatrix.xml
l Message-
From: Benedikt Ritter [mailto:brit...@apache.org]
Sent: Tuesday, May 10, 2016 3:34 AM
To: Commons Developers List
Subject: Re: [CRYPTO] How to build CRYPTO on Mac OS 10.11?
Hello again :-)
Benedikt Ritter schrieb am Mo., 9. Mai 2016 um
21:24 Uhr:
> Hello Dapeng,
>
> Sun, Dapeng
I'm agreed. I think we can prepare the first release.
Regards
Dapeng
-Original Message-
From: Chen, Haifeng [mailto:haifeng.c...@intel.com]
Sent: Thursday, May 05, 2016 11:21 AM
To: Commons Developers List
Subject: RE: [CRYPTO] Discuss to proceed the alpha release for Commons Crypto
Sor
Hi Benedikt,
Hope this information will be helpful
1. Upgrade openssl to 1.0.1c above using brew(http://brew.sh/)[1]:
Check your openssl version, by default it's not 1.0.1
$openssl version
OpenSSL 0.9.8r 8 Feb 2011
$ brew search openssl
$ brew install homebrew/versions/openssl101
$ brew link ope
Hi Gary,
Thank you for pointing it out. I will remove the tag of 'affects version'.
Regards
Dapeng
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Thursday, April 28, 2016 1:03 PM
To: Commons Developers List
Subject: Re: [jira] [Updated] (CRYPTO-31) Make fiel
+1 for Apache Commons Crypto
Regards
Dapeng
-Original Message-
From: Gangumalla, Uma [mailto:uma.ganguma...@intel.com]
Sent: Tuesday, March 29, 2016 9:30 AM
To: Commons Developers List
Subject: Re: [DISCUSS][CHIMERA] Name for the new component
Just collected all the proposed names here
46 matches
Mail list logo
