Re: [Fwknop-discuss] help with naming?

[Suno Ano <suno.ano@su...>]

 JB> I favor the name fwknop; the full form of it successfully define
 JB> what actually it is.

me too. fwknop is a known name already. Rebranding it is just going to
confuse folks for no good reason.

[Fwknop-discuss] help with naming?

[Michael Rash <mbr@ci...>]

Hi all,

With the advent of the new libfko C implementation, what do you all
think about the possibility of coming up with a new project name for
fwknop?  The fwknop name has never really been very easy to understand
or identify with, and it initially was used to emphasize "port
knocking" since SPA didn't exist yet at that time (2004).

A couple of candidates for a new name might be:

"spans" (short for Single Packet Authorization Network Shield)
"spacer" (an SPA gap that must be crossed to access a service)

These are just ideas for words that begin with "SPA".  All input is
welcome.  Would people like to see a new name?  If so, are there some
other candidate names that people would like?

Thanks,

-- 
Michael Rash | Founder
http://www.cipherdyne.org/
Key fingerprint: E2EF 0C8A 5AA9 654C 4763  B50F 37AC E946 7F51 8271

Re: [Fwknop-discuss] help with naming?

[J. Bakshi <joydeep@in...>]

Michael Rash wrote:
> Hi all,
>
> With the advent of the new libfko C implementation, what do you all
> think about the possibility of coming up with a new project name for
> fwknop?  The fwknop name has never really been very easy to understand
> or identify with, and it initially was used to emphasize "port
> knocking" since SPA didn't exist yet at that time (2004).
>
> A couple of candidates for a new name might be:
>
> "spans" (short for Single Packet Authorization Network Shield)
> "spacer" (an SPA gap that must be crossed to access a service)
>
> These are just ideas for words that begin with "SPA".  All input is
> welcome.  Would people like to see a new name?  

I favor the name fwknop; the full form of it successfully define what
actually it is.



> If so, are there some
> other candidate names that people would like?
>
> Thanks,
>
>   

Re: [Fwknop-discuss] help with naming?

[Franck Joncourt <franck.mail@dt...>]

J. Bakshi wrote:
> Michael Rash wrote:

>> With the advent of the new libfko C implementation, what do you all
>> think about the possibility of coming up with a new project name for
>> fwknop?  The fwknop name has never really been very easy to understand
>> or identify with, and it initially was used to emphasize "port
>> knocking" since SPA didn't exist yet at that time (2004).
>>
>> A couple of candidates for a new name might be:
>>
>> "spans" (short for Single Packet Authorization Network Shield)
>> "spacer" (an SPA gap that must be crossed to access a service)
>>
>> These are just ideas for words that begin with "SPA".  All input is
>> welcome.  Would people like to see a new name?  
> 
> I favor the name fwknop; the full form of it successfully define what
> actually it is.

Currently, the Fwknop project provides both fwknopd and fwknop. Next, we
have Fwknop-c which provides fwknop as well, but requires fwknopd from
the Fwknop project.

So, I can install fwknopd from Fwknop and fwknop from fwknop-c. Renaming
fwknop-c in Fwknop is confusing and we are unable to make any difference
between the two projects. To stick to Fwknop, both projects would have
to be merged together.

PS: I am out of town this week, do not expect any quick reply :)

Regards,

-- 
Franck Joncourt
http://debian.org - http://smhteam.info/wiki/

Re: [Fwknop-discuss] help with naming?

[Suno Ano <suno.ano@su...>]

 JB> I favor the name fwknop; the full form of it successfully define
 JB> what actually it is.

me too. fwknop is a known name already. Rebranding it is just going to
confuse folks for no good reason.

Re: [Fwknop-discuss] help with naming?

[leandro almeida <lcavalcanti.almeida@gm...>]

I liked the spans, but I do not think the bad FWKNOP.


2009/8/10 Michael Rash <mbr@...>:
> Hi all,
>
> With the advent of the new libfko C implementation, what do you all
> think about the possibility of coming up with a new project name for
> fwknop?  The fwknop name has never really been very easy to understand
> or identify with, and it initially was used to emphasize "port
> knocking" since SPA didn't exist yet at that time (2004).
>
> A couple of candidates for a new name might be:
>
> "spans" (short for Single Packet Authorization Network Shield)
> "spacer" (an SPA gap that must be crossed to access a service)
>
> These are just ideas for words that begin with "SPA".  All input is
> welcome.  Would people like to see a new name?  If so, are there some
> other candidate names that people would like?
>
> Thanks,
>
> --
> Michael Rash | Founder
> http://www.cipherdyne.org/
> Key fingerprint: E2EF 0C8A 5AA9 654C 4763  B50F 37AC E946 7F51 8271
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Fwknop-discuss mailing list
> Fwknop-discuss@...
> https://lists.sourceforge.net/lists/listinfo/fwknop-discuss
>



-- 
Leandro Almeida