You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Mario Ivanac <ma...@est.tech> on 2019/12/09 10:37:06 UTC
Odg: Proposal of new config property "ssl-server-name-extension"
Hi,
Since this proposal is open for almost three weeks,
and we have 2 plus one,
We will continue with proposed solution.
Regards,
Mario
________________________________
Šalje: Mario Ivanac <ma...@est.tech>
Poslano: 19. studenog 2019. 12:26
Prima: dev@geode.apache.org <de...@geode.apache.org>
Predmet: Proposal of new config property "ssl-server-name-extension"
Hi geode dev,
as a part of solution for https://issues.apache.org/jira/browse/GEODE-7414
we would like to introduce new config property "ssl-server-name-extension".
This property will contain generic string, which will be added as Server Name Indication (SNI) parameter to Client Hello message.
Do you agree with this proposal?
Thanks,
Mario
Odg: Odg: Proposal of new config property "ssl-server-name-extension"
Posted by Mario Ivanac <ma...@est.tech>.
Hi,
I agree with your proposal/question,
and implementation will follow it.
BR,
Mario
________________________________
Šalje: Jens Deppe <jd...@pivotal.io>
Poslano: 9. prosinca 2019. 15:55
Prima: dev@geode.apache.org <de...@geode.apache.org>
Predmet: Re: Odg: Proposal of new config property "ssl-server-name-extension"
Hi Mario,
I did have a question / suggestion about this proposal (possibly on a
different thread). Would you mind responding to that before proceeding
please. I'll just paste it in here too.
> Jens Deppe <jd...@pivotal.io>
> Tue, Nov 19, 4:42 PM
> to dev
> I'd like to add my comment from the original PR here again:
>
>
> Although I support the particular use case, I would prefer the
> implementation being a bit more abstracted. Specifically, if we provided an
> extension point which would allow modification of SSLParameters then we
> wouldn't be coupling to a particular use case. So I'm thinking that the
> user would define (via say a ssl-parameter-extension parameter) a class
> that takes in a SSLParameter and perhaps SSLConfig and whatever else for
> this use-case and does what it needs. The user class would need to
> implement an interface something like this:
>
> public interface SSLParameterExtension {
> SSLParameter modify(SSLParameter, SSLConfig);
> }
>
> I would imagine seeing the user implementation of this being attached to
> SSLConfig.
>
>
> (https://github.com/apache/geode/pull/4310)
>
> I don't mind (mis)using the Server Name field to convey some other
> information, but since it's possible to abstract the specific nature and
> application of that information, I think we should do so. Anyone else who
> looks at the code is going to wonder what the use is especially if the
> consumer of that particular piece of info is going to be provided via an
> external SSLEngine implementation.
>
>
Thanks!
--Jens
On Mon, Dec 9, 2019 at 2:37 AM Mario Ivanac <ma...@est.tech> wrote:
> Hi,
>
> Since this proposal is open for almost three weeks,
> and we have 2 plus one,
>
> We will continue with proposed solution.
>
> Regards,
> Mario
>
> ________________________________
> Šalje: Mario Ivanac <ma...@est.tech>
> Poslano: 19. studenog 2019. 12:26
> Prima: dev@geode.apache.org <de...@geode.apache.org>
> Predmet: Proposal of new config property "ssl-server-name-extension"
>
> Hi geode dev,
>
> as a part of solution for https://issues.apache.org/jira/browse/GEODE-7414
> we would like to introduce new config property "ssl-server-name-extension".
>
> This property will contain generic string, which will be added as Server
> Name Indication (SNI) parameter to Client Hello message.
>
> Do you agree with this proposal?
>
> Thanks,
> Mario
>
Re: Odg: Proposal of new config property "ssl-server-name-extension"
Posted by Jens Deppe <jd...@pivotal.io>.
Hi Mario,
I did have a question / suggestion about this proposal (possibly on a
different thread). Would you mind responding to that before proceeding
please. I'll just paste it in here too.
> Jens Deppe <jd...@pivotal.io>
> Tue, Nov 19, 4:42 PM
> to dev
> I'd like to add my comment from the original PR here again:
>
>
> Although I support the particular use case, I would prefer the
> implementation being a bit more abstracted. Specifically, if we provided an
> extension point which would allow modification of SSLParameters then we
> wouldn't be coupling to a particular use case. So I'm thinking that the
> user would define (via say a ssl-parameter-extension parameter) a class
> that takes in a SSLParameter and perhaps SSLConfig and whatever else for
> this use-case and does what it needs. The user class would need to
> implement an interface something like this:
>
> public interface SSLParameterExtension {
> SSLParameter modify(SSLParameter, SSLConfig);
> }
>
> I would imagine seeing the user implementation of this being attached to
> SSLConfig.
>
>
> (https://github.com/apache/geode/pull/4310)
>
> I don't mind (mis)using the Server Name field to convey some other
> information, but since it's possible to abstract the specific nature and
> application of that information, I think we should do so. Anyone else who
> looks at the code is going to wonder what the use is especially if the
> consumer of that particular piece of info is going to be provided via an
> external SSLEngine implementation.
>
>
Thanks!
--Jens
On Mon, Dec 9, 2019 at 2:37 AM Mario Ivanac <ma...@est.tech> wrote:
> Hi,
>
> Since this proposal is open for almost three weeks,
> and we have 2 plus one,
>
> We will continue with proposed solution.
>
> Regards,
> Mario
>
> ________________________________
> Šalje: Mario Ivanac <ma...@est.tech>
> Poslano: 19. studenog 2019. 12:26
> Prima: dev@geode.apache.org <de...@geode.apache.org>
> Predmet: Proposal of new config property "ssl-server-name-extension"
>
> Hi geode dev,
>
> as a part of solution for https://issues.apache.org/jira/browse/GEODE-7414
> we would like to introduce new config property "ssl-server-name-extension".
>
> This property will contain generic string, which will be added as Server
> Name Indication (SNI) parameter to Client Hello message.
>
> Do you agree with this proposal?
>
> Thanks,
> Mario
>