Re: pkg_add: ftp: connect: Invalid argument

On 02/04/2017 10:46 PM, jungle boogie wrote: Ping was failing with something very similar: ping: sendmsg: Invalid argument ping: wrote yahoo.com 64 chars, ret=-1 Follow up to my own mystery... I have two network interfaces on this laptop: bge0 and wpi0, both of which are on the same

Re: Limits for bcrypt_pbkdf(3) vs bcrypt(3)

cheers Ted, On Tue, 07 Feb 2017 14:50:49 -0500 "Ted Unangst" wrote: > bytevolc...@safe-mail.net wrote: > > 1. Does the 72-character limit also apply to bcrypt_pbkdf() > > [presumably this will mean softraid(4) crypto won't accept > > passwords >72 chars anymore]? > > No.

Solved -- Was: Isakmpd Cert question.

On Tue, Feb 07, 2017 at 01:30:13PM -0500, Christopher Sean Hilton wrote: > On Tue, Feb 07, 2017 at 11:23:29AM -0500, Christopher Sean Hilton wrote: > > I'm using isakmpd to manage an ipsec VPN between OpenBSD 5.8 <-> OpenBSD > > 6.0. This also manages a VPN between Mac OS X/ IPsecuritas and

relayd send/expect syntax

Hi, Running the most recent amd64 snapshot on ESXi. OpenBSD r1.mwlucas.org 6.0 GENERIC#162 amd64 I'm trying to use relayd's check send/expect support to verify a daemon's banner comes up. After problems I've stripped this down to the simplest possible config, a single known good mail server.

Re: Can OpenBSD do mixed b/g/n mode in hostap?

On Tue, Feb 07, 2017 at 08:16:10PM +, Tom Murphy wrote: > Hi Stefan, > > I upgraded my kernel to 24 January 2017 and every once in a while I get: > > athn0: device timeout > > I've gotten 3 of these in 12 days. Running: > > ifconfig athn0 down; sh /etc/netstart athn0 > > fixes

Re: Can OpenBSD do mixed b/g/n mode in hostap?

Hi Stefan, I upgraded my kernel to 24 January 2017 and every once in a while I get: athn0: device timeout I've gotten 3 of these in 12 days. Running: ifconfig athn0 down; sh /etc/netstart athn0 fixes this, but not had this on mode 11g. Could it be something in the 11n hostap code?

Re: Limits for bcrypt_pbkdf(3) vs bcrypt(3)

Have u tried scrypt? bytevolc...@safe-mail.net skrev: (7 februari 2017 16:16:21 CET) >I am investigating bcrypt_pbkdf(3) or bcrypt(3) to secure passphrases >within an existing application. > >However, the man page for bcrypt_pbkdf() does not mention the >72-character password limit that bcrypt()

Re: Limits for bcrypt_pbkdf(3) vs bcrypt(3)

bytevolc...@safe-mail.net wrote: > 1. Does the 72-character limit also apply to bcrypt_pbkdf() [presumably >this will mean softraid(4) crypto won't accept passwords >72 chars >anymore]? No. There is no limit. (The inputs can also contain 0 bytes.) > 2. What is the recommended buffer size

Re: Isakmpd Cert question.

On Tue, Feb 07, 2017 at 11:23:29AM -0500, Christopher Sean Hilton wrote: > I'm using isakmpd to manage an ipsec VPN between OpenBSD 5.8 <-> OpenBSD > 6.0. This also manages a VPN between Mac OS X/ IPsecuritas and OpenBSD 6.0. > Some more information on this and possibly a real question: Here's

Isakmpd vs iked

How hard is it to transition from an isakmpd managed IPsec VPN to iked managment? I have a certificate based isakmpd solution that works. It is mainly just a matter of rsyncing the directories and using a little editor magic on the ipsec.conf file to create iked.conf? Thanks in advance, -- Chris

Isakmpd Cert question.

I'm using isakmpd to manage an ipsec VPN between OpenBSD 5.8 <-> OpenBSD 6.0. This also manages a VPN between Mac OS X/ IPsecuritas and OpenBSD 6.0. The example describes a situation where you have one self signed root certificate located in /etc/isakmpd/ca/root.crt and otherside::client.crt from

Limits for bcrypt_pbkdf(3) vs bcrypt(3)

I am investigating bcrypt_pbkdf(3) or bcrypt(3) to secure passphrases within an existing application. However, the man page for bcrypt_pbkdf() does not mention the 72-character password limit that bcrypt() does, especially given bcrypt_pbkdf() appears to accept an output buffer whose length is

Re: pkg_add: ftp: connect: Invalid argument

Am 5. Februar 2017 07:46:43 MEZ schrieb jungle boogie : > On 02/04/2017 07:17 PM, Philip Guenther wrote: > >> Is this it? > >> > >> "Trying 129.128.5.191... > > ... > >> 80377 ftp CALL connect(3,0xaf766dd0bf0,16) > >> 80377 ftp STRU struct sockaddr { AF_INET,