[lsb-discuss] [Fwd: NSS public functions.]

Submitted by Ron Hale-Evans on Mon, 06/23/2008 - 03:57.

On 6/9/08, Jeff Licquia <jeff@licquia.org> wrote:

<snip>
I would initially propose the strawman list of APIs be included in LSB4 would include.

This are all the functions which we documented in our ssl reference except the following:

NSS_SetDomesticPolicy
NSS_SetExportPolicy
SSL_Enable
SSL_EnableCipher
SSL_EnableDefault
SSL_RedoHandshake
SSL_SetPolicy

The above are deprecated, and no longer needed (either their functionality was replaced by a newer function, or their functionality is no longer needed).

NSS_Init

NSS_InitReadWrite

NSS_NoDBInit

NSS_Shutdown

<snip; more APIs followed>

Jeff, I'm having trouble parsing the text above. I suspect a copy/paste error between the first and second paragraphs, if not some other error between my ears. :-)

Could you please clarify what the strawman list will consist of again? An explicit list of APIs would be very helpful.

Thanks,

Ron Hale-Evans

[lsb-discuss] [Fwd: NSS public functions.]
Submitted by Robert Relyea on Mon, 06/23/2008 - 16:45.

Ron Hale-Evans wrote:
> On 6/9/08, *Jeff Licquia* >
> wrote:
>
>
> I would initially propose the strawman list of APIs be included in
> LSB4 would include.
>
> This are all the functions which we documented in our ssl
> reference except the following:
>
> NSS_SetDomesticPolicy
>
> NSS_SetExportPolicy
>
> SSL_Enable
>
> SSL_EnableCipher
>
> SSL_EnableDefault
>
> SSL_RedoHandshake
>
> SSL_SetPolicy
>
>
> The above are deprecated, and no longer needed (either their
> functionality was replaced by a newer function, or their
> functionality is no longer needed).
>
> NSS_Init
>
>
> NSS_InitReadWrite
>
>
> NSS_NoDBInit
>
>
> NSS_Shutdown
>
>
>
>
>
>
> Jeff, I'm having trouble parsing the text above. I suspect a
> copy/paste error between the first and second paragraphs, if not some
> other error between my ears. :-)
Sorry I wasn't clear...

The explicit list starts at NSS_Init.

The links above that point to explicit documentation I used to create
the lists. That documentation includes some deprecated functions, so I
pointed those out. They probably should not be part of the API.

I was hoping to get some comments from the rest of the NSS team on
whether or not this list is appropriate, particularly whether or not the
deprecated list of functions are correct.

bob

[lsb-discuss] [Fwd: NSS public functions.]
Submitted by Ron Hale-Evans on Mon, 06/23/2008 - 16:45.

On Mon, Jun 23, 2008 at 9:38 AM, Robert Relyea wrote:
> Ron Hale-Evans wrote:
>>
>> On 6/9/08, *Jeff Licquia* >
>> wrote:
>>
>>
>> I would initially propose the strawman list of APIs be included in
>> LSB4 would include.
>>
>> This are all the functions which we documented in our ssl
>> reference except the following:
>>
>> NSS_SetDomesticPolicy
>>
>>
>> NSS_SetExportPolicy
>>
>>
>> SSL_Enable
>>
>>
>> SSL_EnableCipher
>>
>>
>> SSL_EnableDefault
>>
>>
>> SSL_RedoHandshake
>>
>>
>> SSL_SetPolicy
>>
>>
>>
>> The above are deprecated, and no longer needed (either their
>> functionality was replaced by a newer function, or their
>> functionality is no longer needed).
>>
>> NSS_Init
>>
>>
>>
>> NSS_InitReadWrite
>>
>>
>>
>> NSS_NoDBInit
>>
>>
>>
>> NSS_Shutdown
>>
>>
>>
>>
>>
>>
>>
>> Jeff, I'm having trouble parsing the text above. I suspect a copy/paste
>> error between the first and second paragraphs, if not some other error
>> between my ears. :-)
>
> Sorry I wasn't clear...
>
> The explicit list starts at NSS_Init.
>
> The links above that point to explicit documentation I used to create the
> lists. That documentation includes some deprecated functions, so I pointed
> those out. They probably should not be part of the API.
>
> I was hoping to get some comments from the rest of the NSS team on whether
> or not this list is appropriate, particularly whether or not the deprecated
> list of functions are correct.

Thanks, Bob. That's a huge help. I'll pore over this shortly.

Ron

--
Ron Hale-Evans ... rwhe@ludism.org ... http://ron.ludism.org/ ... (206) 201-1768
Mind Performance Hacks book: http://www.oreilly.com/catalog/mindperfhks/
Center for Ludic Synergy: http://www.ludism.org/
(revilous life proving aye the death of ronaldses when winpower wine has
bucked the kick on poor won man)

[Fwd: NSS public functions.]
Submitted by Ron Hale-Evans on Thu, 07/03/2008 - 01:45.

OK, you can find the list of NSS public functions on the LF Wiki here:

http://www.linuxfoundation.org/en/NssPublicFunctions

Feel free to edit it and add any information you deem necessary.

Thanks,

Ron

[Fwd: NSS public functions.]
Submitted by Ron Hale-Evans on Wed, 07/09/2008 - 22:45.

Bob--

As far as I can tell, the NSS docs on the Mozilla Wiki use the
Creative Commons Attribution-Sharealike license, whereas the LSB spec
documentation uses the GNU Free Documentation License. It seems to be
the Free Software Foundation's opinion that these two licenses are
incompatible.

*****

http://www.gnu.org/philosophy/license-list.html

Creative Commons Attribution-Sharealike 2.0 license (a.k.a. CC-BY-SA)

This is a copyleft free license that is good for artistic and
entertainment works, and educational works. Please don't use it for
software or documentation, since it is incompatible with the GNU GPL
and with the GNU FDL.

*****

It will be a lot easier to build on the NSS documentation for the LSB
spec if the licenses are compatible. Is the NSS documentation
available under any other licenses? If not, can it be made so?

Thanks,

Ron Hale-Evans

On Wed, Jul 2, 2008 at 6:37 PM, Ron Hale-Evans wrote:
> OK, you can find the list of NSS public functions on the LF Wiki here:
>
> http://www.linuxfoundation.org/en/NssPublicFunctions
>
> Feel free to edit it and add any information you deem necessary.

[Fwd: NSS public functions.]
Submitted by Ron Hale-Evans on Fri, 07/11/2008 - 04:45.

On Wed, Jul 9, 2008 at 3:32 PM, Ron Hale-Evans wrote:
> Bob--
>
> As far as I can tell, the NSS docs on the Mozilla Wiki use the
> Creative Commons Attribution-Sharealike license, whereas the LSB spec
> documentation uses the GNU Free Documentation License. It seems to be
> the Free Software Foundation's opinion that these two licenses are
> incompatible.
> [snip]
> It will be a lot easier to build on the NSS documentation for the LSB
> spec if the licenses are compatible. Is the NSS documentation
> available under any other licenses? If not, can it be made so?

Never mind; it turns out we can mostly refer to the NSS documentation
rather than rewriting it, providing a delta where necessary. This
wouldn't necessitate compatible licenses.

Thanks,

Ron

[Fwd: NSS public functions.]
Submitted by LSB List on Fri, 07/11/2008 - 13:00.

Posted to the lsb-discuss mailing list by: Nelson B Bolyard

Ron

Bob Relyea is now on vacation until about the end of the month.

Regards,
/Nelson

[lsb-discuss] [Fwd: NSS public functions.]
Submitted by Ron Hale-Evans on Mon, 06/23/2008 - 04:45.

On Sun, Jun 22, 2008 at 8:54 PM, Ron Hale-Evans wrote:
> On 6/9/08, Jeff Licquia wrote:
>>
>>
>> I would initially propose the strawman list of APIs be included in LSB4
>> would include.
>>
>> This are all the functions which we documented in our ssl reference except
>> the following:
>>
>> NSS_SetDomesticPolicy
>> NSS_SetExportPolicy
>> SSL_Enable
>> SSL_EnableCipher
>> SSL_EnableDefault
>> SSL_RedoHandshake
>> SSL_SetPolicy
>>
>> The above are deprecated, and no longer needed (either their functionality
>> was replaced by a newer function, or their functionality is no longer
>> needed).
>>
>> NSS_Init
>> NSS_InitReadWrite
>> NSS_NoDBInit
>> NSS_Shutdown
>
>
>
> Jeff, I'm having trouble parsing the text above. I suspect a copy/paste
> error between the first and second paragraphs, if not some other error
> between my ears. :-)
>
> Could you please clarify what the strawman list will consist of again? An
> explicit list of APIs would be very helpful.

Jeff, after a couple more readings, it seems that everything after
"So, here it is." in your email was actually written by the Mozilla
folks. Is that correct? That would clear up some of my confusion right
away.

If this is the case, whom should I write at Mozilla to get a more
explicit list of their APIs? Robert Relyea?

Thanks,

Ron

[lsb-discuss] [Fwd: NSS public functions.]
Submitted by Wan-Teh Chang on Mon, 06/23/2008 - 15:15.

On Sun, Jun 22, 2008 at 9:31 PM, Ron Hale-Evans wrote:
>
> If this is the case, whom should I write at Mozilla to get a more
> explicit list of their APIs? Robert Relyea?

Yes, please use Robert Relyea as the NSS point of contact.
If he's on vacation now and you need answers right away,
feel free to write to me and Nelson Bolyard.

Wan-Teh

[lsb-discuss] [Fwd: NSS public functions.]
Submitted by Jeff Licquia on Mon, 06/23/2008 - 14:30.

Ron Hale-Evans wrote:
> Jeff, after a couple more readings, it seems that everything after
> "So, here it is." in your email was actually written by the Mozilla
> folks. Is that correct? That would clear up some of my confusion right
> away.

Yes, that's right. It was forwarded to me, because the first attempt at
posting the message seemed to go awry.

> If this is the case, whom should I write at Mozilla to get a more
> explicit list of their APIs? Robert Relyea?

I'd say that would be a good start.

[lsb-discuss] [Fwd: NSS public functions.]

Active forum topics