On Sat, 16 Aug 2008, Nelson B Bolyard wrote: > I don't know how long cURL runs once started
If you decide to for example download a very large file over a slow connection it can very well be running for weeks or more. And curl is just an app, libcurl is used by numerous apps with all sorts of usage patterns of course. > Also, Ideally, cURL would initialize NSS with the user's profile directory. > (That is, I don't think curl typically wants its own set of trusted certs). > So it would be good if it got that profile directory name from the browser > somehow, or called upon PSM to initialize NSS for it. curl is completely independent from browsers, and when installed in systems it usually uses the system-wide CA cert bundle. Of course it has command line options to allow the user to specify what CA bundle to use (or indeed other certs etc). >> 2. Add a function to cURL that cURL users can call to indicate that cURL >> isn't responsible for initializing and shutting down NSS. > > That requires that the invoker of cURL knows that NSS is already initialized > before invoking cURL, right? Yeah, and isn't the problem the same in the other direction too? If curl wouldn't init anything and while running you'll shut down the single other user of NSS. If that other user shuts down NSS, curl gets sad (if I understood things right). -- / daniel.haxx.se _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
