Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Samarul Meu
On Thu, Jan 28, 2021 at 4:38 AM Nick Holland wrote: > -a at the boot prompt is my thought, too...but the little bit of your > dmesg that you show seems to indicate you are not seeing the encrypted > drive handled by in softraid at all. So I have my concerns this won't > do much but delay the

Re: iked(8) CREATE_CHILD_SA successful at initial connection time, fail at rekey interval

2021-01-27 Thread Darren S.
On Wed, Jan 27, 2021 at 3:28 AM Tobias Heider wrote: > looks like a PFS problem. > > Here's where it fails: > > Jan 26 18:48:30 strannik iked[41041]: spi=0x6184b254a8e8d175: > > ikev2_log_proposal: ESP #1 DH=MODP_2048 > > At the moment, PFS groups must be enabled manually. > Try this: > > ikev2

Re: OpenBSD (memory management) performance issues

2021-01-27 Thread Otto Moerbeek
On Wed, Jan 27, 2021 at 08:39:46AM +0100, Otto Moerbeek wrote: > On Tue, Jan 26, 2021 at 04:08:40PM +, Marek Klein wrote: > > > Hi, > > > > We are working on an appliance like product that is based on OpenBSD. > > Recently we found out that our performance critical C++ program is > > ~2.5

Re: OpenSMTPD is not sending e-mail.

2021-01-27 Thread Mitch K.
Diana Eichert wrote on Wed [2021-Jan-27 08:30:34 -0700]: > On Tue, Jan 26, 2021 at 5:25 PM latincom wrote: > > > > Hello misc@ > > > > I can not believe that the solution has been to open port 25, Vultr rent > > servers whit port 25 closed! > > > > Thanks so much to Stuart Henderson for the

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Nick Holland
On 1/27/21 1:45 PM, Samarul Meu wrote: mie., 27 ian. 2021, 20:24 a scris: Ironically this is the same error I have been getting, and recently posted about in the thread "Bootloader on USB stick fails with "root device not found"" ... I read your thread just now. I will try the -a option.

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread tetrahedra
On Wed, Jan 27, 2021 at 05:50:07PM +0200, Samarul Meu wrote: After searching online I discovered this: boot sr0a:/bsd. Now it asks for my Passphrase and it starts booting but then it hangs softraid0 at root scsibus2 at softraid0: 256 targets panic: root device (3312a...) not found Stopped at

Re: auto-boot

2021-01-27 Thread Stuart Longland
On 26/1/21 3:04 am, Mihai Popescu wrote: That short with a metallic wire was just for quick check. It is not recommended for prolonged usage! It will block any communication on the RS232 cable. Probably not very healthy for the RS-232 driver either. High-valued resistor is probably a safer

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread vejetaryenvampir
Samarul Meu wrote: > It showed only this: > > open(hd0a:/etc/boot.conf): Invalid argument > boot> > cannot open hd0a:/etc/random.seed: Invalid argument > booting hd0a:/bsd: open hd0a:/bsd: Invalid argument > failed(22). will try /bsd > > After searching online I discovered this: boot

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Erling Westenvik
On Wed, Jan 27, 2021 at 05:50:07PM +0200, Samarul Meu wrote: > I was playing with some script trying to create an encrypted image and > accidentally I did bioctl -d sd0 where sd0 is the disk with my OpenBSD > install. Of course the system hanged. When I tried to reboot it no longer > ask me for my

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Samarul Meu
mie., 27 ian. 2021, 20:24 a scris: > > Ironically this is the same error I have been getting, and recently > posted about in the thread "Bootloader on USB stick fails with "root > device not found"" ... > I read your thread just now. I will try the -a option. Interesting, but I must mention

Re: plugging head phones does not mute speaker

2021-01-27 Thread Björn Gohla
Maurice McCarthy writes: > Sndiod is to be the default method of controliing audio. > Run sndiod and see what sndioctl says. > > doas rcctl enable sndiod > doas rcctl start sndiod > doas sndioctl [...] thanks. this does not solve the problem unfortunately. -- cheers, björn

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Ashton Fagg
Color me surprised...I can't say I've ever tried it to know. Still, rm is a little different to something that's talking directly to a device. On Wed, 27 Jan 2021 at 12:33, Daniel Jakots wrote: > > On Wed, 27 Jan 2021 11:31:13 -0500, Ashton Fagg > wrote: > > > Do you want "rm -rf /" to hold

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Daniel Jakots
On Wed, 27 Jan 2021 11:31:13 -0500, Ashton Fagg wrote: > Do you want "rm -rf /" to hold your hand also? As a matter of fact, it does :) https://github.com/openbsd/src/commit/c11d908c7069eb03d103482ce1d0227f3d47b349

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Ashton Fagg
Pressed send too early. It is also worth pointing out that I'm fairly sure every *nix has similar ways to blow your arms and legs off. There's nothing special about OpenBSD or bioctl in that sense. On Wed, 27 Jan 2021 at 11:31, Ashton Fagg wrote: > > On Wed, 27 Jan 2021 at 10:55, Samarul Meu

Re: Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Ashton Fagg
On Wed, 27 Jan 2021 at 10:55, Samarul Meu wrote: > > I am a little puzzled that there is no failsafe mechanism for commands like > bioctl or fdisk on the already mounted disk. For me the obvious think was > that the system complains when trying bioctl -d sd0. To be fair, bioctl talks to block

Re: 6.8 and Procmail/Formail: anyone still using them?

2021-01-27 Thread Steve Williams
On 26/01/2021 10:43 a.m., Austin Hook wrote: Wonder if anyone is still using Procmail/Formail under 6.8 for presorting incoming mail before it hits one's main inbox. Also wondering if folks send the remainimg mail, after filtering, to /var/mail/*user*, or to ~/mbox or to ~mail/mbox. Any

Managed to mess up the system encrypted disk. I can no longer boot.

2021-01-27 Thread Samarul Meu
Hello! Please help. I really messed up. I was playing with some script trying to create an encrypted image and accidentally I did bioctl -d sd0 where sd0 is the disk with my OpenBSD install. Of course the system hanged. When I tried to reboot it no longer ask me for my passphrase. It showed

Re: OpenSMTPD is not sending e-mail.

2021-01-27 Thread Diana Eichert
On Tue, Jan 26, 2021 at 5:25 PM latincom wrote: > > Hello misc@ > > I can not believe that the solution has been to open port 25, Vultr rent > servers whit port 25 closed! > > Thanks so much to Stuart Henderson for the solution. Yes Vultr and many other VM providers block tcp port 25 by default,

Re: auto-boot

2021-01-27 Thread Diana Eichert
On Tue, Jan 26, 2021 at 5:30 AM Stuart Longland wrote: > > On 25/1/21 11:40 pm, Bastien Durel wrote: > > Hello, > > > > Short-circuit pins 3-5 using my DB9 cable as Mihai Popescu said[1] > > worked. > > Alas, this setup prevent to plug-in the cable on the other side ^^ > > > > But this confirm

Re: Error trying to compile Suricata 6.0.1 under OpenBSD 6.8 (SOLVED)

2021-01-27 Thread Carlos Lopez
Hi all, I have exported "CC=/usr/bin/clang" in the shell and now Suricata compiles ok. Many thanks to all for your help. On 27/1/21, 14:45, "owner-m...@openbsd.org on behalf of Carlos Lopez" wrote: HI Stuart, Many thanks for your help. I have tried to compile using

Re: Error trying to compile Suricata 6.0.1 under OpenBSD 6.8

2021-01-27 Thread Carlos Lopez
HI Stuart, Many thanks for your help. I have tried to compile using "--with-clang=/usr/bin/clang" flag but same error appears... On 27/1/21, 13:49, "owner-m...@openbsd.org on behalf of Stuart Henderson" wrote: On 2021-01-27, Carlos Lopez wrote: > Hi all, > > I am trying to

Re: Error trying to compile Suricata 6.0.1 under OpenBSD 6.8

2021-01-27 Thread Carlos Lopez
Thanks Gonzalo. Yes I would like to compile without rust support and with GeoIP support ... On 27/1/21, 13:49, "Gonzalo Rodriguez" wrote: I don’t remember now the version we have in 6.8 but are you compiling it for some reason instead of use the package? — gonzalo > On 27.

Re: Error trying to compile Suricata 6.0.1 under OpenBSD 6.8

2021-01-27 Thread Gonzalo Rodriguez
I don’t remember now the version we have in 6.8 but are you compiling it for some reason instead of use the package? — gonzalo > On 27. Jan 2021, at 13:31, Carlos Lopez wrote: > > Hi all, > > I am trying to compile suricata 6.0.1 with some custom options and the > following error is

Re: Error trying to compile Suricata 6.0.1 under OpenBSD 6.8

2021-01-27 Thread Stuart Henderson
On 2021-01-27, Carlos Lopez wrote: > Hi all, > > I am trying to compile suricata 6.0.1 with some custom options and the > following error is returned: > > hecking for strlcat... yes > checking for special C compiler options needed for large files... no > checking for _FILE_OFFSET_BITS value

Error trying to compile Suricata 6.0.1 under OpenBSD 6.8

2021-01-27 Thread Carlos Lopez
Hi all, I am trying to compile suricata 6.0.1 with some custom options and the following error is returned: hecking for strlcat... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking host os...

OpenBSD (memory management) performance issues

2021-01-27 Thread Marek Klein
Hi, We are working on an appliance like product that is based on OpenBSD. Recently we found out that our performance critical C++ program is ~2.5 times slower on OpenBSD compared to Ubuntu 20.04. The program basically just reads data from stdin, does some transformation of the data, and returns

Re: iked(8) CREATE_CHILD_SA successful at initial connection time, fail at rekey interval

2021-01-27 Thread Tobias Heider
Hi, looks like a PFS problem. Here's where it fails: > Jan 26 18:48:30 strannik iked[41041]: spi=0x6184b254a8e8d175: > ikev2_log_proposal: ESP #1 DH=MODP_2048 At the moment, PFS groups must be enabled manually. Try this: ikev2 "home" passive esp inet \ from 10.0.10.0/24 to 10.0.1.0/24

Re: 6.8 and Procmail/Formail: anyone still using them?

2021-01-27 Thread Marcus MERIGHI
aus...@computershop.ca (Austin Hook), 2021.01.26 (Tue) 18:43 (CET): > Wonder if anyone is still using Procmail/Formail under 6.8 for > presorting incoming mail before it hits one's main inbox. Regarding procmail beware of this: https://marc.info/?l=openbsd-ports=151256201621939 formail is not in

smtpd virtual table with only userparts

2021-01-27 Thread Péter Bertalan Zoltán
For an smtpd.conf containing this: 8< table domains { mydomain.tld } table virtuals file:/etc/mail/virtual action "domain" maildir "/var/vmail/mydomain.tld/%{dest.user}" virtual match from any for domain action "domain" 8< The