Re: Passwd cipher for YP

> On Thu, Nov 19, 2015 at 03:36:43PM -0700, Theo de Raadt wrote: > > > I am rather late to this thread... > > > > > > On Thursday 15 October 2015 15:46:47, Raimo Niskanen wrote: > > > > > > Are there more password ciphers planned for the future e.g > > > > > > sha256 and sha512?> > > > > > > > >

Re: serious watchdog timeout issues with em driver

On 19/11/15(Thu) 17:54, Sonic wrote: > Have serious problems for over 7 weeks now with em driver, > specifically any rev of if_em.c > 1.305. Starting with rev 1.306, > released on 2015/09/30 and continuing to -current, watchdog timeouts > rue the day. Unfortunately rev 1.305 no longer builds with

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping the same?

Ah, and maybe equally importantly, what are the security ramifications of changing password/keydisk vs. wiping and installing from scratch with a new password/keydisk? Say that you would change password/keydisk today, and then next week someone gets a copy of your encrypted disk, and of your

"bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping the same?

"bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping the same? I.e. I have an encrypted partition /dev/sd0a which is encrypted using the keydisk /dev/sd1a . Say /dev/sd1a's contents were compromised. How do

Re: serious watchdog timeout issues with em driver

On Fri, Nov 20, 2015 at 8:12 AM, Martin Pieuchot wrote: > I just committed a revert to 1.305 keeping the API changes needed for > the driver to build. > > This should bring your stability back, please let us know if that's not > the case. The kernel/driver builds with those

Re: EFI: Booting from other (not the first) GPT partition possible? How? It's an Apple :-O

Oh yes, so then on 8,2 still you can boot legacy, on 12,1 you don't :( Enviado desde mi tostadora de mano > El 19 nov 2015, a las 15:53, Marc escribió: > > Thank you Gonzalo. > > Just to make sure we are talking about the same thing: > > I was already able to boot OpenBSD in

Re: Passwd cipher for YP

On Thu, Nov 19, 2015 at 03:36:43PM -0700, Theo de Raadt wrote: > > I am rather late to this thread... > > > > On Thursday 15 October 2015 15:46:47, Raimo Niskanen wrote: > > > > > Are there more password ciphers planned for the future e.g > > > > > sha256 and sha512?> > > > > > > > > > > > > No,

support new

0 C FR P Paris T Aubervilliers Z 93300 O Mehdi BADREDDINE I Mehdi BADREDDINE A 6 rue louis aragon M mehdi.badredd...@gmail.com U B +33(0) 6 73 55 27 28 X FAX N Consulting on *BSD systems, especially network-oriented issues and appliance design using OpenBSD. BSDA Certified.

ePDFView was coming back!

ePDFView was removed on ports. now, ePDFView was coming back! http://www.linuxfromscratch.org/blfs/view/svn/pst/epdfview.html http://anduin.linuxfromscratch.org/BLFS/epdfview/epdfview-0.1.8.tar.bz2

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping the same?

I was wondering the exact same thing. Looking forward to finding out. Original Message Subject: Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping the same? Local Time: November 20 2015

Re: Unix::Pledge perl module

On Thu, Nov 19, 2015 at 10:30 PM, Andrew Fresh wrote: > On Thu, Nov 19, 2015 at 04:19:19PM -0500, Richard Farr wrote: >> I've put together a simple CPAN module that allows you to use pledge(2) >> in your Perl programs. Of course it will only work on -current. > > Way cool! I

No USB 3.0 on 5.8 -current Broadwell

If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or USB 3.1 Type C port, nothing gets registered via dmesg, even if I add option USB_DEBUG option UMASS_DEBUG option XHCI_DEBUG and compile a kernel. No dmesg output upon attachment of USB 3.0 devices. If I try, via config(8)

Re: Who teach the true message about the true free software?

> Who teach the true message about the true free software? > > I ask this because I not want be deceived by hypocritical liars that teach > falsely about free software. This explains it. https://www.youtube.com/watch?v=krb2OdQksMc=1m47s

Re: No USB 3.0 on 5.8 -current Broadwell

On 20 Nov 2015 5:54 p.m., "Martin Pieuchot" wrote: > > On 20/11/15(Fri) 17:32, edward wandasiewicz wrote: > > If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or > > USB 3.1 Type C port, nothing gets registered via dmesg, even if I add > > This issue seems to

Re: No USB 3.0 on 5.8 -current Broadwell

edward wandasiewicz wrote: > On 20 Nov 2015 5:54 p.m., "Martin Pieuchot" wrote: > > > > On 20/11/15(Fri) 17:32, edward wandasiewicz wrote: > > > If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or > > > USB 3.1 Type C port, nothing gets registered via dmesg,

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping thesame?

Tinker wrote: > Ah, and maybe equally importantly, what are the security ramifications > of changing password/keydisk vs. wiping and installing from scratch with > a new password/keydisk? The master key, which the data on disk is encrypted with, is masked with your password. The master key

Re: azalia audio works, then stutters until reboot

On 11/20/15 02:12, Alexandre Ratchov wrote: On Thu, Nov 19, 2015 at 12:48:08PM -0700, luke call wrote: $cat sndiod-log snd0 pst=cfg.default: rec=0:1 play=0:1 vol=23170 dup listen(/tmp/aucat/aucat0|ini): created this is very strange, sndiod would have logged all the audio traffic. Could you

Re: No USB 3.0 on 5.8 -current Broadwell

I also get no dmesg or /var/log/messages output when I detach the USB 3.0 device from the USB 3.0 port or Type C port. If I attach and / or detach the USB 3.0 device, it's like it's not recognised at all. I do however, get an "indicator light on" the device when it's plugged in, for what it's

Who teach the true message about the true free software?

Please excuse me because I have posted on OpenBSD lists and other lists. Who teach the true message about the true free software? I ask this because I not want be deceived by hypocritical liars that teach falsely about free software. Hardcore OpenBSD user community, please, for avoid flames,

Re: No USB 3.0 on 5.8 -current Broadwell

On 20/11/15(Fri) 17:32, edward wandasiewicz wrote: > If I try to plug in various USB 3.0 umass(4) devices into a USB 3.0 or > USB 3.1 Type C port, nothing gets registered via dmesg, even if I add This issue seems to be occurring only after a warm reboot as found by jcs@. Could you tell me if

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wiping thesame?

Aha. *Is* the keydisk the master key, and hence can't be changed? Very low priority topic: What about implementing some routine for regenerating the master key, even if that would imply reprocessing *all* of the disk's contents? That could be beneficial in a place where you don't have the

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wipingthesame?

I think it would make sense to be able to do this. I have a scenario where I would like to install OpenBSD on a remote machine with a customized bsd.rd in order to automatically set it all up, feeding a password into the stdin of bioctl.. Now, bioctl doesn't allow hashed password to be fed

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wipingthesame?

Aha. *Is* the keydisk the master key, and hence can't be changed? Very low priority topic: What about implementing some routine for regenerating the master key, even if that would imply reprocessing *all* of the disk's contents? That could be beneficial in a place where you don't have the

Re: serious watchdog timeout issues with em driver

> Date: Fri, 20 Nov 2015 14:12:52 +0100 > From: Martin Pieuchot > > On 19/11/15(Thu) 17:54, Sonic wrote: > > Have serious problems for over 7 weeks now with em driver, > > specifically any rev of if_em.c > 1.305. Starting with rev 1.306, > > released on 2015/09/30 and

Re: "bioctl -P" is to change passphrase without wiping the encrypted partition's contents. How do you generate a new keydisk without wipingthesame?

Tinker wrote: > Aha. > > *Is* the keydisk the master key, and hence can't be changed? The keydisk is the mask for the master key. It can (in theory) be changed like changing a password. Really, the key disk is just a prehashed password. > > > Very low priority topic: > > What about

Re: serious watchdog timeout issues with em driver

On Fri, Nov 20, 2015 at 12:37 PM, Mark Kettenis wrote: > Thanks Martin. All is fine now. System booted with no errors and no watchdog timeouts. Thanks to all. Chris

Remove the mirrored site at openbsd.das.ufsc.br

I want the mirrored site to be removed at the following location: openbsd.das.ufsc.br The archived site is last updated in 2010.

Re: inteldrm(4) display corruption on MacBook

I just tested a 2015 MacBook Air (HD 6000 graphics) and still see the same display corruption. This seems to happen on all Intel Graphics Macs at least from HD 4000 and up and specifically your system, the 12-inch Retina MacBook, 2013 MacBook Air, and 2015 MacBook Air. Hopefully kettenis@ will