Hi,

FYI, cron is looking for a new maintainer, see #984736, so I guess that
is why there hasn't been any activity yet.

On 2021-06-22 16:52, Wouter Verhelst wrote:
> Whoever wrote that patch should be slapped around the head with a copy
> of RFC3696.

As evident from the header, that patch was taken from cronie, RedHat's
fork of cron-4.1. cronie is much more actively maintained than our own
cron, which is a fork of Vixie cron... from 1993.

> Go read it. Now, please. Understand it. Internalize it. Then update your
> data verification code so that all valid email addresses will be
> accepted.
> 
> But first remove the "save_p" function from the cron implementation. It
> is broken, and the fix may otherwise take too long, I suppose.

The safe_p function and its use of were introduced in upstream, that is
ISC cron 4.1 (from 2004), the basis for most cron daemons (cronie,
OpenBSD's version, and others).

On 2021-07-13 11:15, Georges Khaznadar wrote:
> Hello, as bug #990026 got no update for three weeks, I uploaded a fix to
> our salsa repository, which allows characters like "=" and "/" in e-mail
> addresses.
> 
> I add the patch as an attachment.

I'll upload an NMU.

Best,
Christian

Reply via email to