Re: happy birthday theo
it is exciting because we all love you and respect you. also, it "is" a release day; the 54th iteration of theo de raadt. ;) cheers. -mayuresh > From owner-misc+m193...@openbsd.org Fri May 20 03:38:08 2022 > From: "Theo de Raadt" > To: stati...@cryptolab.net > cc: misc@openbsd.org > Subject: Re: happy birthday theo > Comments: In-reply-to stati...@cryptolab.net >message dated "Thu, 19 May 2022 17:14:41 +0200." > > Thank you all, but I don't understand why this is so exciting. > > I mean, it isn't a release day! > > > > stati...@cryptolab.net wrote: > > > I will join in as well: Happy birthday, Theo! > > And thank you for all the good work on this sublime OS... > > > > Cheers, > > Oddmund > > > > > > Le 19/05/2022 à 16:33, Amit Kulkarni a écrit : > > > Happy Birthday to Theo! > > > On Thu, May 19, 2022 at 4:46 AM Brodey Dover > > > wrote: > > >> > > >> Happy Birthday Theo! > > >> > > >> On Thu, 19 May 2022 at 02:51, Mayuresh Kathe wrote: > > >> > > >>> here's wishing theo deraadt a very happy birthday. > > >>> wish you many more years of producing great software and being > > >>> cantankerous. :p > > >>> have a great day today and an amazing year ahead. > > >>> -mayuresh > > >>> > > >>> > > > > > > >
Re: happy birthday theo
Well, you might say it is the anniversary of your personal release day, so to speak... Happy Birthday! -Hysun On Thu, May 19, 2022 at 10:30 PM Theo de Raadt wrote: > Thank you all, but I don't understand why this is so exciting. > > I mean, it isn't a release day! > > > > stati...@cryptolab.net wrote: > > > I will join in as well: Happy birthday, Theo! > > And thank you for all the good work on this sublime OS... > > > > Cheers, > > Oddmund > > > > > > Le 19/05/2022 à 16:33, Amit Kulkarni a écrit : > > > Happy Birthday to Theo! > > > On Thu, May 19, 2022 at 4:46 AM Brodey Dover > > > wrote: > > >> > > >> Happy Birthday Theo! > > >> > > >> On Thu, 19 May 2022 at 02:51, Mayuresh Kathe > wrote: > > >> > > >>> here's wishing theo deraadt a very happy birthday. > > >>> wish you many more years of producing great software and being > > >>> cantankerous. :p > > >>> have a great day today and an amazing year ahead. > > >>> -mayuresh > > >>> > > >>> > > > > > > >
Re: happy birthday theo
On 2022-05-19 23:28, Theo de Raadt wrote: Thank you all, but I don't understand why this is so exciting. I mean, it isn't a release day! Well it sort of is . . . it's the release day of Theo version 1.0! - J
mutt fetch-mail ssl error
I have been unable to fetch mail with mutt on this host using either the currently installed snapshot and mutt package, or the snapshot and mutt package that had been installed 2-3 days previously. I have been able to send mail using mutt in conjuction with msmtp from this host. mutt's error-history command displays Reading /home/aer/var/mail/inbox... Reading /home/aer/var/mail/inbox... 0 Looking up pop3.xtra.co.nz... Connecting to pop3.xtra.co.nz... SSL failed: error:14007086:SSL routines:CONNECT_CR_CERT:certificate +verify failed Error connecting to server: pop3.xtra.co.nz The below snapshot was installed yesterday and all packages were updated immediately afterwards such that mutt's version is now 2.2.5. kern.version=OpenBSD 7.1-current (GENERIC.MP) #533: Thu May 19 07:38:57 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP Another amd64 host that I have with OpenBSD 7.1 (GENERIC.MP) #454 and mutt 2.2.2 installed, fetches and sends mail without error using the same set of mutt configuration files. Am I able to rectify the above error, and if so how? Regards -- aer
Re: happy birthday theo
Thank you all, but I don't understand why this is so exciting. I mean, it isn't a release day! stati...@cryptolab.net wrote: > I will join in as well: Happy birthday, Theo! > And thank you for all the good work on this sublime OS... > > Cheers, > Oddmund > > > Le 19/05/2022 à 16:33, Amit Kulkarni a écrit : > > Happy Birthday to Theo! > > On Thu, May 19, 2022 at 4:46 AM Brodey Dover > > wrote: > >> > >> Happy Birthday Theo! > >> > >> On Thu, 19 May 2022 at 02:51, Mayuresh Kathe wrote: > >> > >>> here's wishing theo deraadt a very happy birthday. > >>> wish you many more years of producing great software and being > >>> cantankerous. :p > >>> have a great day today and an amazing year ahead. > >>> -mayuresh > >>> > >>> > > >
Re: happy birthday theo
happy birthday On Thu, May 19, 2022 at 11:34 AM Gabriel Busch de Brito < gbuschbr...@gmail.com> wrote: > Happy birthday! > > >On 19.05.2022 09:33, Amit Kulkarni wrote: > > Happy Birthday to Theo! > > > > On Thu, May 19, 2022 at 4:46 AM Brodey Dover wrote: > > > > > > Happy Birthday Theo! > > > > > > On Thu, 19 May 2022 at 02:51, Mayuresh Kathe wrote: > > > > > > > here's wishing theo deraadt a very happy birthday. > > > > wish you many more years of producing great software and being > > > > cantankerous. :p > > > > have a great day today and an amazing year ahead. > > > > -mayuresh > > > > > > > > > > > >
7.1 on Toshiba Satellite
Finally running OpenBSD 7.1 on a mobile Toshiba / Dynabook Satellite Pro L50-G-11J, very happy. Got XFCE though I might work quite a bit from the console, I really like the old ways too. Required GPT, does'nt support MBR. Regards Jean-François
Re: happy birthday theo
Happy birthday! >On 19.05.2022 09:33, Amit Kulkarni wrote: > Happy Birthday to Theo! > > On Thu, May 19, 2022 at 4:46 AM Brodey Dover wrote: > > > > Happy Birthday Theo! > > > > On Thu, 19 May 2022 at 02:51, Mayuresh Kathe wrote: > > > > > here's wishing theo deraadt a very happy birthday. > > > wish you many more years of producing great software and being > > > cantankerous. :p > > > have a great day today and an amazing year ahead. > > > -mayuresh > > > > > > >
Re: happy birthday theo
On 2022-05-19 02:49, Mayuresh Kathe wrote: here's wishing theo deraadt a very happy birthday. Hhmmm... Given the precision found in OBSD, one should really wish Theo a happy anniversary of his birthday. And I do! jog wish you many more years of producing great software and being cantankerous. :p have a great day today and an amazing year ahead. -mayuresh
Re: happy birthday theo
Happy Birthday Theo!!! On Wed, May 18, 2022, at 11:49 PM, Mayuresh Kathe wrote: > here's wishing theo deraadt a very happy birthday. > wish you many more years of producing great software and being cantankerous. > :p > have a great day today and an amazing year ahead. > -mayuresh
Re: happy birthday theo
Happy Birthday to Theo! On Thu, May 19, 2022 at 4:46 AM Brodey Dover wrote: > > Happy Birthday Theo! > > On Thu, 19 May 2022 at 02:51, Mayuresh Kathe wrote: > > > here's wishing theo deraadt a very happy birthday. > > wish you many more years of producing great software and being > > cantankerous. :p > > have a great day today and an amazing year ahead. > > -mayuresh > > > >
Re: calling all PFsync users for experience, gotchas, feedback, tips and tricks
On Thu, May 19, 2022 at 09:35:53AM -, Stuart Henderson wrote: > On 2022-05-19, Jordan Geoghegan wrote: > > I've run pfsync + CARP for a number of years now. One interesting > > "gotcha" I discovered when building an IPv6-only test network was that > > pfsync does not work in an IPv6-only environment. I tried both unicast > > and multicast configurations to no avail. When pfsync has a parent > > interface that only has an IPv6 address assigned (ie no IPv4 at all), no > > pfsync traffic transits the interface. Just thought I'd share this > > little tidbit since you were looking for edge cases and gotchas and > > since IPv6 support (or lack thereof) is not mentioned in the manpage. > > That sounds like a bug not an "edge case". To my knowledge nobody ever > reported that, consider writing it up for bugs@. Connectivity issues in a pure IPv6 environment are often due to NDP packets not being correctly passed. For example, the default firewall ruleset in /etc/rc is supposed to allow basic connectivity such as ssh. However, it breaks IPv6 neighour discovery protocol in at least some situations. I'm not in the office at the moment, so I can't test anything on a current system, but notes I made last year which would have been with 6.8-release: Considering a direct link between two machines with no routing or other network hardware inbetween: Output from ndp -a with the default ruleset: Neighbor Linklayer Address Netif ExpireS Flags node1(incomplete) em0 expired N node2b4:2e:99:f2:2f:67 em0 permanent R l fe80::b62e:99ff:fef2:2f67%em0b4:2e:99:f2:2f:67 em0 permanent R l The default ruleset allows neighbour solicitations out and neighbour advertisements in. Adding rules to allow neighbour solicitations in and neighbour advertisements out, fixes the problem.
Re: happy birthday theo
Happy Birthday Theo! On Thu, 19 May 2022 at 02:51, Mayuresh Kathe wrote: > here's wishing theo deraadt a very happy birthday. > wish you many more years of producing great software and being > cantankerous. :p > have a great day today and an amazing year ahead. > -mayuresh > >
Re: best place to put export variables
On 2022-05-18, Michael wrote: > On 05/19/22 01:44AM, Mihai Popescu wrote: >> Hello, >> >> I want to export XDG_CACHE_HOME variable used by Xorg. >> What is the best place (file or ?) to export this variable? >> >> I remember i used some file to export a long time ago PS1 variable. >> Should I use ~/.login file or is it a better way to export this xorg >> variable? >> >> OpenBSD amd64 here, snapshots install. >> >> Thank you. >> > > Non-expert answer here, but I recently was trying various places to get > the following working: > > export QT_QPA_PLATFORMTHEME=qt5ct > > Everywhere online (Linux users mainly) were saying to put it in > .profile, which did not work on OpenBSD. What ended up working for me > is putting it in .xsession. So I assume that is a good place for any > export command like this. .xsession is not a bad place for things relating to a single user in X. For a more global thing, environment variables can be set in login.conf, independent of shells etc.
Re: calling all PFsync users for experience, gotchas, feedback, tips and tricks
On 2022-05-19, Jordan Geoghegan wrote: > I've run pfsync + CARP for a number of years now. One interesting > "gotcha" I discovered when building an IPv6-only test network was that > pfsync does not work in an IPv6-only environment. I tried both unicast > and multicast configurations to no avail. When pfsync has a parent > interface that only has an IPv6 address assigned (ie no IPv4 at all), no > pfsync traffic transits the interface. Just thought I'd share this > little tidbit since you were looking for edge cases and gotchas and > since IPv6 support (or lack thereof) is not mentioned in the manpage. That sounds like a bug not an "edge case". To my knowledge nobody ever reported that, consider writing it up for bugs@.
Re: calling all PFsync users for experience, gotchas, feedback, tips and tricks
On 5/11/22 12:32, Tom Smyth wrote: Hello Folks, We are updating some course material for an upcoming PF firewall course, and I would like to put a call out to those who use PFsync in a redundant firewall cluster about your user experience, have you come across any edge cases? have you any tips or tricks about PFSync. have you come across any edge cases / minor misconfigurations / suboptimal configurations that caused problems, were there some tweaks you had to make to make your system scale ? it is likely that people who are running PFSync have more complicated firewall configs. and I would like to see what tuning other people have done in the field. I would appreciate any feedback or problem descriptions (with our without solutions) what is the largest throughput firewall you deployed with PFSync? how was your experience of running with PFsync vs without PFsync on your firewall. Thanks again, I've run pfsync + CARP for a number of years now. One interesting "gotcha" I discovered when building an IPv6-only test network was that pfsync does not work in an IPv6-only environment. I tried both unicast and multicast configurations to no avail. When pfsync has a parent interface that only has an IPv6 address assigned (ie no IPv4 at all), no pfsync traffic transits the interface. Just thought I'd share this little tidbit since you were looking for edge cases and gotchas and since IPv6 support (or lack thereof) is not mentioned in the manpage. Regards, Jordan
Re: best place to put export variables
> > I want to export XDG_CACHE_HOME variable used by Xorg. > > What is the best place (file or ?) to export this variable? > > I remember i used some file to export a long time ago PS1 variable. > > Should I use ~/.login file or is it a better way to export this xorg > > variable? > Everywhere online (Linux users mainly) were saying to put it in > .profile, which did not work on OpenBSD. What ended up working for me > is putting it in .xsession. So I assume that is a good place for any > export command like this. Well, .profile is a shell init file setting, so if you read advice from people who are running another shell than you are, then their solutions will not work. It is not (primarily) about what OS you are using, but which shell you have, and which files it will read and parse at startup. .xsession will also work, in the graphical environments, and for QT that might be implied of course. -- May the most significant bit of your life be positive.