smtpd smtp_proceed_wiz function

src/usr.sbin/smtpd/smtp_session.c contains the following code: 1892 static void 1893 smtp_proceed_wiz(struct smtp_session *s, const char *args) 1894 { 1895 smtp_reply(s, "500 %s %s: this feature is not supported yet ;-)", 1896 esc_code(ESC_STATUS_PERMFAIL,

Re: smtpd smtp_proceed_wiz function

On 2021/11/08 14:52, Crystal Kolipe wrote: > src/usr.sbin/smtpd/smtp_session.c contains the following code: > > 1892static void > 1893smtp_proceed_wiz(struct smtp_session *s, const char *args) > 1894{ > 1895smtp_reply(s, "500 %s %s: this feature is

Re: sppp(4)/pppoe(4) - DNS configuration via resolvd(8)

On Mon, Nov 08, 2021 at 11:52:52AM +0100, Bjorn Ketelaars wrote: > Diff below does two things: > 1. add PPP IPCP extensions for name server addresses (rfc1877) to >sppp(4) > 2. propose negotiated name servers from sppp(4) to resolvd(8) using >RTM_PROPOSAL_STATIC route messages. > > With

Re: cert.pem sync

ok > On Jun 10, 2021, at 05:05, Theo Buehler wrote: > > On Thu, Jun 10, 2021 at 11:39:46AM +0100, Stuart Henderson wrote: >> I was just reminded of the Apple cert problem with GeoTrust Global CA >> and checked and they're using better intermediates for api.push.apple.com >> now. OK to sync up

Re: smtpd smtp_proceed_wiz function

On Mon, Nov 08, 2021 at 06:13:14PM +, Stuart Henderson wrote: > On 2021/11/08 14:52, Crystal Kolipe wrote: > > I'm not aware of a 'wiz' command in any SMTP related RFC. > This will become clear if you look into sendmail history :) Got it :). I assume that this won't be implemented in OpenBSD

Re: smtpd smtp_proceed_wiz function

Crystal Kolipe [kolip...@exoticsilicon.com] wrote: > On Mon, Nov 08, 2021 at 06:13:14PM +, Stuart Henderson wrote: > > On 2021/11/08 14:52, Crystal Kolipe wrote: > > > I'm not aware of a 'wiz' command in any SMTP related RFC. > > This will become clear if you look into sendmail history :) > >

Re: sppp(4)/pppoe(4) - DNS configuration via resolvd(8)

On 2021/11/08 15:50, Klemens Nanni wrote: > With this diff pppoe(4) sends two nameservers and thus wins, but that is > expected and setups such as mine must either > - disable resolvd > - enable resolvd but also enable unwind > (unwind also learns DNS proposals but always wins in resolv.conf) >

Cirque Corporation USB GlidePoint

I have this usb device but running OpenBSD did not recognize it. Trying to troubleshoot I saw that the device has a device descriptor of 0x00 instead of the expected 0x01 as the following debug message shows: usbd_new_device: adding unit addr=5, rev=110, class=0, subclass=0, protocol=0,

Re: regress/rpki-client: test openssl in regress target only

On Mon, Nov 08, 2021 at 10:47:04PM +, Klemens Nanni wrote: > On Mon, Nov 08, 2021 at 12:59:51AM +0100, Theo Buehler wrote: > > > rpki-client seems to be the one-off under regress/ in this regard. > > > > Maybe. I wish I had a better idea than this > > There is: pull the test into the proper

Re: add 802.11n 40MHz support to iwn(4)

On Nov 01 12:56:26, s...@stsp.name wrote: > This patch adds 802.11n 40MHz support to the iwn(4) driver. > > This driver supports many different devices. Please try to be precise > about which device you have tested so I can maintain a record of our > test coverage. This is current/amd64 on a

Re: regress/rpki-client: test openssl in regress target only

On Mon, Nov 08, 2021 at 12:59:51AM +0100, Theo Buehler wrote: > > rpki-client seems to be the one-off under regress/ in this regard. > > Maybe. I wish I had a better idea than this There is: pull the test into the proper Makefile as done in regress/sys/net/inetinet/pmtu/Makefile and not

Re: ixl(4): add rx/tx checksum offloading

On Tue, Oct 26, 2021 at 02:52:10PM +0200, Jan Klemkow wrote: > On Tue, Oct 26, 2021 at 05:17:55PM +1000, Jonathan Matthew wrote: > > First of all, thanks for looking at this, I forgot we hadn't done offloads > > for ixl(4) yet. > > You're welcome. > > > In the case of ixl(4), the driver has to

make iwx(4) use per-queue Tx timers

iwx(4) has an issue which occurs very occasionally for me (every couple of days or sometimes even weeks) where ssh(1) fails to connect until the interface is reset with ifconfig down/up. The initial protocol exchange with the SSH server succeeds, but as soon as the client enters interactive state

Re: ldap search vs ldapsearch

Moving to tech@ On Sat, 2021-11-06 at 03:11 -0400, Allan Streib wrote: > On OpenBSD 7.0-release, comparing the output of OpenLDAP's > ldapsearch(1) to ldap(1) search, the ldap(1) search output is > missing the last attribute of each directory entry. > > e.g. from a directory I am working on at

sync iwm(4) resume code path with iwx(4)

The resume code path of iwx(4) was improved during the k2k21 hackathon. This patch merges the corresponding changes to iwm(4), such that iwm(4) resumes directly in DVACT_WAKEUP instead of using the init task. Tested by me on an 8265 device. ok? diff 02c3ac519701a4fe198f8ee3de592b34a39ee6f7

sppp(4)/pppoe(4) - DNS configuration via resolvd(8)

Diff below does two things: 1. add PPP IPCP extensions for name server addresses (rfc1877) to sppp(4) 2. propose negotiated name servers from sppp(4) to resolvd(8) using RTM_PROPOSAL_STATIC route messages. With this I'm able to use DNS servers as provided by my ISP who uses PPPoE.

iwm/iwx: update last_rx timestamp

The last_rx timestamp which controls timeout of an Rx block ack session is not updated when a frame is received. This can result in the session timing out too early. Not a huge deal because the AP will simply request a new session when it has more data to send. And many APs do not even enable

Re: sppp(4)/pppoe(4) - DNS configuration via resolvd(8)

On Mon, Nov 08, 2021 at 11:52:52AM +0100, Bjorn Ketelaars wrote: > Diff below does two things: > 1. add PPP IPCP extensions for name server addresses (rfc1877) to >sppp(4) You could add that RFC to sppp(4)'s STANDARDS section. > 2. propose negotiated name servers from sppp(4) to resolvd(8)