Re: [openssl-users] Spam and posting controls

2016-04-19 Thread Johann v . Preußen
Mr. Salz: despite mr dukhovni's assertion that spam is not a problem and that people that are concerned about it are a problem, i contend that the seeming laxness of list controls is the core problem and spam is just an indicating vector. to wit: '/List membership is not public/' which may be

Re: [openssl-users] Spam

2016-04-19 Thread Salz, Rich
> the wider problem case is how non-subscribers are given two-way access to the > list that exposes so much subscriber info (name, professional affiliation, > email addr, ...) to whomever. i cannot fathom why the list does not make use > of aliases so that each subscriber can control what they

[openssl-users] THREAD CLOSED: (was: Spam)

2016-04-19 Thread Viktor Dukhovni
Folks, we're here to discuss using OpenSSL, not email list management. Junk mail is a a negligible issue for this list. Discussion of junk mail causes a lot more distraction that the junk mail itself. Therefore, unless the list becomes substantially dominated by junk mail, please keep your though

Re: [openssl-users] Spam

2016-04-19 Thread Johann v . Preußen
i have posted my thoughts on unacceptable list access previously and it sank to the level of a frequent poster denigrating other users since they took exception to his self-professed role of protecting list admins in order "to avoid the list admins following bad advice from people" who might hav

Re: [openssl-users] Spam

2016-04-19 Thread Oliver Niebuhr
Am 20.04.2016 um 01:05 schrieb Scott Neugroschl: > Can the spam filters on the listserv be updated? Got two today in > Spanish and Portuguese for monetary scams. Anyone else getting these? > > > > --- > > Scott Neugroschl | XYPRO Technology Corporation > > 4100 Guardian Street | Suite 100

[openssl-users] Spam

2016-04-19 Thread Scott Neugroschl
Can the spam filters on the listserv be updated? Got two today in Spanish and Portuguese for monetary scams. Anyone else getting these? --- Scott Neugroschl | XYPRO Technology Corporation 4100 Guardian Street | Suite 100 |Simi Valley, CA 93063 | Phone 805 583-2874|Fax 805 583-0124 | -- op

Cielo - Confirme sua participa��o (Premia��o N� 00003881) (21989)

2016-04-19 Thread openssl-users
Title: Mensagem Cielo Nada supera essa máquina! PROGRAMA DEVANTAGENS DA CIELO Na sua próxima compra a partir de 25,00R$ com qualquer cartão de crédito ou débito na máquina da Cielo, você concorre a sorteios semanais de

[openssl-users] Banco do Brasil - Chamado 332016501 (Comunicado) (62759)

2016-04-19 Thread openssl-users
Title: Documento sem título Banco do Brasil Comunicado Prezado(a) Cliente, O Banco do Brasil vem mudando para melhorar sua vida, e está disponibi

[openssl-users] OpenSSL version 1.1.0 pre release 5 published

2016-04-19 Thread OpenSSL
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenSSL version 1.1.0 pre release 5 (beta) === OpenSSL - The Open Source toolkit for SSL/TLS http://www.openssl.org/ OpenSSL 1.1.0 is currently in beta. OpenSSL 1.1.0 pre release 5 has now be

Re: [openssl-users] FIPS compile issue with Perl on Windows

2016-04-19 Thread Steve Marquess
On 04/19/2016 10:43 AM, Jakob Bohm wrote: > On 19/04/2016 16:31, Steve Marquess wrote: >> On 04/19/2016 09:16 AM, Jakob Bohm wrote: >>> On 19/04/2016 13:44, Leaky wrote: Thanks, but I am still scratching my head as to if that is even possible on Windows, which would mean you can't ac

Re: [openssl-users] FIPS compile issue with Perl on Windows

2016-04-19 Thread Jakob Bohm
On 19/04/2016 16:31, Steve Marquess wrote: On 04/19/2016 09:16 AM, Jakob Bohm wrote: On 19/04/2016 13:44, Leaky wrote: Thanks, but I am still scratching my head as to if that is even possible on Windows, which would mean you can't actually compile the FIPS canister on Windows and meet the secur

Re: [openssl-users] FIPS compile issue with Perl on Windows

2016-04-19 Thread Steve Marquess
On 04/19/2016 09:16 AM, Jakob Bohm wrote: > On 19/04/2016 13:44, Leaky wrote: >>> The Security Policy is quite specific on the requirements, which make no >>> allowance for the common sense (to a software engineer) fact that there >>> are equivalent multiple ways to accomplish each step (such as un

Re: [openssl-users] FIPS compile issue with Perl on Windows

2016-04-19 Thread Jakob Bohm
On 19/04/2016 13:44, Leaky wrote: The Security Policy is quite specific on the requirements, which make no allowance for the common sense (to a software engineer) fact that there are equivalent multiple ways to accomplish each step (such as unzipping the tarball). You are also specifically requir

Re: [openssl-users] FIPS compile issue with Perl on Windows

2016-04-19 Thread Leaky
> The Security Policy is quite specific on the requirements, which make no > allowance for the common sense (to a software engineer) fact that there > are equivalent multiple ways to accomplish each step (such as unzipping > the tarball). You are also specifically required to begin with the > offic

Re: [openssl-users] FIPS compile issue with Perl on Windows

2016-04-19 Thread Steve Marquess
On 04/18/2016 08:25 PM, Jakob Bohm wrote: > On 19/04/2016 01:51, Steve Marquess wrote: >> On 04/18/2016 04:05 PM, Leaky wrote: > plus you're constrained by the > requirements of the Security Policy to build the module with precisely > the commands: > > gunzip -c openssl-fips-2