You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "gtantachuco ." <gt...@gmail.com> on 2015/07/11 03:02:19 UTC
Request to post Geode security article
Dev team,
I would like to publish this Geode security article to
https://blogs.apache.org/geode/. Here is the initial draft.
At your convenience, please can you let me know what the next steps would
be to get this published?
Thank you.
--
Best regards,
-Guillermo
Re: Request to post Geode security article
Posted by "gtantachuco ." <gt...@gmail.com>.
Greg,
Please use the attached document instead. I updated the links on the
document to point to:
https://github.com/Pivotal-Open-Source-Hub
Sorry for the inconvenience.
On Tue, Jul 14, 2015 at 1:49 PM, gtantachuco . <gt...@gmail.com>
wrote:
> Thanks Greg. Here is the final version of the article. Also, I transferred
> the Geode sample repo to the POSH organization. They can contact me by
> email: gtantachuco@pivotal.io
>
> On Tue, Jul 14, 2015 at 11:58 AM, Gregory Chase <gc...@pivotal.io> wrote:
>
>> Hi Guillermo,
>> I have given you admin access onto
>> https://github.com/Pivotal-Open-Source-Hub. Please transfer your sample
>> project repository to this Github.
>>
>> Thanks!
>>
>> -Greg
>>
>> On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io> wrote:
>>
>> > As I understand, someone has to post on your behalf now who has access
>> to
>> > the blog. I think I am one such somebody, so let me see how to post it
>> for
>> > you :)
>> >
>> > Is there a particular ID you would like me to attribute it to for
>> someone
>> > who wants to contact you? Twitter for Github or just an email?
>> >
>> > On Tue, Jul 14, 2015 at 9:19 AM, gtantachuco . <gt...@gmail.com>
>> > wrote:
>> >
>> >> Thanks guys for your input. I made the changes you suggested and also
>> made
>> >> Geode sample's Github repo public:
>> >> https://github.com/gtantachuco-pivotal/geode-security-samples
>> >> What would the next steps be?
>> >>
>> >> On Sat, Jul 11, 2015 at 12:07 PM, Jags Ramnarayanan <
>> >> jramnarayan@pivotal.io>
>> >> wrote:
>> >>
>> >> > Guillermo,
>> >> > Glad to see you are still active with Gem. Good article.
>> >> > Few points on a quick glance:
>> >> >
>> >> > - You mention - "Cache server authentication allows a new server to
>> >> join a
>> >> > cluster. The locator is responsible for authenticating credentials of
>> >> said
>> >> > server. The first locator to join the cluster is assumed to be
>> >> > authenticated and subsequent locators authenticate against the first
>> >> one"
>> >> > Strictly speaking it is responsibility of the membership coordinator
>> to
>> >> > authenticate subsequent ones. And, yes, when using locators, the
>> first
>> >> > locator will automatically be the coordinator.
>> >> >
>> >> > - Also important to point out that you should always run Gem cluster
>> in
>> >> a
>> >> > secure domain making it super difficult to spoof the node executing
>> the
>> >> > coordinator.
>> >> >
>> >> > -- Jags
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <
>> gtantachuco@gmail.com>
>> >> > wrote:
>> >> >
>> >> > > Dev team,
>> >> > > I would like to publish this Geode security article to
>> >> > > https://blogs.apache.org/geode/. Here is the initial draft.
>> >> > > At your convenience, please can you let me know what the next steps
>> >> would
>> >> > > be to get this published?
>> >> > >
>> >> > > Thank you.
>> >> > >
>> >> > > --
>> >> > > Best regards,
>> >> > > -Guillermo
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Best regards,
>> >> -Guillermo
>> >>
>> >
>> >
>> >
>> > --
>> > Greg Chase
>> >
>> > Director of Big Data Communities
>> > http://www.pivotal.io/big-data
>> >
>> > Pivotal Software
>> > http://www.pivotal.io/
>> >
>> > 650-215-0477
>> > @GregChase
>> > Blog: http://geekmarketing.biz/
>> >
>> >
>>
>>
>> --
>> Greg Chase
>>
>> Director of Big Data Communities
>> http://www.pivotal.io/big-data
>>
>> Pivotal Software
>> http://www.pivotal.io/
>>
>> 650-215-0477
>> @GregChase
>> Blog: http://geekmarketing.biz/
>>
>
>
>
> --
> Best regards,
> -Guillermo
>
>
--
Best regards,
-Guillermo
Re: Request to post Geode security article
Posted by "gtantachuco ." <gt...@gmail.com>.
Thanks Greg. Here is the final version of the article. Also, I transferred
the Geode sample repo to the POSH organization. They can contact me by
email: gtantachuco@pivotal.io
On Tue, Jul 14, 2015 at 11:58 AM, Gregory Chase <gc...@pivotal.io> wrote:
> Hi Guillermo,
> I have given you admin access onto
> https://github.com/Pivotal-Open-Source-Hub. Please transfer your sample
> project repository to this Github.
>
> Thanks!
>
> -Greg
>
> On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io> wrote:
>
> > As I understand, someone has to post on your behalf now who has access to
> > the blog. I think I am one such somebody, so let me see how to post it
> for
> > you :)
> >
> > Is there a particular ID you would like me to attribute it to for someone
> > who wants to contact you? Twitter for Github or just an email?
> >
> > On Tue, Jul 14, 2015 at 9:19 AM, gtantachuco . <gt...@gmail.com>
> > wrote:
> >
> >> Thanks guys for your input. I made the changes you suggested and also
> made
> >> Geode sample's Github repo public:
> >> https://github.com/gtantachuco-pivotal/geode-security-samples
> >> What would the next steps be?
> >>
> >> On Sat, Jul 11, 2015 at 12:07 PM, Jags Ramnarayanan <
> >> jramnarayan@pivotal.io>
> >> wrote:
> >>
> >> > Guillermo,
> >> > Glad to see you are still active with Gem. Good article.
> >> > Few points on a quick glance:
> >> >
> >> > - You mention - "Cache server authentication allows a new server to
> >> join a
> >> > cluster. The locator is responsible for authenticating credentials of
> >> said
> >> > server. The first locator to join the cluster is assumed to be
> >> > authenticated and subsequent locators authenticate against the first
> >> one"
> >> > Strictly speaking it is responsibility of the membership coordinator
> to
> >> > authenticate subsequent ones. And, yes, when using locators, the first
> >> > locator will automatically be the coordinator.
> >> >
> >> > - Also important to point out that you should always run Gem cluster
> in
> >> a
> >> > secure domain making it super difficult to spoof the node executing
> the
> >> > coordinator.
> >> >
> >> > -- Jags
> >> >
> >> >
> >> >
> >> >
> >> > On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gtantachuco@gmail.com
> >
> >> > wrote:
> >> >
> >> > > Dev team,
> >> > > I would like to publish this Geode security article to
> >> > > https://blogs.apache.org/geode/. Here is the initial draft.
> >> > > At your convenience, please can you let me know what the next steps
> >> would
> >> > > be to get this published?
> >> > >
> >> > > Thank you.
> >> > >
> >> > > --
> >> > > Best regards,
> >> > > -Guillermo
> >> > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> -Guillermo
> >>
> >
> >
> >
> > --
> > Greg Chase
> >
> > Director of Big Data Communities
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
> >
> >
>
>
> --
> Greg Chase
>
> Director of Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
>
--
Best regards,
-Guillermo
Re: Request to post Geode security article
Posted by Gregory Chase <gc...@pivotal.io>.
Hi Guillermo,
I have given you admin access onto
https://github.com/Pivotal-Open-Source-Hub. Please transfer your sample
project repository to this Github.
Thanks!
-Greg
On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io> wrote:
> As I understand, someone has to post on your behalf now who has access to
> the blog. I think I am one such somebody, so let me see how to post it for
> you :)
>
> Is there a particular ID you would like me to attribute it to for someone
> who wants to contact you? Twitter for Github or just an email?
>
> On Tue, Jul 14, 2015 at 9:19 AM, gtantachuco . <gt...@gmail.com>
> wrote:
>
>> Thanks guys for your input. I made the changes you suggested and also made
>> Geode sample's Github repo public:
>> https://github.com/gtantachuco-pivotal/geode-security-samples
>> What would the next steps be?
>>
>> On Sat, Jul 11, 2015 at 12:07 PM, Jags Ramnarayanan <
>> jramnarayan@pivotal.io>
>> wrote:
>>
>> > Guillermo,
>> > Glad to see you are still active with Gem. Good article.
>> > Few points on a quick glance:
>> >
>> > - You mention - "Cache server authentication allows a new server to
>> join a
>> > cluster. The locator is responsible for authenticating credentials of
>> said
>> > server. The first locator to join the cluster is assumed to be
>> > authenticated and subsequent locators authenticate against the first
>> one"
>> > Strictly speaking it is responsibility of the membership coordinator to
>> > authenticate subsequent ones. And, yes, when using locators, the first
>> > locator will automatically be the coordinator.
>> >
>> > - Also important to point out that you should always run Gem cluster in
>> a
>> > secure domain making it super difficult to spoof the node executing the
>> > coordinator.
>> >
>> > -- Jags
>> >
>> >
>> >
>> >
>> > On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
>> > wrote:
>> >
>> > > Dev team,
>> > > I would like to publish this Geode security article to
>> > > https://blogs.apache.org/geode/. Here is the initial draft.
>> > > At your convenience, please can you let me know what the next steps
>> would
>> > > be to get this published?
>> > >
>> > > Thank you.
>> > >
>> > > --
>> > > Best regards,
>> > > -Guillermo
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Best regards,
>> -Guillermo
>>
>
>
>
> --
> Greg Chase
>
> Director of Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
>
>
--
Greg Chase
Director of Big Data Communities
http://www.pivotal.io/big-data
Pivotal Software
http://www.pivotal.io/
650-215-0477
@GregChase
Blog: http://geekmarketing.biz/
Re: Request to post Geode security article
Posted by William Markito <wm...@pivotal.io>.
Cool! Congrats!!
On Wed, Jul 29, 2015 at 11:12 AM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> Thanks to Greg for fighting the Roller and, of course,
> thanks a ton to Guillermo for writing it! The blog is now
> live: https://blogs.apache.org/geode/
>
> On Fri, Jul 17, 2015 at 12:22 PM, Gregory Chase <gc...@pivotal.io> wrote:
> > Ok,
> > I tried to post this article after quite some pain.
> >
> > It turns out the blog site only accepts HTML.
> >
> > For some reason I don't have access to upload or apply images however.
> >
> > Someone else with more access will need to finish this off.
> >
> > -Greg
> >
> > On Wed, Jul 15, 2015 at 5:46 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> > wrote:
> >
> >> On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io>
> wrote:
> >> > As I understand, someone has to post on your behalf now who has
> access to
> >> > the blog. I think I am one such somebody, so let me see how to post
> it
> >> for
> >> > you :)
> >>
> >> Yup ;-) Let me know if you guys need any help, but at this point as
> long as
> >> Greg can create a draft on blogs.apache.org I can then review and
> publish
> >> it.
> >>
> >> Thanks,
> >> Roman.
> >>
> >
> >
> >
> > --
> > Greg Chase
> >
> > Director of Big Data Communities
> > http://www.pivotal.io/big-data
> >
> > Pivotal Software
> > http://www.pivotal.io/
> >
> > 650-215-0477
> > @GregChase
> > Blog: http://geekmarketing.biz/
>
--
William Markito Oliveira
Enterprise Architect
-- For questions about Apache Geode, please write to
*dev@geode.incubator.apache.org
<de...@geode.incubator.apache.org>*
Re: Request to post Geode security article
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
Thanks to Greg for fighting the Roller and, of course,
thanks a ton to Guillermo for writing it! The blog is now
live: https://blogs.apache.org/geode/
On Fri, Jul 17, 2015 at 12:22 PM, Gregory Chase <gc...@pivotal.io> wrote:
> Ok,
> I tried to post this article after quite some pain.
>
> It turns out the blog site only accepts HTML.
>
> For some reason I don't have access to upload or apply images however.
>
> Someone else with more access will need to finish this off.
>
> -Greg
>
> On Wed, Jul 15, 2015 at 5:46 PM, Roman Shaposhnik <ro...@shaposhnik.org>
> wrote:
>
>> On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io> wrote:
>> > As I understand, someone has to post on your behalf now who has access to
>> > the blog. I think I am one such somebody, so let me see how to post it
>> for
>> > you :)
>>
>> Yup ;-) Let me know if you guys need any help, but at this point as long as
>> Greg can create a draft on blogs.apache.org I can then review and publish
>> it.
>>
>> Thanks,
>> Roman.
>>
>
>
>
> --
> Greg Chase
>
> Director of Big Data Communities
> http://www.pivotal.io/big-data
>
> Pivotal Software
> http://www.pivotal.io/
>
> 650-215-0477
> @GregChase
> Blog: http://geekmarketing.biz/
Re: Request to post Geode security article
Posted by Gregory Chase <gc...@pivotal.io>.
Ok,
I tried to post this article after quite some pain.
It turns out the blog site only accepts HTML.
For some reason I don't have access to upload or apply images however.
Someone else with more access will need to finish this off.
-Greg
On Wed, Jul 15, 2015 at 5:46 PM, Roman Shaposhnik <ro...@shaposhnik.org>
wrote:
> On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io> wrote:
> > As I understand, someone has to post on your behalf now who has access to
> > the blog. I think I am one such somebody, so let me see how to post it
> for
> > you :)
>
> Yup ;-) Let me know if you guys need any help, but at this point as long as
> Greg can create a draft on blogs.apache.org I can then review and publish
> it.
>
> Thanks,
> Roman.
>
--
Greg Chase
Director of Big Data Communities
http://www.pivotal.io/big-data
Pivotal Software
http://www.pivotal.io/
650-215-0477
@GregChase
Blog: http://geekmarketing.biz/
Re: Request to post Geode security article
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Tue, Jul 14, 2015 at 9:36 AM, Gregory Chase <gc...@pivotal.io> wrote:
> As I understand, someone has to post on your behalf now who has access to
> the blog. I think I am one such somebody, so let me see how to post it for
> you :)
Yup ;-) Let me know if you guys need any help, but at this point as long as
Greg can create a draft on blogs.apache.org I can then review and publish it.
Thanks,
Roman.
Re: Request to post Geode security article
Posted by Gregory Chase <gc...@pivotal.io>.
As I understand, someone has to post on your behalf now who has access to
the blog. I think I am one such somebody, so let me see how to post it for
you :)
Is there a particular ID you would like me to attribute it to for someone
who wants to contact you? Twitter for Github or just an email?
On Tue, Jul 14, 2015 at 9:19 AM, gtantachuco . <gt...@gmail.com>
wrote:
> Thanks guys for your input. I made the changes you suggested and also made
> Geode sample's Github repo public:
> https://github.com/gtantachuco-pivotal/geode-security-samples
> What would the next steps be?
>
> On Sat, Jul 11, 2015 at 12:07 PM, Jags Ramnarayanan <
> jramnarayan@pivotal.io>
> wrote:
>
> > Guillermo,
> > Glad to see you are still active with Gem. Good article.
> > Few points on a quick glance:
> >
> > - You mention - "Cache server authentication allows a new server to join
> a
> > cluster. The locator is responsible for authenticating credentials of
> said
> > server. The first locator to join the cluster is assumed to be
> > authenticated and subsequent locators authenticate against the first one"
> > Strictly speaking it is responsibility of the membership coordinator to
> > authenticate subsequent ones. And, yes, when using locators, the first
> > locator will automatically be the coordinator.
> >
> > - Also important to point out that you should always run Gem cluster in a
> > secure domain making it super difficult to spoof the node executing the
> > coordinator.
> >
> > -- Jags
> >
> >
> >
> >
> > On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
> > wrote:
> >
> > > Dev team,
> > > I would like to publish this Geode security article to
> > > https://blogs.apache.org/geode/. Here is the initial draft.
> > > At your convenience, please can you let me know what the next steps
> would
> > > be to get this published?
> > >
> > > Thank you.
> > >
> > > --
> > > Best regards,
> > > -Guillermo
> > >
> > >
> >
>
>
>
> --
> Best regards,
> -Guillermo
>
--
Greg Chase
Director of Big Data Communities
http://www.pivotal.io/big-data
Pivotal Software
http://www.pivotal.io/
650-215-0477
@GregChase
Blog: http://geekmarketing.biz/
Re: Request to post Geode security article
Posted by "gtantachuco ." <gt...@gmail.com>.
Thanks guys for your input. I made the changes you suggested and also made
Geode sample's Github repo public:
https://github.com/gtantachuco-pivotal/geode-security-samples
What would the next steps be?
On Sat, Jul 11, 2015 at 12:07 PM, Jags Ramnarayanan <jr...@pivotal.io>
wrote:
> Guillermo,
> Glad to see you are still active with Gem. Good article.
> Few points on a quick glance:
>
> - You mention - "Cache server authentication allows a new server to join a
> cluster. The locator is responsible for authenticating credentials of said
> server. The first locator to join the cluster is assumed to be
> authenticated and subsequent locators authenticate against the first one"
> Strictly speaking it is responsibility of the membership coordinator to
> authenticate subsequent ones. And, yes, when using locators, the first
> locator will automatically be the coordinator.
>
> - Also important to point out that you should always run Gem cluster in a
> secure domain making it super difficult to spoof the node executing the
> coordinator.
>
> -- Jags
>
>
>
>
> On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
> wrote:
>
> > Dev team,
> > I would like to publish this Geode security article to
> > https://blogs.apache.org/geode/. Here is the initial draft.
> > At your convenience, please can you let me know what the next steps would
> > be to get this published?
> >
> > Thank you.
> >
> > --
> > Best regards,
> > -Guillermo
> >
> >
>
--
Best regards,
-Guillermo
Re: Request to post Geode security article
Posted by Jags Ramnarayanan <jr...@pivotal.io>.
Guillermo,
Glad to see you are still active with Gem. Good article.
Few points on a quick glance:
- You mention - "Cache server authentication allows a new server to join a
cluster. The locator is responsible for authenticating credentials of said
server. The first locator to join the cluster is assumed to be
authenticated and subsequent locators authenticate against the first one"
Strictly speaking it is responsibility of the membership coordinator to
authenticate subsequent ones. And, yes, when using locators, the first
locator will automatically be the coordinator.
- Also important to point out that you should always run Gem cluster in a
secure domain making it super difficult to spoof the node executing the
coordinator.
-- Jags
On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
wrote:
> Dev team,
> I would like to publish this Geode security article to
> https://blogs.apache.org/geode/. Here is the initial draft.
> At your convenience, please can you let me know what the next steps would
> be to get this published?
>
> Thank you.
>
> --
> Best regards,
> -Guillermo
>
>
Re: Request to post Geode security article
Posted by Michael Stolz <ms...@pivotal.io>.
I think it need to be "The authorization of operations..."
--
Mike Stolz
Principal Technical Account Manager
Mobile: 631-835-4771
On Jul 11, 2015 10:56 AM, "Anthony Baker" <ab...@pivotal.io> wrote:
> Really nice writeup! One minor suggestion, consider changing
>
> "In terms of authorization operations performed by a client application on
> a cluster can be restricted or completely blocked according to your
> configurations and programmatic authorization callback."
>
> to
>
> “The authorization operations performed by a client application on a
> cluster can be restricted or completely blocked according to your
> configurations and programmatic authorization callback."
>
> Also, is the copyright notice at the end required? I don’t see that on
> many ASF blog posts.
>
> Anthony
>
> > On Jul 10, 2015, at 6:08 PM, William Markito <wm...@pivotal.io>
> wrote:
> >
> > +1 for the article
> >
> > +1 for ASF blog
> >
> > On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
> > wrote:
> >
> >> Dev team,
> >> I would like to publish this Geode security article to
> >> https://blogs.apache.org/geode/. Here is the initial draft.
> >> At your convenience, please can you let me know what the next steps
> would
> >> be to get this published?
> >>
> >> Thank you.
> >>
> >> --
> >> Best regards,
> >> -Guillermo
> >>
> >>
> >
> >
> > --
> >
> > William Markito Oliveira
> > Enterprise Architect
> > -- For questions about Apache Geode, please write to
> > *dev@geode.incubator.apache.org
> > <de...@geode.incubator.apache.org>*
>
>
Re: Request to post Geode security article
Posted by Anthony Baker <ab...@pivotal.io>.
Really nice writeup! One minor suggestion, consider changing
"In terms of authorization operations performed by a client application on a cluster can be restricted or completely blocked according to your configurations and programmatic authorization callback."
to
“The authorization operations performed by a client application on a cluster can be restricted or completely blocked according to your configurations and programmatic authorization callback."
Also, is the copyright notice at the end required? I don’t see that on many ASF blog posts.
Anthony
> On Jul 10, 2015, at 6:08 PM, William Markito <wm...@pivotal.io> wrote:
>
> +1 for the article
>
> +1 for ASF blog
>
> On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
> wrote:
>
>> Dev team,
>> I would like to publish this Geode security article to
>> https://blogs.apache.org/geode/. Here is the initial draft.
>> At your convenience, please can you let me know what the next steps would
>> be to get this published?
>>
>> Thank you.
>>
>> --
>> Best regards,
>> -Guillermo
>>
>>
>
>
> --
>
> William Markito Oliveira
> Enterprise Architect
> -- For questions about Apache Geode, please write to
> *dev@geode.incubator.apache.org
> <de...@geode.incubator.apache.org>*
Re: Request to post Geode security article
Posted by William Markito <wm...@pivotal.io>.
+1 for the article
+1 for ASF blog
On Fri, Jul 10, 2015 at 6:02 PM, gtantachuco . <gt...@gmail.com>
wrote:
> Dev team,
> I would like to publish this Geode security article to
> https://blogs.apache.org/geode/. Here is the initial draft.
> At your convenience, please can you let me know what the next steps would
> be to get this published?
>
> Thank you.
>
> --
> Best regards,
> -Guillermo
>
>
--
William Markito Oliveira
Enterprise Architect
-- For questions about Apache Geode, please write to
*dev@geode.incubator.apache.org
<de...@geode.incubator.apache.org>*