From owner-freebsd-bugs@freebsd.org  Wed Dec 13 13:27:03 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 085A9E9DFC8
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 13 Dec 2017 13:27:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id EAA1C70747
 for <freebsd-bugs@FreeBSD.org>; Wed, 13 Dec 2017 13:27:02 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vBDDR2HR046887
 for <freebsd-bugs@FreeBSD.org>; Wed, 13 Dec 2017 13:27:02 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 210537] [patch] [feature request] set MIME type in
 cron-generated e-mails
Date: Wed, 13 Dec 2017 13:27:03 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: mi@ALDAN.algebra.com
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-210537-8-0b7UXIwhXD@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-210537-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-210537-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Dec 2017 13:27:03 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210537

--- Comment #17 from Mikhail T. <mi@ALDAN.algebra.com> ---
(In reply to Eugene Grosbein from comment #16)
> our libc actually has b64_ntop() function for base64 encoding provided wi=
th <resolv.h>

I saw that, but it asks for a buffer to fill, whereas -lcrypto's implementa=
tion
can output directly into a FILE *. I tried using -larchive, but that librar=
y's
base64-code unconditionally wraps the base64-output with `begin-base64 ...
=3D=3D=3D=3D` lines, which confuses e-mail programs
(https://github.com/libarchive/libarchive/issues/976).

> sizeof(char) is 1 by definition of C programming language

Ironically, the very uuencode code, which you referred me to has lines like:

    rv =3D b64_ntop(buf, n, buf2, (sizeof(buf2) / sizeof(buf2[0])));

:-) But, yes, I'll be glad to clean out things like sizeof(char).

--=20
You are receiving this mail because:
You are the assignee for the bug.=