Nelson Bolyard wrote:
...
I didn't know they were competition, I thought they both the open source
systems that would keep the Internet open.
I'm curious,
Would you also say that RedHat, Suse and Debian are not in competition?
They are all "open source systems that would keep the Internet open."
I would say they are not in competition in the way you are suggesting.
Debian for example is non-commercial, yet if it does what is needed it
might be used instead of Redhat or SuSE. Which of the above should cause
developers to hate each other and hide improvements to Linux itself?
Will RedHat benefit by making proprietary fixes that nobody else has?
Certainly they'll benefit by solving some problem better than the
others, but they are partially synergistic, it is not entirely win or lose.
Are mozilla and openssl commercial products? If so, I've had a
misconception. If apache uses openssl (and it does), and suddenly
openssl is gone, it harms apache...which harms mozilla. If mozilla is
gone, and only IE is left, I'd bet on openssl having less purpose as MS
makes changes that break its use. For whatever comparison you use that
makes mozilla and openssl "enemies", it's only part of the story.
Apache, openssl, and mozilla are just pieces of something that works
together.
Do they compete? for customers? for revenue? If many of the paying
customers of one switch to another, does this have no effect on either?
If one of them suffers declining revenue because of persistent untrue
rumors that their product cannot do what their competitors' products do,
does that hurt them, and their ability to sustain product development,
or not?
I'm pretty surprised that anyone who makes his living by working on open
source would suggest there is no competition.
I'm surprised the concept of working together is four letter word.
Anyone working in open source should know that it is not so simple.
Competition is not the same as monopolistic leaching. Competition in
some narrow aspect is vastly misleading.
...
The features I mentioned above are all implemented in moz browser products,
accessible via html, javascript, and the GUI. (At least in Mozilla 1.x,
and probably in FireFox too.) They are also available in command line
utilities. Start looking here:
http://www.google.com/search?num=100&q=keygen-tag
Sorry, I did not know what to search for, as mozilla itself does not
present any clues that this was even a possibility. I have no magic to
pop "generateCRMFRequest" into my brain to search for. That's why I ask.
If I must learn javascript or build programs that for example use
"crypto.generateCRMFRequest()", then it is probably better to use
openssl. I'm certainly not going to refer someone I'm trying to help to
a programmer's man page, that'd be a total failure. I'm looking for
tools to do the job, not API's to write something with.
I imagine not all browsers are able to generate keys...up until now I didn't
realize mozilla could. I probably will need to know how to deal with keys for
other browsers later, but for the moment the mozilla way would be sufficient.
I believe that most browsers are able. IINM, Safari offers the same
<keygen> tag as do Mozilla and Netscape. The methods by which a web page
requests the generation of cert signing requests varies from one to another,
but the ability is there in most, if not all.
At this point it looks like it is easier to use openssl. I need one
simple way to do this that I can send to other people who know nothing
about programming or public/private key structure. I can't ask anyone to
create scripts or edit javascript.
_______________________________________________
mozilla-crypto mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-crypto
