Wg-quick warns that unwind may leak DNS queries
Hello, I was hoping to get some clarification on a warning I noticed today after running wg-quick (part of wireguard-tools) to connect to a commercial VPN provider. I run OpenBSD 7.1, with all the patches installed. The notice was: "[!] WARNING: unwind will leak DNS queries" I was not able to find any discussion of this on the internet. My purpose in using unwind is to reduce the need for third-party DNS queries (primarily for privacy). Is wg-quick saying that unwind may leak the queries to the VPN provider? If that is the case I am not concerned. The VPN provider has a connection check that says "No DNS leaks". What I would want to know is if my DNS queries are visible to my ISP. I thought that they are not, with unwind + VPN, but this warning causes some doubt. Any advice on how to clear this up would be appreciated. Michael
Re: console in mc like in linux
On 2022-09-14, Stuart Henderson wrote:
> On 2022-09-13, 3 wrote:
>> sorry guys for the stupid question, but the answers to stupid questions keep
>> the world going :) in linux, there is a convenient feature in mc, when when
>> pressing ctrl-o we not only see the console, but also we can execute
>> commands in it. how to achieve this in obsd? it's about remote access via
>> putty, if it matters(i have no way to test the behavior without putty)
>
> Not a stupid question, this mc feature ("subshell") is implemented
> in a bit of a complex way.
>
> mc only supports it with certain shells: bash, zsh, tcsh, fish, dash
> (and ash, but that's not available on openbsd)
>
> Also there is a default terminal mapping on the ^O key which you may
> need to override with "stty discard undef"
>
> I'll see if I can get it to work for ksh, but for now if you use one
> of the supported shells, it should work.
... I added support for OpenBSD's ksh to the port in -current
--
Please keep replies on the mailing list.
Re: console in mc like in linux
On 2022-09-13, 3 wrote:
> sorry guys for the stupid question, but the answers to stupid questions keep
> the world going :) in linux, there is a convenient feature in mc, when when
> pressing ctrl-o we not only see the console, but also we can execute commands
> in it. how to achieve this in obsd? it's about remote access via putty, if it
> matters(i have no way to test the behavior without putty)
Not a stupid question, this mc feature ("subshell") is implemented
in a bit of a complex way.
mc only supports it with certain shells: bash, zsh, tcsh, fish, dash
(and ash, but that's not available on openbsd)
Also there is a default terminal mapping on the ^O key which you may
need to override with "stty discard undef"
I'll see if I can get it to work for ksh, but for now if you use one
of the supported shells, it should work.
--
Please keep replies on the mailing list.
Re: A minimal browser in base
We used to have lynx in the base system. It was removed because of security concerns and no-one willing to audit/replace it. This is a fairly common pattern in OpenBSD. Considering the complexity of the web, I don't see this ending any differently with any other text browser.
Issue with FDE and bootblocks on 7.2 snapshots ?
Hi, I’ve been trying to install my T460s from scratch (using FDE with UEFI boot and gpt disk configuration) using the 2022-09-13 snapshot. At the end of installation process, I keep getting « Failed to install bootblocks ». I tried a several times. Also tried a non-FDE installation (using UEFI gpt) and it also failed. I’ve just run the FDE installation using install71.img and everything went ok. Then I « sysupgrade -s » and everything went ok too. Just saying in case it is a bug in install72.img. Regards, Joel
Re: Old Unix manuals (was: Re: A minimal browser in base)
On Wed, Sep 14, 2022 at 07:00:56AM +0100, Jason McIntyre wrote: > On Tue, Sep 13, 2022 at 06:54:40PM -0400, luna wrote: > > On Tue, Sep 13, 2022 at 07:04:55 +0100, Jason McIntyre wrote: > > > hi. > > > > > > we stopped installing them because many of them were falling out of date > > > and there wasn;t really the resources (or motivation) to update them. > > > however not all of them were removed. although no longer installed, some > > > of the better ones remain in the source tree. from a quick look: > > > > Note that you'll need to pull /usr/src/share/mk/bsd.doc.mk out of the > > attic and install it in /usr/share/mk, and then you'll need a copy of > > groff to build these documents. I haven't tested this on a recent > > version of OpenBSD, though I can say that older versions of both > > OpenBSD and FreeBSD work quite well for building these old docs. If you > > want versions you can read on your terminal, you can pass -Tascii to > > groff like FreeBSD's bsd.doc.mk does, which is (handwaving over other > > details here) what groff does to render manpages. > > > > I can wholeheartedly recommend building and reading the ones you can > > find, especially if you're interested in Unix history. They're something > > of a time capsule, providing a snapshot of what Unix was at the time and > > how people used it. In addition, as said above, some of them are just as > > applicable today as when they were written. > > > > also, although it won;t be pretty, you can just pass the documents to > mandoc and get something that's at least semi-readable. > > jmc can also be found at https://docs-legacy.freebsd.org/44doc/ https://wolfram.schneider.org/bsd/7thEdManVol2/ https://9p.io/7thEdMan/v7vol2b.pdf http://bitsavers.org/pdf/att/unix/7th_Edition/UNIX_Programmers_Manual_Seventh_Edition_Vol_2_1983.pdf
Re: Old Unix manuals (was: Re: A minimal browser in base)
On Tue, Sep 13, 2022 at 06:54:40PM -0400, luna wrote: > On Tue, Sep 13, 2022 at 07:04:55 +0100, Jason McIntyre wrote: > > hi. > > > > we stopped installing them because many of them were falling out of date > > and there wasn;t really the resources (or motivation) to update them. > > however not all of them were removed. although no longer installed, some > > of the better ones remain in the source tree. from a quick look: > > Note that you'll need to pull /usr/src/share/mk/bsd.doc.mk out of the > attic and install it in /usr/share/mk, and then you'll need a copy of > groff to build these documents. I haven't tested this on a recent > version of OpenBSD, though I can say that older versions of both > OpenBSD and FreeBSD work quite well for building these old docs. If you > want versions you can read on your terminal, you can pass -Tascii to > groff like FreeBSD's bsd.doc.mk does, which is (handwaving over other > details here) what groff does to render manpages. > > I can wholeheartedly recommend building and reading the ones you can > find, especially if you're interested in Unix history. They're something > of a time capsule, providing a snapshot of what Unix was at the time and > how people used it. In addition, as said above, some of them are just as > applicable today as when they were written. > also, although it won;t be pretty, you can just pass the documents to mandoc and get something that's at least semi-readable. jmc
