From nobody Sun Jul 30 18:32:48 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RDVPF6FBjz4pJ18 for ; Sun, 30 Jul 2023 18:33:04 +0000 (UTC) (envelope-from ksrdhrbsd@gmail.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RDVNt5qNpz3Lbv for ; Sun, 30 Jul 2023 18:33:02 +0000 (UTC) (envelope-from ksrdhrbsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=IEP2OrbB; spf=pass (mx1.freebsd.org: domain of ksrdhrbsd@gmail.com designates 2a00:1450:4864:20::632 as permitted sender) smtp.mailfrom=ksrdhrbsd@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-99bcc0adab4so601038166b.2 for ; Sun, 30 Jul 2023 11:33:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690741979; x=1691346779; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pAEHQ39EjReyDEUpEj8ARhT9+OPE+Uam28mWOHhAbzw=; b=IEP2OrbBZ8zF0ysXwAZAWW0qxn4rrToaP0ftMg9tq/oZYam6o41/UNMwT9++TTLGkr iOBSpoAYc7cwPNJ9uGfVXEEklWHVi10qS/E/rBlazvLUascQI+uvnovTKzTd2gM3/wND A83Umy3Vw9imClbGPCZLhvN7Mvwe2675v5lccJwp2C8iC9YSfnN+ZtNT0gvMhLHJjT2m bmFNtYlL1g1Kkl8+VcYSEm5HdvQuTaBBOOqYlv5CMzDIs97Fgs+uzreBGmBAr8DvSKfd MOrBWvSsoAs8qI4iNeehWQ5cfy49SjDUWf7o30avP0SDn5H09yxvtcS2R3u9NhKbNkWY 1+jQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690741979; x=1691346779; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pAEHQ39EjReyDEUpEj8ARhT9+OPE+Uam28mWOHhAbzw=; b=WkE5ezEwHfr6osySq+QWE98lPyDanU9mNCGGH/b4K5Ld7lWsa7t3eF2CaLznN4co+U l47q5eZ6VHhxVgb8GyM1TbefHoxpNdlPTwtZ+n0UEuigyKSIL/rmr84jNcfl5hhunwci MLtuJiIhBCimb9trUuZ8/KfgJ8qFXhakB8mct7VhC//VEErXcHrBECi1qeVEG8pA8XxA PD0QQatONgudAADJfZyQCqeGlYS5Y17rixMgsVNM0ynql9HgWH+/MixPZXulLLso7vo3 Ci2NSS6P1sGczcn7rXiwjPvHemth3Mn8vAjn4rNvWUj/gF4yQ3WiiGU8Hxm47QXoUE9K d1yg== X-Gm-Message-State: ABy/qLb6OK4YwUZQwO3HwFMNKi90aRhKzQzV9roiJrNsV5p0f2VXgtyf 4PgUzKp106jEXAKrnZoAw8+pPIaeOO5FC8n+EQ== X-Google-Smtp-Source: APBJJlGvZWQbPRW/6mC+dYHZhuzE1i/oIHyKeVi4w+dKEvT/Iqplg1ZBPCOPSRU7bQ/h25/ojpZAHrz6iGkn76nAieU= X-Received: by 2002:a17:906:114:b0:973:ff8d:2a46 with SMTP id 20-20020a170906011400b00973ff8d2a46mr4784273eje.3.1690741979209; Sun, 30 Jul 2023 11:32:59 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <5EBDAA39-3512-4AA9-A4E2-72741FAE414C@iitbombay.org> In-Reply-To: <5EBDAA39-3512-4AA9-A4E2-72741FAE414C@iitbombay.org> From: k sridhar Date: Sun, 30 Jul 2023 14:32:48 -0400 Message-ID: Subject: Re: Contributing to one of the projects in the Ideas page To: Bakul Shah Cc: imp@bsdimp.com, FreeBSD Hackers Content-Type: multipart/alternative; boundary="00000000000013e3a50601b88b65" X-Spamd-Result: default: False [-3.82 / 15.00]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_LONG(-0.93)[-0.929]; NEURAL_HAM_MEDIUM(-0.90)[-0.899]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::632:from]; RCVD_TLS_LAST(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4RDVNt5qNpz3Lbv X-Spamd-Bar: --- --00000000000013e3a50601b88b65 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks a lot for your tips and pointers. I am setting up my BSD machines and will start once that is complete. Thanks. On Sun, Jul 23, 2023 at 10:44=E2=80=AFPM Bakul Shah w= rote: > Note that NetBSD seems to have the same version as FreeBSD's > ports/sysutils/isc-cron (modulo replacing sprintf, strcpy, strcat etc wit= h > safer versions). > > Paul seems to be maintaining the original at > https://github.com/vixie/cron.git with a few fixes this year. Though his > CRON_VERSION says V4.999 compared to ports/isc-cron that has V5.0! I woul= d > suggest keeping in sync with Paul's version at github and may be feeding > back improvements. > > On Jul 23, 2023, at 7:06 PM, k sridhar wrote: > > Sure, I will start by reviewing what OpenBSD and NetBSD have done. > > Thanks a lot. > > On Sun, Jul 23, 2023 at 10:04=E2=80=AFPM Warner Losh wro= te: > >> >> >> On Sun, Jul 23, 2023, 7:59 PM k sridhar wrote: >> >>> >>> Hello, >>> >>> I was browsing the Ideas page for ways to contribute to BSD. >>> I came across this (which does not have any contact, I think). >>> >>> If it is still open, I wanted to check if I could try to do this. >>> >>> Briefly - I am in IT, and have been using UNIX since grad school in the >>> early 90s (Solaris, briefly Ultrix/Aix and then different Linuxes >>> and MacOS). C/C++/Java programming, scripting, installs, etc... and var= ious >>> other stuff. >>> >>> I want to give it a shot if you all think that is ok. >>> >> >> Nobody is working on this. Might be best to see what openbsd and netbsd >> have done first and start from there. It will be the first question peop= le >> ask when you start the review process. I think yhey have some fixes and= a >> newer vixie cron import, but I'm not sure. >> >> Happy coding >> >> Warner >> >> Thanks a lot >>> k.sridhar (U.S resident in Virginia) >>> *Improve cron(8) and atrun(8)* >>> >>> *Currently, cron(8) and atrun(8) are outdated in their implementation. >>> Here are some directions for improvement:* >>> >>> - *Update cron(8) to ISC cron with security fixes from OpenBSD.* >>> - *Integrate the atrun(8) functionality into cron(8), as it was done >>> in NetBSD.* >>> >>> >>> *Requirements* >>> >>> - *Strong knowledge of the C language and Unix API.* >>> >>> > --00000000000013e3a50601b88b65 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks a lot for your tips and pointers.
I am setting = up my BSD machines and will start once that is complete.
Thanks.<= /div>

On Sun, Jul 23, 2023 at 10:44=E2=80=AFPM Bakul Shah <bakul@iitbombay.org> wrote:
Note that NetBSD see= ms to have the same version as FreeBSD's ports/sysutils/isc-cron (modul= o replacing sprintf, strcpy, strcat etc with safer versions).

Paul seems to be maintaining the original at https://github.com/vixie/cron.git with a few fixes this year. Though his CRON_VERSION says V4.999 compared= to ports/isc-cron that has V5.0! I would suggest keeping in sync with Paul= 's version at github and may be feeding back improvements.

=

Sure, I will start by review= ing what OpenBSD and NetBSD have done.

Thanks a lot.

On Sun, Jul 23, 2023 at 10:04=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:
=


=
On Sun, Jul 23, 2023, 7:59 PM k sridh= ar <ksrdhrbsd@g= mail.com> wrote:

Hello,

I was browsing the Ideas page= for ways to contribute to BSD.
I came across this (which does no= t have any contact, I think).

If it is still open,= I wanted to check if I could try to do this.

= Briefly - I am in IT, and have been using UNIX since grad school in the ear= ly 90s (Solaris, briefly Ultrix/Aix and then different Linuxes and=C2=A0Mac= OS). C/C++/Java programming, scripting, installs, etc... and various other = stuff.=C2=A0

I want to give it a shot if you all thi= nk that is ok.
=

Nobody is working on this. Mi= ght be best to see what openbsd and=C2=A0 netbsd have done first and start = from there. It will be the first question people ask when you start the rev= iew=C2=A0process.=C2=A0 I think yhey have some fixes and a newer vixie cron= import, but I'm=C2=A0not sure.=C2=A0

=
Happy coding

Warner

Thanks a lot
k.sri= dhar (U.S resident in Virginia)

Improve cr= on(8) and atrun(8)

Currently, cron(8) and atrun(= 8) are outdated in their implementation. Here are some directions for impro= vement:

  • Update cron(8) to ISC cron with security fixes = from OpenBSD.=
  • Integrate the atrun(8) funct= ionality into cron(8), as it was done in NetBSD.

Requirement= s
  • Strong knowledge of the C language and Un= ix API.

--00000000000013e3a50601b88b65--