Re: tags on the portable branch?

2019-08-26 Thread Gilles Chehade
On Sun, Aug 25, 2019 at 07:16:23AM +0200, Harald Dunkel wrote:
> Hi Gilles,
> 
> On 8/24/19 9:14 PM, Gilles Chehade wrote:
> > 
> > This is expected.
> > 
> > Version 6.4.x only builds with LibreSSL or OpenSSL 1.0.x
> > 
> 
> do you think it would be possible to set a tag matching support
> for openssl 1.1.1c as well? The version I am using right now now
> is based on 772da22936c8d80f7ad3284ea7e5bdbfdbee2efb, but this
> might be too experimental for production use.
> 

I'm unsure I understand what you want :-/

OpenSSL 1.1.x is only supported in the development branch so you need to
track latest commit in branch 'portable': the commit you're using is one
of the development branch from two weeks ago, if you are happy with that
keep it, it's no less or more experimental than any commit in the branch
since you're already running development code.

I wouldn't know what to tag honestly


-- 
Gilles Chehade @poolpOrg

https://www.poolp.orgpatreon: https://www.patreon.com/gilles



Re: tags on the portable branch?

2019-08-24 Thread Harald Dunkel
Hi Gilles,

On 8/24/19 9:14 PM, Gilles Chehade wrote:
> 
> This is expected.
> 
> Version 6.4.x only builds with LibreSSL or OpenSSL 1.0.x
> 

do you think it would be possible to set a tag matching support
for openssl 1.1.1c as well? The version I am using right now now
is based on 772da22936c8d80f7ad3284ea7e5bdbfdbee2efb, but this
might be too experimental for production use.


Regards
Harri



Re: tags on the portable branch?

2019-08-24 Thread Harald Dunkel
On 8/23/19 9:55 PM, John Cox wrote:
> Hi
> 
> Whilst I know it doesn't help you I just git cloned that URL and the
> tag checkout just worked for me.  What happens if you make another new
> (temporary) repo with clone and try again?
> 
> Regards
> 
> John Cox
> 

Using a new clone, as suggested: The tag "opensmtpd-6.4.2p1" is available,
but it doesn't build on Debian sid (openssl 1.1.1c). Full build.log is
attached.

:
:
gcc -DHAVE_CONFIG_H -I. -I../..  -I../../smtpd -I../../openbsd-compat 
-I../../openbsd-compat/err_h -I../../openbsd-compat/paths_h -I. -I/usr/include  
-DSMTPD_CONFDIR=\"/usr/local/etc\" -DPATH_CHROOT=\"/var/empty\" 
-DPATH_SMTPCTL=\"/usr/local/sbin/smtpctl\"
-DPATH_MAILLOCAL=\"/usr/local/libexec/opensmtpd/mail.local\" 
-DPATH_LIBEXEC=\"/usr/local/libexec/opensmtpd\" -DHAVE_CONFIG_H -DIO_SSL 
-DCA_FILE=\"/etc/ssl/cert.pem\" -g -O2  -fPIC -DPIC -Wall -Wpointer-arith 
-Wuninitialized -Wsign-compare -Wformat-security -Wsizeof-pointer-memaccess
-Wno-pointer-sign -Wno-unused-result -fno-strict-aliasing -fno-builtin-memset 
-D_BSD_SOURCE -D_DEFAULT_SOURCE  -D_GNU_SOURCE -DNEED_EVENT_ASR_RUN -c -o 
../../smtpd/smtpd-ca.o `test -f '../../smtpd/ca.c' || echo './'`../../smtpd/ca.c
../../smtpd/ca.c: In function 'ca_X509_verify':
../../smtpd/ca.c:204:47: error: dereferencing pointer to incomplete type 
'X509_STORE_CTX' {aka 'struct x509_store_ctx_s'}
  204 |*errstr = X509_verify_cert_error_string(xsc->error);
  |   ^~
../../smtpd/ca.c: At top level:
../../smtpd/ca.c:307:1: error: variable 'rsae_method' has initializer but 
incomplete type
  307 | static RSA_METHOD rsae_method = {
  | ^~
../../smtpd/ca.c:308:2: warning: excess elements in struct initializer
  308 |  "RSA privsep engine",
  |  ^~~~
../../smtpd/ca.c:308:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:309:2: warning: excess elements in struct initializer
  309 |  rsae_pub_enc,
  |  ^~~~
../../smtpd/ca.c:309:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:310:2: warning: excess elements in struct initializer
  310 |  rsae_pub_dec,
  |  ^~~~
../../smtpd/ca.c:310:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:311:2: warning: excess elements in struct initializer
  311 |  rsae_priv_enc,
  |  ^
../../smtpd/ca.c:311:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:312:2: warning: excess elements in struct initializer
  312 |  rsae_priv_dec,
  |  ^
../../smtpd/ca.c:312:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:313:2: warning: excess elements in struct initializer
  313 |  rsae_mod_exp,
  |  ^~~~
../../smtpd/ca.c:313:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:314:2: warning: excess elements in struct initializer
  314 |  rsae_bn_mod_exp,
  |  ^~~
../../smtpd/ca.c:314:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:315:2: warning: excess elements in struct initializer
  315 |  rsae_init,
  |  ^
../../smtpd/ca.c:315:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:316:2: warning: excess elements in struct initializer
  316 |  rsae_finish,
  |  ^~~
../../smtpd/ca.c:316:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:317:2: warning: excess elements in struct initializer
  317 |  0,
  |  ^
../../smtpd/ca.c:317:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:318:2: warning: excess elements in struct initializer
  318 |  NULL,
  |  ^~~~
../../smtpd/ca.c:318:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:319:2: warning: excess elements in struct initializer
  319 |  NULL,
  |  ^~~~
../../smtpd/ca.c:319:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:320:2: warning: excess elements in struct initializer
  320 |  NULL,
  |  ^~~~
../../smtpd/ca.c:320:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c:321:2: warning: excess elements in struct initializer
  321 |  rsae_keygen
  |  ^~~
../../smtpd/ca.c:321:2: note: (near initialization for 'rsae_method')
../../smtpd/ca.c: In function 'rsae_pub_enc':
../../smtpd/ca.c:407:21: error: dereferencing pointer to incomplete type 
'RSA_METHOD' {aka 'const struct rsa_meth_st'}
  407 |  return (rsa_default->rsa_pub_enc(flen, from, to, rsa, padding));
  | ^~
../../smtpd/ca.c: In function 'ca_engine_init':
../../smtpd/ca.c:493:38: error: invalid use of incomplete typedef 'RSA_METHOD' 
{aka 'struct rsa_meth_st'}
  493 |   if (!ENGINE_set_name(e, rsae_method.name)) {
  |  ^
../../smtpd/ca.c:511:27: error: 'RSA_FLAG_SIGN_VER' undeclared (first use in 
this function)
  511 |  if (rsa_default->flags & RSA_FLAG_SIGN_VER)
  |   ^
../../smtpd/ca.c:511:27: note: each 

Re: tags on the portable branch?

2019-08-23 Thread John Cox
Hi

>On 8/23/19 1:37 PM, Harald Dunkel wrote:
>> 
>> {hdunkel@dpcl082:OpenSMTPD (portable) 518} git remote -v
>> origin  https://github.com/OpenSMTPD/OpenSMTPD.git (fetch)
>> origin  https://github.com/OpenSMTPD/OpenSMTPD.git (push)
>> {hdunkel@dpcl082:OpenSMTPD (portable) 519} git checkout opensmtpd-6.4.2p1
>> error: pathspec 'opensmtpd-6.4.2p1' did not match any file(s) known to git
>> 
>> ???
>> 
>
>PS: Of course I did a "git fetch --all" first.

Whilst I know it doesn't help you I just git cloned that URL and the
tag checkout just worked for me.  What happens if you make another new
(temporary) repo with clone and try again?

Regards

John Cox



Re: tags on the portable branch?

2019-08-23 Thread Harald Dunkel

On 8/23/19 1:37 PM, Harald Dunkel wrote:


{hdunkel@dpcl082:OpenSMTPD (portable) 518} git remote -v
origin  https://github.com/OpenSMTPD/OpenSMTPD.git (fetch)
origin  https://github.com/OpenSMTPD/OpenSMTPD.git (push)
{hdunkel@dpcl082:OpenSMTPD (portable) 519} git checkout opensmtpd-6.4.2p1
error: pathspec 'opensmtpd-6.4.2p1' did not match any file(s) known to git

???



PS: Of course I did a "git fetch --all" first.



Re: tags on the portable branch?

2019-08-23 Thread Harald Dunkel

On 8/22/19 10:34 AM, Gilles Chehade wrote:

On Thu, Aug 22, 2019 at 10:24:30AM +0200, Harald Dunkel wrote:

Hi folks,

would it be possible to set tags on the portable branch as well?
Something like

portable-6.4.1

would do.

This could help alot for creating some kind of "official" source
package for Debian and Fedora/RedHat.



you mean like this ? :-)

https://github.com/OpenSMTPD/OpenSMTPD/releases/tag/opensmtpd-6.4.2p1



{hdunkel@dpcl082:OpenSMTPD (portable) 518} git remote -v
origin  https://github.com/OpenSMTPD/OpenSMTPD.git (fetch)
origin  https://github.com/OpenSMTPD/OpenSMTPD.git (push)
{hdunkel@dpcl082:OpenSMTPD (portable) 519} git checkout opensmtpd-6.4.2p1
error: pathspec 'opensmtpd-6.4.2p1' did not match any file(s) known to git

???




Re: tags on the portable branch?

2019-08-22 Thread Gilles Chehade
On Thu, Aug 22, 2019 at 10:24:30AM +0200, Harald Dunkel wrote:
> Hi folks,
> 
> would it be possible to set tags on the portable branch as well?
> Something like
> 
>   portable-6.4.1
> 
> would do.
> 
> This could help alot for creating some kind of "official" source
> package for Debian and Fedora/RedHat.
> 

you mean like this ? :-)

https://github.com/OpenSMTPD/OpenSMTPD/releases/tag/opensmtpd-6.4.2p1

-- 
Gilles Chehade @poolpOrg

https://www.poolp.orgpatreon: https://www.patreon.com/gilles



tags on the portable branch?

2019-08-22 Thread Harald Dunkel

Hi folks,

would it be possible to set tags on the portable branch as well?
Something like

portable-6.4.1

would do.

This could help alot for creating some kind of "official" source
package for Debian and Fedora/RedHat.


Thanx in advance
Harri