On Sat, Oct 17, 2015 at 03:57:09AM +0000, Gerald Hanuer wrote: > Hello bugs@. > > Pledge(2) appears to kill /usr/bin/openssl enc.... >
This bug has already been reported privately and diff has been just commited for that. The problem should be resolved now. > 29093 openssl CALL kbind(140187732356888,24,-2708749615844173383) > 29093 openssl RET kbind 0 > 29093 openssl CALL open(0x862a03bea3f,0<O_RDONLY>) > 29093 openssl NAMI "/dev/tty" > 29093 openssl RET open 4 > 29093 openssl CALL > open(0x862a03bea3f,0x601<O_WRONLY|O_CREAT|O_TRUNC>,0666<S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH>) > 29093 openssl NAMI "/dev/tty" > 29093 openssl RET open 5 > 29093 openssl CALL kbind(140187732356808,24,-2708749615844173383) > 29093 openssl RET kbind 0 > 29093 openssl CALL ioctl(4,TIOCGETA,0x862a0711160) > 29093 openssl PSIG SIGKILL SIG_DFL > > Adding ( tty ioctl ) separately and together did not correct the issue. > Same ktrace(1) output as above. Just doing a grep for searching pledge call should let you understand the logic: openssl.c is the "main" function (which a first pledge call). Later, depending of subcommand use (here "enc"), another pledge call occurs. You could also check that using ktrace/kdump: $ kdump | grep pledge 11502 openssl CALL pledge(0xcd5fe663120,0) 11502 openssl STRU pledge request="stdio inet rpath wpath cpath proc" 11502 openssl RET pledge 0 11502 openssl CALL pledge(0xcd5fe65bb33,0) 11502 openssl STRU pledge request="stdio rpath wpath cpath" 11502 openssl RET pledge 0 There are 2 pledge(2) call: so two "abort" to add to get a backtrace... > /usr/bin/openssl enc... was working as of Sep 25 current. > Not sure when this stopped working, it was noticed Oct 15. Please try with a new snapshot, or fetch and build src/usr.bin/openssl directory. Thanks. -- Sebastien Marie
