Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

It's also not that much of a problem in practice.. If you are using those API's you are adding new crypto. methods. Doing that after threading has started is not going to give good results with or without locking. Peter From: "Salz, Rich via openssl-dev" To: "openssl-dev@openssl.org"

Re: [openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

* OpenSSL APIs, which makes the following OpenSSL documentation statement invalid (https://www.openssl.org/docs/man1.0.2/crypto/threads.html

[openssl-dev] About multi-thread unsafe for APIs defined in crypto/objects/obj_dat.c

The APIs defined in the file crypto/objects/obj_dat.c share some static global variables defined in the file without locking, which makes the APIs in this file not multi-thread safe even if the locking callbacks are set. In addition, the APIs in this file are also used by the other OpenSSL APIs,

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

* Hubert Kario: > when I mark project as followed I'm getting messages from all issues > and all PRs - likely dozens if not hundred messages a day But isn't that the point? My main concern with Github is that I have no record of my own actions. (Their single-account policy is also a problem for

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

In message <8c351e82-600b-487e-aef3-a3f42cd23...@akamai.com> on Tue, 23 Jan 2018 14:38:14 +, "Salz, Rich via openssl-dev" said: openssl-dev> openssl-dev> ➢ For the lovers of NNTP: openssl-project has been added to news.gmane.org openssl-dev> as gmane.comp.encryption.openssl.projec

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

➢ ah, true, I have those disabled because I use the same account for both my personal and my work projects so no single email address is correct for them At least we figured out the confusion! I have no good answer other than subject line filtering and forwarding, sorry. -- openssl-dev

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

On Tuesday, 23 January 2018 16:13:30 CET Salz, Rich wrote: > ➢ github ones require me to go to the web > UI which is slow > > I am confused by that. When someone posts an issue or comment, I get the > text emailed to me. Not just openssl, but all projects I watch. ah, true, I have those

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

➢ github ones require me to go to the web UI which is slow I am confused by that. When someone posts an issue or comment, I get the text emailed to me. Not just openssl, but all projects I watch. -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/ope

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

On 23.01.2018 15:54, Hubert Kario wrote: > On Tuesday, 23 January 2018 15:36:26 CET Salz, Rich wrote: >> ➢ this feature sends notifications about _all_ conversations happening. >> >> For me, I get the actual comments that are posted. Don’t you? > when I comment in an issue/PR or mark it as fo

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

On Tuesday, 23 January 2018 15:36:26 CET Salz, Rich wrote: > ➢ this feature sends notifications about _all_ conversations happening. > > For me, I get the actual comments that are posted. Don’t you? when I comment in an issue/PR or mark it as followed I'm getting only messages from that iss

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

➢ For the lovers of NNTP: openssl-project has been added to news.gmane.org as gmane.comp.encryption.openssl.project as readonly list. I will always have a fondness for NNTP :) But that reminds me to nudge the other mailing list distributors, and update the website. Thanks! -- opens

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

➢ this feature sends notifications about _all_ conversations happening. For me, I get the actual comments that are posted. Don’t you? On the mailing list, you have to explicitly mark/junk conversation threads in your mail program. You would still have to do that here. I don’t understand

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

On Tuesday, 23 January 2018 15:22:13 CET Salz, Rich wrote: > You should be able to just watch the openssl repo (the eyeball/watch notice > in the upper-right side) that's what I was talking about this feature sends notifications about _all_ conversations happening. > On 1/23/18, 7:00 AM, "Hubert

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

Salz, Rich via open ssl-dev in gmane.comp.encryption.openssl.devel (Fri, 19 Jan 2018 17:34:57 +): >- New mailing list openssl-project for project discussions For the lovers of NNTP: openssl-project has been added to news.gmane.org as gmane.comp.encryption.openssl.project as readonly li

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

You should be able to just watch the openssl repo (the eyeball/watch notice in the upper-right side) On 1/23/18, 7:00 AM, "Hubert Kario" wrote: On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev wrote: > There’s a new blog post at > https://www.openssl.org/blog/

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

Hello, On Tue, Jan 23, 2018 at 3:00 PM, Hubert Kario wrote: > On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev wrote: > > There’s a new blog post at > > https://www.openssl.org/blog/blog/2018/01/18/f2f-london/ > > > We decided to increase our use of GitHub. In addition to a

Re: [openssl-dev] Blog post; changing in email, crypto policy, etc

On Friday, 19 January 2018 18:34:57 CET Salz, Rich via openssl-dev wrote: > There’s a new blog post at > https://www.openssl.org/blog/blog/2018/01/18/f2f-london/ > We decided to increase our use of GitHub. In addition to asking that all bug > reports and enhancement requests be reported as is