YESS!! Thank you qwerjkl...
I can confirm, "bioctl -c C -l ... softraid0" seems to have picked up the
existing partition...and after a "cd /dev && sh MAKEDEV sd2", the installer
was picked up the device (sd2), and I was able to get back to a working
system.
Thanks again!
On Mon, Jun 3, 2019 at
On 6/3/19 8:17 PM, Bryan Stenson wrote:
> Hi all -
>
> I'm running -CURRENT on a SSD with FDE encryption using softraid/crypto
> with a passphrase entered via the keyboard at boot. It worked great.
> Then, I upgraded to a build that had a broken bootloader (reported to be
> fixed now: "Re: amd64
I have done that two days ago. When you use bioctl -c ... -l ... softraid0 on
an existing raid configuration, it will map the raid volume to another sd
device. You will be prompted for a password if your raid level is crypto. This
will _not_ create another raid or overwrite your data, unless you
Hi all -
I'm running -CURRENT on a SSD with FDE encryption using softraid/crypto
with a passphrase entered via the keyboard at boot. It worked great.
Then, I upgraded to a build that had a broken bootloader (reported to be
fixed now: "Re: amd64 snapshot very broken (Jun 1 02:24:13)"). Per that
t
Hi,
I have found the following errors on the log:
/bsd: chrome[18585]: pledge "", syscall 289
they appear everytime I start chrome.. they are about 4 or 5, what means?
It's the first time, yesterday and in the past there aren't any.
thx cord
Diogo Pinela [dpin...@ipatimup.pt] wrote:
>
> That's interesting, but it doesn't answer my question at all.
I don't know if Kristaps is planning on updating it. Nobody else has
mentioned it. Maybe it's a prime job for you to investigate?
The final RFC version, ACMEv2, is documented in RFC 8555:
> 4. jun. 2019 kl. 00:32 skrev Josef Pospisil :
>
> Can someone be that kind and explain to me if the whole code of OpenBSD
> was checked at least once since the openBSD was founded? That there are
> no backholes like i was describing?
Code auditing (aka ‘reading the code like the devil reads th
I think the OpenBSD code review is taken so seriously thank is more than a
good practice matter.
https://www.openbsd.org/security.html
Em seg, 3 de jun de 2019 às 22:33, Josef Pospisil
escreveu:
> Hey, thank you all for this mailing list.
>
> I have a question regarding the security of OpebB
In the latest mds errata patch, I noticed that one of the steps is to
run fw_update. From briefly looking over the syspatch script, I don't
see it calling fw_update once a patch is applied.
Would you welcome a diff to add support for this? If so I can look at
writing one. It would check agains
Hi,
I am planning a mail server of opensmtpd and dovecot. I'd be glad to know if
there is any way to save a copy of mail to dovecot's "Sent" mail box before
relaying them out.
I am also not about find any docs on opensmtpd-extra-pgsql. Is there any guide
to link postgresql up with smtpd for vi
On 2019-06-02, Артур Истомин wrote:
> I'm trying update BIOS on alix2d13 board with flashrom ver 1.0 on OpenBSD 6.5
>
> # flashrom -w alix1.bin -p internal
> flashrom v1.0 on OpenBSD 6.5 (i386)
> flashrom is free software, get the source code at https://flashrom.org
>
> Calibrating delay loop... d
On sáb, jun 1, 2019 at 3:42 PM, Patrick Dohman
wrote:
On May 31, 2019, at 10:42 AM, Diogo Pinela
wrote:
As I understand it, acme-client currently only supports
ACMEv1. Let's Encrypt recently announced they're going
to begin progressively deprecating that protocol starting
this November
On Mon, Jun 03, 2019 at 10:18:38AM -0400, sven falempin wrote:
> On Mon, Jun 3, 2019 at 1:44 AM Otto Moerbeek wrote:
> >
> > Hi,
> >
> > If you ever wanted to be more involved in OpenBSD here's a chanche:
> >
> > https://marc.info/?l=openbsd-tech&m=155950103825035&w=2
> >
> > It requires setting
On Mon, Jun 3, 2019 at 1:44 AM Otto Moerbeek wrote:
>
> Hi,
>
> If you ever wanted to be more involved in OpenBSD here's a chanche:
>
> https://marc.info/?l=openbsd-tech&m=155950103825035&w=2
>
> It requires setting up a test machine running a recent snapshot, so
> that's a nice first step. Then g
On 2019-06-01, Christian Weisgerber wrote:
> The amd64 snapshot with BUILDINFO
> Build date: 1559355853 - Sat Jun 1 02:24:13 UTC 2019
> is very broken. Specifically, the boot loader is broken.
Sorry, I forgot to follow up: This has been fixed for more than a
day now.
--
Christian "naddy" Wei
On Mon, Jun 03, 2019 at 06:28:30AM +1000, Zach Nedwich wrote:
> Did you try booting in single mode? "boot -s" at the boot prompt, then mount
> -a to mount /usr/bin.
No, I don't have serial port.
For installing/upgrading OpenBSD, I'm using QEMU and CF-card/USB adapter.
To run system with kern.s
On Mon, Jun 03, 2019 at 10:55:47AM +0200, Mara Toni wrote:
> Hello,
>
> did anybody hear about the:
>
> https://vigilance.fr/vulnerability/OpenBSD-privilege-escalation-via-vmmints-28874
>
> OpenBSD: privilege escalation via vmmints
> Synthesis of the vulnerability
> An attacker can bypass rest
Hello,
did anybody hear about the:
https://vigilance.fr/vulnerability/OpenBSD-privilege-escalation-via-vmmints-28874
OpenBSD: privilege escalation via vmmints
Synthesis of the vulnerability
An attacker can bypass restrictions via vmmints of OpenBSD, in order to
escalate his privileges.
Vulner
18 matches
Mail list logo
