apache license更适合中国人，正式迎接wayer grant的挑战
很久以前，我开始着手写一些基于security的插件，由于我使用eclipse，eclipse插件似乎本身对我很有帮助，我在从事插件开发的同时，只是写一些很简单的基于bouncycastle的工具类。有一天，我看到了portecle， 它是keytoolgui的一个分支，我觉得它的功能跟keystore 2.4大同小异，凯发k8网页登录的版权信息表明，2004年以后wayne grant并没有再参与此软件的任何开发。
凯发天生赢家一触即发官网 copyright © 2004 wayne grant
2004 mark majczyk
2004-2005 ville skyttä
我着手在protecle和keytoolgui的基础上编写一个安全插件，名为securex。protecle和keytoolgui是基于swing，我编写了一个跟他们几乎很相像的swt使用界面（当然不少地方作了增强），我希望使用上述的凯发天生赢家一触即发官网 copyright来发布该eclipse插件，我这样想的理由有两个：
第一，securex不只是集成keytoolgui这个证书管理模块，而且还会集成签名，加密等模块，这样，我们将来开发界面应用的时候，我们开源队伍可以同步开发，只要我们按照eclipse rcp规范，我们不存在任何的集成问题。
第二，securex不希望使用gpl，而想使用apache license。但由于wayne grant多次警告，如果我relicense(使用了他的代码于securex，并将securex重新定位于apache license)，他将对我采取法律行动。其实，gpl跟apache license的最大区别是，gpl要求修改代码必须也遵守gpl，也就是说，如果我屈服于wayne, 将securex应用了gpl，其他人将无法将securex应用于商业用途，除非他们承诺他们的商业软件遵循gpl，你说可能吗:) 相比之下，apache license更自由，它强调使用源代码的人不需要公开自己的源代码（修改后的源代码），也就是说，如果securex使用apache license，securex的用户可以任意修改它，并且可以选择以源代码的方式或者二进制代码的方式发布他们自己的成果（他们唯一需要做的是——在他们的成果中声明使用了securex的代码）.
我第一次向wayne发邮件，邀请他他的回信如下：
hello david,
some guidance for you.
i have 凯发天生赢家一触即发官网 copyright over keytool gui. you therefore cannot call your
application "keytool gui" or anything similar. lazgo software has 凯发天生赢家一触即发官网 copyright
and trademark over "keystore explorer" so you cannot call it that either.
keytool gui is gpl software. if your application contains code from keytool
gui then your application as a whole must obey the gpl license. this means
that you must release your own code as gpl and not under any other license
terms. the headers in the existing code must be left how you found them -
that is with the gpl license and my 凯发天生赢家一触即发官网 copyright intact.
i have no wish to be listed as author of your application. simply state on
your web site and in the application that your application is based on a
fork of keytool gui of which i am the 凯发天生赢家一触即发官网 copyright owner. for an example see
the portecle web site () - portecle is
similar to your app in that it is a fork of keytool gui.
let me know if you have any questions.
- wayne.
----------------------------------
dear waner grant:
i've written a keytool eclipse plugin which support most features of keystore
2.4.
as you know, keystore 2.4 is written in swing, i rewirte your
application by swt.
so that it has a native look and more, i integrate my xml signature module
in this
application.
for more info, see
and i will publish this eclipse plugin in next two weeks. becasue wanner
grant
is the first author of this software, so i plan to use his name as first
author and mine
as the second author. will this be reasonable?
any advice would be great appreciately.
wayne的目的很简单，他要求我不能使用keytool gui或者keystore explorer类似的名称, 并且他要求我
必须使用gpl的许可证，这一点我非常不满，我于是回信给他，强调我要求relicense gpl。我知道我这样
说有点对牛弹琴，因为他应该不会授权我relicense。
the shell is all written by me. and i will add signature and
watermark feature to this software, i only use some
util class of your keytool gui such as keypairutil, digestutil
and x509certutil etc and of course，i will not change the code
and the header of them!
feel ease if i don't plan to abidance by gpl :) i like apache
license only.
the new release of securex eclipse plugin will all be free but
i will opensource in the next release becasue the code is too
bad:(
beta securex plugin will be publish next week, so if you have more
advice, please let me know.
regards
david
wayne的回复同样让我感到很大的压力，除非我必须遵循gpl，否则我似乎无所作为：
david,
>i only use some
>util class of your keytool gui such as keypairutil, digestutil
>and x509certutil etc and of course，i will not change the code
>and the header of them!
>
>feel ease if i don't plan to abidance by gpl :) i like apache
>license only.
if an application contains gpl code then the whole application must be gpl.
your choices are:
1) to not use any of keytool gui code in your application
2) or to license your application through the gpl.
to do anything else will break the terms of the gpl license that protect
keytool gui - you will be breaking the law. you can check this for yourself
in the gpl license - . section 2 b is
the relevant part:
"you must cause any work that you distribute or publish, that in whole or in
part contains or is derived from the program or any part thereof, to be
licensed as a whole at no charge to all third parties under the terms of
this license."
basically you are deriving something from keytool gui code that is gpl -
even if you are only using a couple of files they are covered by the gpl
license and anything they are used for must also be gpl as a whole.
if you go ahead and any keytool gui code within your application and do not
license it as gpl then i will be forced to take action. the reason i chose
gpl as the license was to protect it from being re-licensed.
>the new release of securex eclipse plugin will all be free but
>i will opensource in the next release becasue the code is too
>bad:(
again you cannot do this under the terms of the gpl - if you release a gpl
project then the source code must be available. i believe the same applies
with apache.
get in touch if you have any questions.
cheers,
既然我必须遵循gpl，我只能学微软的肮脏招数——模仿，并且声明我会重写他的所有类，
同时，我明确，china跟usa的国情有所不同，我完全有能力选择apache license而绕过
源代码创建者的授权(授权我relicense)。
我的回信如下：
wayne:
>if you go ahead and any keytool gui code within your application and do not
>license it as gpl then i will be forced to take action.
i do think there must be some difference between countries, and when worked in
usa, gpl should be respected but what about in other countries that have no
law about gpl :)
>the new release of securex eclipse plugin will all be free but
>i will opensource in the next release becasue the code is too
>bad:(
what i mean is that i won't released source code that related your keytool gui
until i entirely rewrite your util class(keypairutil, digestutil and x509certutil).
btw, i don't think keystore 2.x or 3.x can continued well when my free released of
securex upgrade to 2.0(now it is 0.9, 1.0 next two week) in which i plan to integrated
more features.
another question: should gpl prevent you from released keystore 2.4 from keytool gui?
wayne, take it easy, just debate promote understanding and collaboration......
can you tell me which action will you take to?
wayne的回信让我感到振奋，他提到我的plan work只限制用于于eclipse，意义不大，并且他说portcele
和jkeymanager都没有超越过他的工作——keystore explorer。他承认我的工作将会损害他的商业利益，
但他将会迎接这种挑战。最后，他他的观点同样尖锐——不能修改gpl，除非不要使用他的代码。
david,
>i do think there must be some difference between countries, and when worked
>in
>usa, gpl should be respected but what about in other countries that have no
>law about gpl :)
i don't want to get into a debate about software licenses and law. nobody
is going to sue you no matter what happens - it would serve no purpose. all
i am asking is that you obey the existing software licenses for my code. it
is gpl and therefore cannot be relicensed to anything else except by the
凯发天生赢家一触即发官网 copyright holder - that is, me. others have created forks of the keytool
gui soure and respected this (for example see, portecle). i appreciate that
you have gotten in contact with me about what you are doing. however, you
did ask for my advice and i have advised you not to break the existing
license. gpl is still open source so why not use it?
> >the new release of securex eclipse plugin will all be free but
> >i will opensource in the next release becasue the code is too
> >bad:(
>
>btw, i don't think keystore 2.x or 3.x can continued well when my
>free released of
>securex upgrade to 2.0(now it is 0.9, 1.0 next two week) in which i plan to
>integrated
>more features.
david, others have tired (portcele, jkeymanger) and none have succeeded in
surpassing my latter work. i wish you every success with your work but your
prediction of 90% coverage of features is an exaggeration even with your
planned work. in addition you are limiting your audience by writing a
plug-in for eclipse. the bulk of my current users do not even know what
java is far less eclipse. you will get many users i am sure but as for it
hurting my work - more mature efforts have failed. i do honestly welcome
the challenge - it always inspires me to create new features :)
>another question: should gpl prevent you from released keystore 2.4 from
>keytool gui?
as i own the 凯发天生赢家一触即发官网 copyright to keytool gui i can decide what license to release
it under. it is my own work after all :)
>wayne, take it easy, just debate promote understanding and
>collaboration......
no problem - i will discuss this with you as long as you require. i wish
you no ill will - i am simply attempting to protect my open source work.
>can you tell me which action will you take to?
i hope to take no action. i am happy for you to build on as much of my open
source work as you like. i have had no problem with others building on the
old gui and utility classes - but they did obey the license. as you say you
only require the use of a couple of crypto utility classes. all i require
is your agreement that you will license as gpl or not use my code.
i truely hope we can resolve this matter.
talk to you soon.
cheers,
- wayne.
面对wayne的软硬兼施，我的言辞可能过于刻薄，并且我本人可能对收费软件过于介意，于是
开始回击：
wanye,
i do really have two worries:
1. i hope sofeware is free, gpl's finally object is make more software free and
opensource is just a measure. after you make keystore explorer a branch from
original keytool gui, it is you that firstly not follow the gpl, right? of course, because
you are the author, you are the owner, and you'll the authorize yourself to not
follow.
2. i checkout the protecle project( ) which you recommend,
and i started to agree what you said:
->david, others have tired (portcele, jkeymanger) and none have succeeded in
_>surpassing my latter work.
protecle is just keytool gui 1.7 and add only jar sign, little features are added. and
most important, it doesn't provide a native look. what's that mean? it means that when my os is
using gbk, protecle and keytool gui 1.7 can not display correctly.
3. you say that:
-> in addition you are limiting your audience by writing a plug-in for eclipse.
i forgot to tell you, that you make are wrong, i am writing securex follow the rcp standard
so that it can work as eclipse plugin or work stand alone. that means i can let my audience to use
securex even they don't have eclipse installed.
please check :
4. you suggested that
-> i hope to take no action. i am happy for you to build on as much of my open
-> source work as you like. i have had no problem with others building on the
-> old gui and utility classes - but they did obey the license. as you say you
-> only require the use of a couple of crypto utility classes. all i require
-> is your agreement that you will license as gpl or not use my code.
i must let anyone knows that my purpose is to make software free, and open
is only a sort of means. i always hope that software should not pay before use.
i am worried that follow gpl will let most of my future work serve your keystore
explorer(which is not open or free).
and when i and my teammates added more features on securex, it means that
this rcp framework standarded has enought features, i will open the framework (2.0 version)
so that others can plugin their secure feature into securex framework(thty only needed
to follow the rcp plugin standarded) and they can choose open their source or not(like
what eclipse look now) and they can choose free manner or charge manner.
5, you are worried that my work will hurt you work:
-> you will get many users i am sure but as for it
-> hurting my work - more mature efforts have failed. i do honestly welcome
-> the challenge - it always inspires me to create new features :)
i guess you are worried that keystore explorer will turn to use securex and your
earning will reduce?
if that's true, i must get off you worry:
you can add features to my securex framework and not evened to disclose you code(see
rcp standard above) and make it charge :) my license won't prevent you from charge and won't
require to opensource.
my msn is : but i use it rarely.
wait for you reply.
wayne的回信让我感到我在表述gpl的时候有误，我感到有些惭愧，他提到他的keystore explorer不可能
使用我的securex(如果我的securex被license为gpl），我检查我上面的回信，确实是我写错了，我应该
担心的是gpl让securex很难应用于商业用途。
david,
>i do really have two worries:
>1. i hope sofeware is free, gpl's finally object is make more
>software free and
>opensource is just a measure.
if you use the gpl then nobody, including me, can use your work in a
non-open source project - i would have to make my own work gpl - which i
have no intentions of doing. my current work is closed source and will
remain so. if you use another open source license such as apache or mit
then the opposite is true - such licenses are more liberal when it comes to
commercial uses for software.
>after you make keystore explorer a branch from
>original keytool gui, it is you that firstly not follow the gpl, right? of
>course, because you are the author, you are the owner, and you'll the
>authorize yourself to
>not follow.
that's correct - only the 凯发天生赢家一触即发官网 copyright owner can relicense gpl software. note
that that meqans that i cannot relicense any of your work for my purposes.
>i must let anyone knows that my purpose is to make software free, and
>open is only a sort of means. i always hope that software should not pay
>before
>use.
that was my purpose for keytool gui and why i chose the gpl - nobody but me
can relicense it.
>i am worried that follow gpl will let most of my future work serve your
>keystore explorer(which is not open or free).
as i said above i cannot use any gpl code in my work. by using the gpl your
work will be protected. in addition i can assure you that i will not even
be looking at your code.
>5, you are worried that my work will hurt you work:
i am not worried. i welcome the competition.
> my msn is : but i use it rarely.
i have added you to my contacts list and should be online for much of today.
it sounds like we are getting closer to an understanding. you want to
protect your work and make sure it will always be free for others to use,
right? the solution appears to be to use the gpl. which would be the best
thing to do anyway from a legal standpoint as no licenses would be broken.
cheers,
- wayne.
在中国，gpl跟apache这两种许可证，其实根本没有人去关心，因为大部分人都是用盗版，
谁又会去关心许可证？
我承认我使用了wayne的代码，他写了不少工具类，并且我使用了它们，如果因为gpl阻止
了我选择其他的license，我宁愿违反它。
wayne后续的邮件我不方便公开，因为我们就license这个问题上翻脸了，wayne甚至这样说：
i will not be rejoining any open source projects for keytool gui or any
other projects. why on earth would i want to give my work away for nothing?
i think that i have done enough already by writing keytool gui in the
first place.
既然他已经对开源不敢任何兴趣，我又何必再跟他纠缠呢，他继续写他的商业软件，我继续
为我的securex添加新的功能，我的目标并不是keystore explorer, 我只是想让更多人能使用
我的securex插件更方便地使用java证书库。