Re: Deprecate flags DH_FLAG_NO_EXP_CONSTTIME and RSA_FLAG_NO_CONSTTIME

2016-06-25 Thread Brent Cook
On Sun, Jun 26, 2016 at 12:00:51AM -0500, Brent Cook wrote: > On Sat, Jun 25, 2016 at 07:19:09PM -0600, Bob Beck wrote: > > If we are going to delete it, lets just do so > > > > IMO we can commit this removing the define. bets are we see nothing in > > ports for fallout so lets just blow it away >

Re: Deprecate flags DH_FLAG_NO_EXP_CONSTTIME and RSA_FLAG_NO_CONSTTIME

2016-06-25 Thread Brent Cook
On Sat, Jun 25, 2016 at 07:19:09PM -0600, Bob Beck wrote: > If we are going to delete it, lets just do so > > IMO we can commit this removing the define. bets are we see nothing in > ports for fallout so lets just blow it away > Sounds good, I'll commit this: Index: src/crypto/dh/dh.h =

Re: Deprecate flags DH_FLAG_NO_EXP_CONSTTIME and RSA_FLAG_NO_CONSTTIME

2016-06-25 Thread Bob Beck
If we are going to delete it, lets just do so IMO we can commit this removing the define. bets are we see nothing in ports for fallout so lets just blow it away On Saturday, 25 June 2016, Brent Cook wrote: > I searched around a bit and could find only one open-source instance > of RSA_FLAG_NO_C

Re: Deprecate flags DH_FLAG_NO_EXP_CONSTTIME and RSA_FLAG_NO_CONSTTIME

2016-06-25 Thread Brent Cook
I searched around a bit and could find only one open-source instance of RSA_FLAG_NO_CONSTTIME in the wild - something called 'anon-proxy' that lives as a zombie in the Debian repos, but hasn't had a real release since 2008 and seems to be orphaned from its original source site. I didn't even see an

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
New version, after some rewrite and input by semarie Changes to PkgInfo. - fix a regexp bug... tests showed the issue. - simplify the -z option code, as it can actually share most of the code from the rest. This means pkg_info -zm for installed packages, and funnily enough, pkg_info -zm somepack

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
Here's another approach. I believe I do not need more than @option is-branch to actually mark branched ports... The current tree is clean enough that the last component of the pkgpath is always enough to disambiguate the path (even though there are some surprising choices of names). Follows a q

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
Scratch that, doesn't work for packages where the stem changes, e.g., GCC subpackages. Guess it will really need some kind of branch annotation... :(

Re: next step, auto-branch determination

2016-06-25 Thread Marc Espie
Here is what it turns out as, -z option to pkg_info Prints just simple stem--flavor[%branch] list of installed packages... Only manual installs, no need to encumber it with dependencies. Index: OpenBSD/PkgInfo.pm === RCS file: /cvs/

next step, auto-branch determination

2016-06-25 Thread Marc Espie
The following very simple code shows that it's possible to figure out most of the branches (new % format) automatically based on comparison between fullpkgname and fullpkgpath. There are a few "false positive" (innocuous). I'm going to check soon that I have them all. This ought to yield a "bett

domknodat: use error path when FIFO not setted

2016-06-25 Thread Sebastien Marie
Hi, First, I am unsure about FIFO preprocessor variable use. But it seems to me that just returning EOPNOTSUPP isn't good here: the error code path at this point is to set `error' variable, and let code after calling VOP_ABORTOP() and vrele()/vput(). Before, there is a namei(&nd) call with:

Re: [PATCH] let the mbufs use more then 4gb of memory

2016-06-25 Thread Stefan Fritsch
On Thursday 23 June 2016 14:41:53, Mark Kettenis wrote: > We really don't want to implement bounce-buffers. Adding IOMMU > support is probably a better approach as it also brings some > security benefits. Not all amd64 hardware supports an IOMMU. And > hardware that does support it doesn't alway