;
>> > > >> > > >>> On Tue, Jun 18, 2019 at 5:06 AM Dmitriy Pavlov <
>> > > >> dpav...@apache.org>
>> > > >> > > >>> wrote:
>> > > >> > > >>>
>> &g
> > and
> > > >> about
> > > >> > > >>> > declaring .NET versions (.NET Core & . NET Classic). By
> > > >> default, I
> > > >> > > >>> propose
> > > >> > > >>> > to keep both.
>
t; > >> > > >>> > Dmitriy Pavlov
> > >> > > >>> >
> > >> > > >>> > пн, 17 июн. 2019 г. в 19:24, Dmitriy Pavlov <
> > dpav...@apache.org
> > >> >:
> > >> > > >>> >
> &
gt;> > >
> >> > > >>> > >
> >> > > >>> >
> >> > > >>>
> >> > >
> >> >
> >>
> https://github.com/apache/ignite/pull/6616/files#diff-1995c8
gt; process
>> > > >>> > and
>> > > >>> > > provide matrix update, add CRYPTO notice (I'll draft it).
>> > > >>> > >
>> > > >>> > > Other products don't declare all possible JDKs -
&g
> > > пн, 17 июн. 2019 г. в 19:11, Pavel Tupitsyn <
> > ptupit...@apache.org
> > > >:
> > > >>> > >
> > > >>> > >> >>Should it go instead of Microsoft? Should we mention .NET
t; > >>> > >>
> > >>> > >> >>to Microsoft?
> > >>> > >>
> > >>> > >>
> > >>> > >>
> > >>> > >> >Yes, I think we can do this. Ignite targets both of the them
t; >>> > >>
> >>> > >> >Pavel may correct me.
> >>> > >>
> >>> > >>
> >>> > >> We use crypto APIs from standard class library. We ship our
> >>> binaries,
>
; > >>
>>> > >> Our binaries can be executed with .NET Core (open-source, MIT
>>> license),
>>> > >> Mono (open-source, MIT license), and .NET Classic (old framework,
>>> > >> Windows-only, Microsoft license).
>>> >
t;> > >>
>> > >> On Mon, Jun 17, 2019 at 5:20 PM Alexandr Shapkin
>> > >> wrote:
>> > >>
>> > >> > >1) Declaring older versions of Ignite.
>> > >> >
>> > >> > >2) Is it correct to menti
gt; wrote:
> > >>
> > >> > >1) Declaring older versions of Ignite.
> > >> >
> > >> > >2) Is it correct to mention that Ignite uses .NET core controlled
> by
> > >> .NET
> > >> >
> > >> > >Foundation? E.g. as
undation
> >> >
> >> > >title=Designed to use .NET Framework Cryptography Model
> >> >
> >> > >href=https://dotnetfoundation.org/projects
> >> >
> >> >
> >> >
> >> > >Should it go instead o
;> >
>> > >Should it go instead of Microsoft? Should we mention .NET code in
>> addition
>> >
>> > >to Microsoft?
>> >
>> >
>> >
>> > Yes, I think we can do this. Ignite targets both of the them. And .NET
>> &
we mention .NET code in
> addition
> >
> > >to Microsoft?
> >
> >
> >
> > Yes, I think we can do this. Ignite targets both of the them. And .NET
> > Core uses it’s own implementation of standard class library[1]
> >
> > Pavel may correct m
itriy Pavlov
> *Sent: *Monday, June 17, 2019 4:35 PM
> *To: *dev
> *Cc: *Denis Magda ; Igor Sapego ; Pavel
> Petroshenko ; Nikolay Izhikov
> *Subject: *Re: Signing off Ignite for export beyond the U.S.
>
>
>
> Thanks, Pavel!
>
>
>
> Denis, Pavel, Igniters,
is. Ignite targets both of the them. And .NET
> Core uses it’s own implementation of standard class library[1]
> Pavel may correct me.
>
> [1] https://github.com/dotnet/corefx
>
> From: Dmitriy Pavlov
> Sent: Monday, June 17, 2019 4:35 PM
> To: dev
> Cc: Denis Magda; Igor S
From: Dmitriy Pavlov
Sent: Monday, June 17, 2019 4:35 PM
To: dev
Cc: Denis Magda; Igor Sapego; Pavel Petroshenko; Nikolay Izhikov
Subject: Re: Signing off Ignite for export beyond the U.S.
Thanks, Pavel!
Denis, Pavel, Igniters, please review the following proposal:
- Python, Node JS, ODBC to b
Igniters,
One more usage,we need to mention at Export matrix data:
<<<
JCraft, Inc.
title=Provides encryption SSH library
href=http://www.jcraft.com/jsch/
>>>
One more thing I would like to declare as an open question:
3) Is it possible to setup HTTPs connection to Ignite Rest
Thanks, Pavel!
Denis, Pavel, Igniters, please review the following proposal:
- Python, Node JS, ODBC to be declared as OpenSSL usage.
- AWS-S3 client-side encryption to be declared as JCA/JCE usage.
- SSLContextFactory usage to be declared as JCA/JCE usage.
- TDE to be declared as JCA/JCE
Export
Hi Denis,
Ignite.NET uses .NET Framework Standard Library for all security and
cryptographic related code. There are no dependencies on external libraries.
Thanks
ср, 12 июн. 2019 г., 21:07 Denis Magda :
> Igniters,
>
> Regardless of the fact that Ignite is an open source software, ASF as an
>
Alexey, Igor, thank you for your replies.
I've found one more usage at Java side:
It is Amazon AWS S3 Client-side encryption:
https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html
See code at:
https://github.com/apache/ignite/blob/master/modules/aws/src/main/java/org/apac
Alex, Igor, thanks for the details. Looks good.
*Pavel Tupitsyn, Aleksandr Shapkin,* could you please help with .NET?
-
Denis
On Thu, Jun 13, 2019 at 2:08 AM Igor Sapego wrote:
> Denis,
>
> C++ thin client and ODBC use OpenSSL to establish secure connection with
> the cluster and do not conta
Denis,
C++ thin client and ODBC use OpenSSL to establish secure connection with
the cluster and do not contain any crypto algorithms in their own code.
Best Regards,
Igor
On Thu, Jun 13, 2019 at 12:56 AM Alexey Kosenchuk <
alexey.kosenc...@nobitlost.com> wrote:
> Hi Denis,
>
> Info about Pytho
Hi Denis,
Info about Python, PHP, Node.JS thin clients:
The clients itself do not contain any cryptographic code but use the
features provided by the underlying platforms.
Python client uses Python's SSL lib [1] which is a wrapper over OpenSSL [2].
Python 2.7 and Python 3.4 require OpenSSL 1.
Igniters,
Regardless of the fact that Ignite is an open source software, ASF as an
entity based in the U.S. has to comply with certain exporting regulations
[1].
Dmitry Pavlov and I are working on adding Ignite to the table [2] of
projects allowed for export and might need the assistance of some
25 matches
Mail list logo
