You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by "Alan D. Cabrera" <li...@toolazydogs.com> on 2008/07/25 08:17:14 UTC

JSecurity name "collisions"

I searched on Google and found these companies using the JSecurity name:

http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
http://joomlaequipment.com/content/view/1/4/

The latter looks like the JSecurity product got absorbed into a  
product called JDefender.  We'll probably need to do a more thorough  
search.


Regards,
Alan


Re: JSecurity name "collisions"

Posted by Sam Ruby <ru...@intertwingly.net>.
On Mon, Aug 11, 2008 at 12:22 AM, Alan D. Cabrera <li...@toolazydogs.com> wrote:
> I haven't heard anything from legal.

The division of responsibilities here is a bit confusing.

Expertise on name selection and inbound IP clearance is found in the
incubator.  This includes existing projects.  From a legal
perspective, certainly don't be provocative, and when possible be risk
adverse.  Neither of these apply to your situation: you have a
preexisting name that to date has not been challenged.

Enforcement of our marks falls to the PRC.  They would be the ones to
decide if registering a trademark is desirable.

- Sam Ruby

---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Re: JSecurity name "collisions"

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I haven't heard anything from legal.


Regards,
Alan

On Jul 25, 2008, at 7:31 AM, Alan D. Cabrera wrote:

> Being around for three years and not having anyone contact the  
> project will not be good enough, although it is promising.  The  
> Incubator status template makes a reference to www.nameprotect.com,  
> but I am not sure how we go about the search and what is the  
> criteria to pass this check.
>
> Can anyone from legal comment?  (Please reply to all)
>
>
> Regards,
> Alan
>
>
>
> On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:
>
>> Yep, we've seen these before, but the good thing is that they're  
>> not related
>> in form or function to our project so there shouldn't be any legal  
>> conflict
>> at least (IANAL, but I think that's the case).  Since the joomla  
>> product has
>> been renamed, I don't think there's any issue there.  Also the  
>> juniper
>> product is named slightly different to J - dash - Security, so  
>> they're not
>> an exact overlap.  This coupled with the different target of their  
>> focus
>> (totally different than ours), I think that makes things 'safe'.
>>
>> Plus in the last 3 or so years, I'm sure they've seen us (just do  
>> any search
>> engine lookup for 'jsecurity' and we're always number one), but no  
>> one has
>> ever contacted us about naming conflicts.  I'm fairly sure they  
>> don't care -
>> if they would have, they'd have said something by now...
>>
>> At least that's my take on it :)
>>
>> I wonder if should investigate purchasing a registered trademark  
>> just in
>> case...
>>
>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <list@toolazydogs.com 
>> >
>> wrote:
>>
>>> I searched on Google and found these companies using the JSecurity  
>>> name:
>>>
>>>
>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>> http://joomlaequipment.com/content/view/1/4/
>>>
>>> The latter looks like the JSecurity product got absorbed into a  
>>> product
>>> called JDefender.  We'll probably need to do a more thorough search.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>
>


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Re: JSecurity name "collisions"

Posted by Craig L Russell <Cr...@Sun.COM>.
On Jul 25, 2008, at 7:31 AM, Alan D. Cabrera wrote:

> Being around for three years and not having anyone contact the  
> project will not be good enough, although it is promising.  The  
> Incubator status template makes a reference to www.nameprotect.com,  
> but I am not sure how we go about the search and what is the  
> criteria to pass this check.

Last I checked (a year ago) this was an obsolete reference.
>
>
> Can anyone from legal comment?  (Please reply to all)


The name checks I've run for other podlings have been a google search  
and analysis of the first few hundred hits.

Craig
>
>
>
>
> Regards,
> Alan
>
>
>
> On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:
>
>> Yep, we've seen these before, but the good thing is that they're  
>> not related
>> in form or function to our project so there shouldn't be any legal  
>> conflict
>> at least (IANAL, but I think that's the case).  Since the joomla  
>> product has
>> been renamed, I don't think there's any issue there.  Also the  
>> juniper
>> product is named slightly different to J - dash - Security, so  
>> they're not
>> an exact overlap.  This coupled with the different target of their  
>> focus
>> (totally different than ours), I think that makes things 'safe'.
>>
>> Plus in the last 3 or so years, I'm sure they've seen us (just do  
>> any search
>> engine lookup for 'jsecurity' and we're always number one), but no  
>> one has
>> ever contacted us about naming conflicts.  I'm fairly sure they  
>> don't care -
>> if they would have, they'd have said something by now...
>>
>> At least that's my take on it :)
>>
>> I wonder if should investigate purchasing a registered trademark  
>> just in
>> case...
>>
>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <list@toolazydogs.com 
>> >
>> wrote:
>>
>>> I searched on Google and found these companies using the JSecurity  
>>> name:
>>>
>>>
>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>> http://joomlaequipment.com/content/view/1/4/
>>>
>>> The latter looks like the JSecurity product got absorbed into a  
>>> product
>>> called JDefender.  We'll probably need to do a more thorough search.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only.  Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF.  See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>

Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Re: JSecurity name "collisions"

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I haven't heard anything from legal.


Regards,
Alan

On Jul 25, 2008, at 7:31 AM, Alan D. Cabrera wrote:

> Being around for three years and not having anyone contact the  
> project will not be good enough, although it is promising.  The  
> Incubator status template makes a reference to www.nameprotect.com,  
> but I am not sure how we go about the search and what is the  
> criteria to pass this check.
>
> Can anyone from legal comment?  (Please reply to all)
>
>
> Regards,
> Alan
>
>
>
> On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:
>
>> Yep, we've seen these before, but the good thing is that they're  
>> not related
>> in form or function to our project so there shouldn't be any legal  
>> conflict
>> at least (IANAL, but I think that's the case).  Since the joomla  
>> product has
>> been renamed, I don't think there's any issue there.  Also the  
>> juniper
>> product is named slightly different to J - dash - Security, so  
>> they're not
>> an exact overlap.  This coupled with the different target of their  
>> focus
>> (totally different than ours), I think that makes things 'safe'.
>>
>> Plus in the last 3 or so years, I'm sure they've seen us (just do  
>> any search
>> engine lookup for 'jsecurity' and we're always number one), but no  
>> one has
>> ever contacted us about naming conflicts.  I'm fairly sure they  
>> don't care -
>> if they would have, they'd have said something by now...
>>
>> At least that's my take on it :)
>>
>> I wonder if should investigate purchasing a registered trademark  
>> just in
>> case...
>>
>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <list@toolazydogs.com 
>> >
>> wrote:
>>
>>> I searched on Google and found these companies using the JSecurity  
>>> name:
>>>
>>>
>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>> http://joomlaequipment.com/content/view/1/4/
>>>
>>> The latter looks like the JSecurity product got absorbed into a  
>>> product
>>> called JDefender.  We'll probably need to do a more thorough search.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>
>


Re: JSecurity name "collisions"

Posted by Craig L Russell <Cr...@Sun.COM>.
On Jul 25, 2008, at 7:31 AM, Alan D. Cabrera wrote:

> Being around for three years and not having anyone contact the  
> project will not be good enough, although it is promising.  The  
> Incubator status template makes a reference to www.nameprotect.com,  
> but I am not sure how we go about the search and what is the  
> criteria to pass this check.

Last I checked (a year ago) this was an obsolete reference.
>
>
> Can anyone from legal comment?  (Please reply to all)


The name checks I've run for other podlings have been a google search  
and analysis of the first few hundred hits.

Craig
>
>
>
>
> Regards,
> Alan
>
>
>
> On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:
>
>> Yep, we've seen these before, but the good thing is that they're  
>> not related
>> in form or function to our project so there shouldn't be any legal  
>> conflict
>> at least (IANAL, but I think that's the case).  Since the joomla  
>> product has
>> been renamed, I don't think there's any issue there.  Also the  
>> juniper
>> product is named slightly different to J - dash - Security, so  
>> they're not
>> an exact overlap.  This coupled with the different target of their  
>> focus
>> (totally different than ours), I think that makes things 'safe'.
>>
>> Plus in the last 3 or so years, I'm sure they've seen us (just do  
>> any search
>> engine lookup for 'jsecurity' and we're always number one), but no  
>> one has
>> ever contacted us about naming conflicts.  I'm fairly sure they  
>> don't care -
>> if they would have, they'd have said something by now...
>>
>> At least that's my take on it :)
>>
>> I wonder if should investigate purchasing a registered trademark  
>> just in
>> case...
>>
>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <list@toolazydogs.com 
>> >
>> wrote:
>>
>>> I searched on Google and found these companies using the JSecurity  
>>> name:
>>>
>>>
>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>> http://joomlaequipment.com/content/view/1/4/
>>>
>>> The latter looks like the JSecurity product got absorbed into a  
>>> product
>>> called JDefender.  We'll probably need to do a more thorough search.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>
>
> ---------------------------------------------------------------------
> DISCLAIMER: Discussions on this list are informational and educational
> only.  Statements made on this list are not privileged, do not
> constitute legal advice, and do not necessarily reflect the opinions
> and policies of the ASF.  See <http://www.apache.org/licenses/> for
> official ASF policies and documents.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
> For additional commands, e-mail: legal-discuss-help@apache.org
>

Craig L Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


Re: JSecurity name "collisions"

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I haven't heard anything from legal.


Regards,
Alan

On Jul 25, 2008, at 7:31 AM, Alan D. Cabrera wrote:

> Being around for three years and not having anyone contact the  
> project will not be good enough, although it is promising.  The  
> Incubator status template makes a reference to www.nameprotect.com,  
> but I am not sure how we go about the search and what is the  
> criteria to pass this check.
>
> Can anyone from legal comment?  (Please reply to all)
>
>
> Regards,
> Alan
>
>
>
> On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:
>
>> Yep, we've seen these before, but the good thing is that they're  
>> not related
>> in form or function to our project so there shouldn't be any legal  
>> conflict
>> at least (IANAL, but I think that's the case).  Since the joomla  
>> product has
>> been renamed, I don't think there's any issue there.  Also the  
>> juniper
>> product is named slightly different to J - dash - Security, so  
>> they're not
>> an exact overlap.  This coupled with the different target of their  
>> focus
>> (totally different than ours), I think that makes things 'safe'.
>>
>> Plus in the last 3 or so years, I'm sure they've seen us (just do  
>> any search
>> engine lookup for 'jsecurity' and we're always number one), but no  
>> one has
>> ever contacted us about naming conflicts.  I'm fairly sure they  
>> don't care -
>> if they would have, they'd have said something by now...
>>
>> At least that's my take on it :)
>>
>> I wonder if should investigate purchasing a registered trademark  
>> just in
>> case...
>>
>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <list@toolazydogs.com 
>> >
>> wrote:
>>
>>> I searched on Google and found these companies using the JSecurity  
>>> name:
>>>
>>>
>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>> http://joomlaequipment.com/content/view/1/4/
>>>
>>> The latter looks like the JSecurity product got absorbed into a  
>>> product
>>> called JDefender.  We'll probably need to do a more thorough search.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: JSecurity name "collisions"

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Being around for three years and not having anyone contact the project  
will not be good enough, although it is promising.  The Incubator  
status template makes a reference to www.nameprotect.com, but I am not  
sure how we go about the search and what is the criteria to pass this  
check.

Can anyone from legal comment?  (Please reply to all)


Regards,
Alan



On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:

> Yep, we've seen these before, but the good thing is that they're not  
> related
> in form or function to our project so there shouldn't be any legal  
> conflict
> at least (IANAL, but I think that's the case).  Since the joomla  
> product has
> been renamed, I don't think there's any issue there.  Also the juniper
> product is named slightly different to J - dash - Security, so  
> they're not
> an exact overlap.  This coupled with the different target of their  
> focus
> (totally different than ours), I think that makes things 'safe'.
>
> Plus in the last 3 or so years, I'm sure they've seen us (just do  
> any search
> engine lookup for 'jsecurity' and we're always number one), but no  
> one has
> ever contacted us about naming conflicts.  I'm fairly sure they  
> don't care -
> if they would have, they'd have said something by now...
>
> At least that's my take on it :)
>
> I wonder if should investigate purchasing a registered trademark  
> just in
> case...
>
> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera  
> <li...@toolazydogs.com>
> wrote:
>
>> I searched on Google and found these companies using the JSecurity  
>> name:
>>
>>
>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>> http://joomlaequipment.com/content/view/1/4/
>>
>> The latter looks like the JSecurity product got absorbed into a  
>> product
>> called JDefender.  We'll probably need to do a more thorough search.
>>
>>
>> Regards,
>> Alan
>>
>>


---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only.  Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF.  See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Re: JSecurity name "collisions"

Posted by Les Hazlewood <le...@hazlewood.com>.
Thanks Joe!

On Fri, Jul 25, 2008 at 10:19 AM, Joe Schaefer <jo...@yahoo.com>wrote:

> There is no list called legal@apache.org.  Perhaps you meant
> either legal-discuss@apache.org (publicly archived) or
> legal-internal@apache.org (private)?
>
> --- On Fri, 7/25/08, Les Hazlewood <le...@hazlewood.com> wrote:
>
> > From: Les Hazlewood <le...@hazlewood.com>
> > Subject: Re: JSecurity name "collisions"
> > To: "JSecurity Developer List" <js...@incubator.apache.org>
> > Cc: infrastructure@apache.org
> > Date: Friday, July 25, 2008, 10:10 AM
> > Um, I couldn't send mail to that email address (cc'd
> > infrastructure to see
> > if it is related to Apache email servers again).  I got an
> > immediate
> > bounce-back:
> >
> > "This is an automatically generated Delivery Status
> > Notification
> >
> > Delivery to the following recipient failed permanently:
> >
> >     legal@apache.org
> >
> > Technical details of permanent failure:
> > Google tried to deliver your message, but it was rejected
> > by the recipient
> > domain. We recommend contacting the other email provider
> > for further
> > information about the cause of this error. The error that
> > the other server
> > returned was: 550 550 mail to legal@apache.org not accepted
> > here (state
> > 14)."
> >
> > On Fri, Jul 25, 2008 at 10:08 AM, Les Hazlewood
> > <le...@hazlewood.com> wrote:
> >
> > > I've CCd them to see what feedback they may have.
> > How do we ensure that we
> > > can use the name?
> > >
> > > Thanks,
> > >
> > > Les
> > >
> > >
> > > On Fri, Jul 25, 2008 at 9:36 AM, Emmanuel Lecharny
> > <el...@gmail.com>
> > > wrote:
> > >
> > >> Hi,
> > >>
> > >> it would be a good idea to run the question by
> > legal@apache.org.
> > >>
> > >>
> > >>
> > >>
> > >> Les Hazlewood wrote:
> > >>
> > >>> Yep, we've seen these before, but the good
> > thing is that they're not
> > >>> related
> > >>> in form or function to our project so there
> > shouldn't be any legal
> > >>> conflict
> > >>> at least (IANAL, but I think that's the
> > case).  Since the joomla product
> > >>> has
> > >>> been renamed, I don't think there's
> > any issue there.  Also the juniper
> > >>> product is named slightly different to J -
> > dash - Security, so they're
> > >>> not
> > >>> an exact overlap.  This coupled with the
> > different target of their focus
> > >>> (totally different than ours), I think that
> > makes things 'safe'.
> > >>>
> > >>> Plus in the last 3 or so years, I'm sure
> > they've seen us (just do any
> > >>> search
> > >>> engine lookup for 'jsecurity' and
> > we're always number one), but no one
> > >>> has
> > >>> ever contacted us about naming conflicts.
> > I'm fairly sure they don't
> > >>> care -
> > >>> if they would have, they'd have said
> > something by now...
> > >>>
> > >>> At least that's my take on it :)
> > >>>
> > >>> I wonder if should investigate purchasing a
> > registered trademark just in
> > >>> case...
> > >>>
> > >>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D.
> > Cabrera <li...@toolazydogs.com>
> > >>> wrote:
> > >>>
> > >>>
> > >>>
> > >>>> I searched on Google and found these
> > companies using the JSecurity name:
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> >
> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
> > >>>>
> > http://joomlaequipment.com/content/view/1/4/
> > >>>>
> > >>>> The latter looks like the JSecurity
> > product got absorbed into a product
> > >>>> called JDefender.  We'll probably need
> > to do a more thorough search.
> > >>>>
> > >>>>
> > >>>> Regards,
> > >>>> Alan
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> --
> > >> cordialement, regards,
> > >> Emmanuel Lécharny
> > >> www.iktek.com
> > >> directory.apache.org
> > >>
> > >>
> > >>
> > >
>
>
>
>

Re: JSecurity name "collisions"

Posted by Joe Schaefer <jo...@yahoo.com>.
There is no list called legal@apache.org.  Perhaps you meant
either legal-discuss@apache.org (publicly archived) or
legal-internal@apache.org (private)?

--- On Fri, 7/25/08, Les Hazlewood <le...@hazlewood.com> wrote:

> From: Les Hazlewood <le...@hazlewood.com>
> Subject: Re: JSecurity name "collisions"
> To: "JSecurity Developer List" <js...@incubator.apache.org>
> Cc: infrastructure@apache.org
> Date: Friday, July 25, 2008, 10:10 AM
> Um, I couldn't send mail to that email address (cc'd
> infrastructure to see
> if it is related to Apache email servers again).  I got an
> immediate
> bounce-back:
> 
> "This is an automatically generated Delivery Status
> Notification
> 
> Delivery to the following recipient failed permanently:
> 
>     legal@apache.org
> 
> Technical details of permanent failure:
> Google tried to deliver your message, but it was rejected
> by the recipient
> domain. We recommend contacting the other email provider
> for further
> information about the cause of this error. The error that
> the other server
> returned was: 550 550 mail to legal@apache.org not accepted
> here (state
> 14)."
> 
> On Fri, Jul 25, 2008 at 10:08 AM, Les Hazlewood
> <le...@hazlewood.com> wrote:
> 
> > I've CCd them to see what feedback they may have. 
> How do we ensure that we
> > can use the name?
> >
> > Thanks,
> >
> > Les
> >
> >
> > On Fri, Jul 25, 2008 at 9:36 AM, Emmanuel Lecharny
> <el...@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> it would be a good idea to run the question by
> legal@apache.org.
> >>
> >>
> >>
> >>
> >> Les Hazlewood wrote:
> >>
> >>> Yep, we've seen these before, but the good
> thing is that they're not
> >>> related
> >>> in form or function to our project so there
> shouldn't be any legal
> >>> conflict
> >>> at least (IANAL, but I think that's the
> case).  Since the joomla product
> >>> has
> >>> been renamed, I don't think there's
> any issue there.  Also the juniper
> >>> product is named slightly different to J -
> dash - Security, so they're
> >>> not
> >>> an exact overlap.  This coupled with the
> different target of their focus
> >>> (totally different than ours), I think that
> makes things 'safe'.
> >>>
> >>> Plus in the last 3 or so years, I'm sure
> they've seen us (just do any
> >>> search
> >>> engine lookup for 'jsecurity' and
> we're always number one), but no one
> >>> has
> >>> ever contacted us about naming conflicts. 
> I'm fairly sure they don't
> >>> care -
> >>> if they would have, they'd have said
> something by now...
> >>>
> >>> At least that's my take on it :)
> >>>
> >>> I wonder if should investigate purchasing a
> registered trademark just in
> >>> case...
> >>>
> >>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D.
> Cabrera <li...@toolazydogs.com>
> >>> wrote:
> >>>
> >>>
> >>>
> >>>> I searched on Google and found these
> companies using the JSecurity name:
> >>>>
> >>>>
> >>>>
> >>>>
> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
> >>>>
> http://joomlaequipment.com/content/view/1/4/
> >>>>
> >>>> The latter looks like the JSecurity
> product got absorbed into a product
> >>>> called JDefender.  We'll probably need
> to do a more thorough search.
> >>>>
> >>>>
> >>>> Regards,
> >>>> Alan
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> --
> >> cordialement, regards,
> >> Emmanuel Lécharny
> >> www.iktek.com
> >> directory.apache.org
> >>
> >>
> >>
> >


      

Re: JSecurity name "collisions"

Posted by Les Hazlewood <le...@hazlewood.com>.
Um, I couldn't send mail to that email address (cc'd infrastructure to see
if it is related to Apache email servers again).  I got an immediate
bounce-back:

"This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    legal@apache.org

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient
domain. We recommend contacting the other email provider for further
information about the cause of this error. The error that the other server
returned was: 550 550 mail to legal@apache.org not accepted here (state
14)."

On Fri, Jul 25, 2008 at 10:08 AM, Les Hazlewood <le...@hazlewood.com> wrote:

> I've CCd them to see what feedback they may have.  How do we ensure that we
> can use the name?
>
> Thanks,
>
> Les
>
>
> On Fri, Jul 25, 2008 at 9:36 AM, Emmanuel Lecharny <el...@gmail.com>
> wrote:
>
>> Hi,
>>
>> it would be a good idea to run the question by legal@apache.org.
>>
>>
>>
>>
>> Les Hazlewood wrote:
>>
>>> Yep, we've seen these before, but the good thing is that they're not
>>> related
>>> in form or function to our project so there shouldn't be any legal
>>> conflict
>>> at least (IANAL, but I think that's the case).  Since the joomla product
>>> has
>>> been renamed, I don't think there's any issue there.  Also the juniper
>>> product is named slightly different to J - dash - Security, so they're
>>> not
>>> an exact overlap.  This coupled with the different target of their focus
>>> (totally different than ours), I think that makes things 'safe'.
>>>
>>> Plus in the last 3 or so years, I'm sure they've seen us (just do any
>>> search
>>> engine lookup for 'jsecurity' and we're always number one), but no one
>>> has
>>> ever contacted us about naming conflicts.  I'm fairly sure they don't
>>> care -
>>> if they would have, they'd have said something by now...
>>>
>>> At least that's my take on it :)
>>>
>>> I wonder if should investigate purchasing a registered trademark just in
>>> case...
>>>
>>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <li...@toolazydogs.com>
>>> wrote:
>>>
>>>
>>>
>>>> I searched on Google and found these companies using the JSecurity name:
>>>>
>>>>
>>>>
>>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>>> http://joomlaequipment.com/content/view/1/4/
>>>>
>>>> The latter looks like the JSecurity product got absorbed into a product
>>>> called JDefender.  We'll probably need to do a more thorough search.
>>>>
>>>>
>>>> Regards,
>>>> Alan
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> --
>> --
>> cordialement, regards,
>> Emmanuel Lécharny
>> www.iktek.com
>> directory.apache.org
>>
>>
>>
>

Re: JSecurity name "collisions"

Posted by Les Hazlewood <le...@hazlewood.com>.
I've CCd them to see what feedback they may have.  How do we ensure that we
can use the name?

Thanks,

Les

On Fri, Jul 25, 2008 at 9:36 AM, Emmanuel Lecharny <el...@gmail.com>
wrote:

> Hi,
>
> it would be a good idea to run the question by legal@apache.org.
>
>
>
>
> Les Hazlewood wrote:
>
>> Yep, we've seen these before, but the good thing is that they're not
>> related
>> in form or function to our project so there shouldn't be any legal
>> conflict
>> at least (IANAL, but I think that's the case).  Since the joomla product
>> has
>> been renamed, I don't think there's any issue there.  Also the juniper
>> product is named slightly different to J - dash - Security, so they're not
>> an exact overlap.  This coupled with the different target of their focus
>> (totally different than ours), I think that makes things 'safe'.
>>
>> Plus in the last 3 or so years, I'm sure they've seen us (just do any
>> search
>> engine lookup for 'jsecurity' and we're always number one), but no one has
>> ever contacted us about naming conflicts.  I'm fairly sure they don't care
>> -
>> if they would have, they'd have said something by now...
>>
>> At least that's my take on it :)
>>
>> I wonder if should investigate purchasing a registered trademark just in
>> case...
>>
>> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <li...@toolazydogs.com>
>> wrote:
>>
>>
>>
>>> I searched on Google and found these companies using the JSecurity name:
>>>
>>>
>>>
>>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>>> http://joomlaequipment.com/content/view/1/4/
>>>
>>> The latter looks like the JSecurity product got absorbed into a product
>>> called JDefender.  We'll probably need to do a more thorough search.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> --
> cordialement, regards,
> Emmanuel Lécharny
> www.iktek.com
> directory.apache.org
>
>
>

Re: JSecurity name "collisions"

Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi,

it would be a good idea to run the question by legal@apache.org.



Les Hazlewood wrote:
> Yep, we've seen these before, but the good thing is that they're not related
> in form or function to our project so there shouldn't be any legal conflict
> at least (IANAL, but I think that's the case).  Since the joomla product has
> been renamed, I don't think there's any issue there.  Also the juniper
> product is named slightly different to J - dash - Security, so they're not
> an exact overlap.  This coupled with the different target of their focus
> (totally different than ours), I think that makes things 'safe'.
>
> Plus in the last 3 or so years, I'm sure they've seen us (just do any search
> engine lookup for 'jsecurity' and we're always number one), but no one has
> ever contacted us about naming conflicts.  I'm fairly sure they don't care -
> if they would have, they'd have said something by now...
>
> At least that's my take on it :)
>
> I wonder if should investigate purchasing a registered trademark just in
> case...
>
> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <li...@toolazydogs.com>
> wrote:
>
>   
>> I searched on Google and found these companies using the JSecurity name:
>>
>>
>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>> http://joomlaequipment.com/content/view/1/4/
>>
>> The latter looks like the JSecurity product got absorbed into a product
>> called JDefender.  We'll probably need to do a more thorough search.
>>
>>
>> Regards,
>> Alan
>>
>>
>>     
>
>   


-- 
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org



Re: JSecurity name "collisions"

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Being around for three years and not having anyone contact the project  
will not be good enough, although it is promising.  The Incubator  
status template makes a reference to www.nameprotect.com, but I am not  
sure how we go about the search and what is the criteria to pass this  
check.

Can anyone from legal comment?  (Please reply to all)


Regards,
Alan



On Jul 25, 2008, at 6:15 AM, Les Hazlewood wrote:

> Yep, we've seen these before, but the good thing is that they're not  
> related
> in form or function to our project so there shouldn't be any legal  
> conflict
> at least (IANAL, but I think that's the case).  Since the joomla  
> product has
> been renamed, I don't think there's any issue there.  Also the juniper
> product is named slightly different to J - dash - Security, so  
> they're not
> an exact overlap.  This coupled with the different target of their  
> focus
> (totally different than ours), I think that makes things 'safe'.
>
> Plus in the last 3 or so years, I'm sure they've seen us (just do  
> any search
> engine lookup for 'jsecurity' and we're always number one), but no  
> one has
> ever contacted us about naming conflicts.  I'm fairly sure they  
> don't care -
> if they would have, they'd have said something by now...
>
> At least that's my take on it :)
>
> I wonder if should investigate purchasing a registered trademark  
> just in
> case...
>
> On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera  
> <li...@toolazydogs.com>
> wrote:
>
>> I searched on Google and found these companies using the JSecurity  
>> name:
>>
>>
>> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
>> http://joomlaequipment.com/content/view/1/4/
>>
>> The latter looks like the JSecurity product got absorbed into a  
>> product
>> called JDefender.  We'll probably need to do a more thorough search.
>>
>>
>> Regards,
>> Alan
>>
>>


Re: JSecurity name "collisions"

Posted by Les Hazlewood <le...@hazlewood.com>.
Yep, we've seen these before, but the good thing is that they're not related
in form or function to our project so there shouldn't be any legal conflict
at least (IANAL, but I think that's the case).  Since the joomla product has
been renamed, I don't think there's any issue there.  Also the juniper
product is named slightly different to J - dash - Security, so they're not
an exact overlap.  This coupled with the different target of their focus
(totally different than ours), I think that makes things 'safe'.

Plus in the last 3 or so years, I'm sure they've seen us (just do any search
engine lookup for 'jsecurity' and we're always number one), but no one has
ever contacted us about naming conflicts.  I'm fairly sure they don't care -
if they would have, they'd have said something by now...

At least that's my take on it :)

I wonder if should investigate purchasing a registered trademark just in
case...

On Fri, Jul 25, 2008 at 2:17 AM, Alan D. Cabrera <li...@toolazydogs.com>
wrote:

> I searched on Google and found these companies using the JSecurity name:
>
>
> http://www.juniper.net/security/index.html?from=HomePage-Header-to-JSecurity
> http://joomlaequipment.com/content/view/1/4/
>
> The latter looks like the JSecurity product got absorbed into a product
> called JDefender.  We'll probably need to do a more thorough search.
>
>
> Regards,
> Alan
>
>