Re: Keepassx without gtk

2019-02-04 Thread Daniel Jakots
On Mon, 4 Feb 2019 14:39:28 +0300, Isimsiz wrote: > Good day, sirs > Is it possible to install keepassx without gtk+? > For some reason keepassx depends on qt4 and gtk+3 > I use packages. Maybe i need to compile to exclude gtk support or its > impossible at all? I'm not sure what problem you're

Re: Keepassx without gtk

2019-02-04 Thread Isimsiz
That's kinda sad, lol, thanks you for ur help, appreciate it. пн, 4 февр. 2019 г. в 15:58, Antoine Jacoutot : > On Mon, Feb 04, 2019 at 03:04:14PM +0300, Isimsiz wrote: > > Thank you for ur reply! > > I have gtk-update-icon-cache already installed ( for feh ) but keepassx > installation keep >

Re: Keepassx without gtk

2019-02-04 Thread Isimsiz
Thank you for ur reply! I have gtk-update-icon-cache already installed ( for feh ) but keepassx installation keep installing gtk+ : # pkg_add -n keepassx quirks-3.88 signed on 2019-01-31T11:46:10Z keepassx-2.0.3p5:libgpg-error-1.35: ok keepassx-2.0.3p5:libgcrypt-1.8.4p0: ok

Re: Keepassx without gtk

2019-02-04 Thread Isimsiz
Nope, thank you, i'll look closer on it, > I'm not sure what problem you're trying to solve I dont understand what cause to install gtk+3 for keepassx or even otter-browser, that uses QT. I dont like gtk and wont have it on my laptop at all, but somehow even qt-based applications trying to

Re: Keepassx without gtk

2019-02-04 Thread Antoine Jacoutot
On Mon, Feb 04, 2019 at 03:04:14PM +0300, Isimsiz wrote: > Thank you for ur reply! > I have gtk-update-icon-cache already installed  ( for feh ) but keepassx > installation keep > installing gtk+ : That comes from qt4, not keepassx. qr4 -> gstreamer-plugins-base -> gvfs -> gcr -> gtk+3 > #

Re: amd64 cc error unknown argument '-msave-args'

2019-02-04 Thread Jyri Hovila [Turvamies.fi]
> And since you are doing this with -current *ALL OVER THE PLACE* > there are instructions that if you have trouble you should upgrade > to a snapshot. Theo, with all due respect, there are many situations where upgrading to a snapshot really isn't an option. > Those instructions to exist the

Re: amd64 cc error unknown argument '-msave-args'

2019-02-04 Thread Anthony J. Bentley
Jyri Hovila [Turvamies.fi] writes: > Theo, with all due respect, there are many situations where upgrading > to a snapshot really isn't an option. In such a situation, you shouldn't expect to be able to build -current all the time. And the advice you'll always get is: update to a snapshot,

Re: Wireguard Pre and Post Routing for OpenBSD

2019-02-04 Thread Tom Smyth
Hi Larry >From looking at your config it looks like when the wiregusrd interface comes up You want to allow forward traffic And you want masqurade traffic leaving on eth0 1)You dont really need to add and remove those rules as the wireguard tunnel comes up id suggest just adding firewall rules

Re: amd64 cc error unknown argument '-msave-args'

2019-02-04 Thread Peter J. Philipp
On Tue, Feb 05, 2019 at 07:23:59AM +0200, Jyri Hovila [Turvamies.fi] wrote: > > > And since you are doing this with -current *ALL OVER THE PLACE* > > there are instructions that if you have trouble you should upgrade > > to a snapshot. > > Theo, with all due respect, there are many situations

Wireguard Pre and Post Routing for OpenBSD

2019-02-04 Thread Larry Gadallah
Hi all: Does anyone know how to accomplish the equivalent of the Linux: PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j ACC EPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -D FORWARD -o wg0 -j A

Re: Wireguard Pre and Post Routing for OpenBSD

2019-02-04 Thread Claudio Jeker
On Mon, Feb 04, 2019 at 10:58:31PM -0800, Larry Gadallah wrote: > Hi all: > > Does anyone know how to accomplish the equivalent of the Linux: > > PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -A FORWARD -o wg0 -j > ACC > EPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE >

Re: Modern CPUs AES-NI enabling system wide

2019-02-04 Thread Denis
They in his usual style... I understand, thanks for reply. Expecting better IO results only. On 2/4/2019 12:00 PM, Theo de Raadt wrote: > Denis wrote: > >> Thank you for answers. >> >> As I understand you right amd64 kernel supports AES-NI for ipsec, >> softraid, and LibreSSL only. Right? > >

Re: Modern CPUs AES-NI enabling system wide

2019-02-04 Thread Jordan Geoghegan
On 02/04/19 00:54, Denis wrote: Softraid created bioctl -r 8192 (for test purposes) works relatively slow ~10~12Mb/s on AES-NI enabled machines. Tested for Intel and AMD CPUs. I am able to read and write over 100MB/s from my softraid volume... I just backed up my home folder to my NAS and

I am sorry

2019-02-04 Thread Leonid Bobrov
Hi, dear OpenBSD community. Please forgive me for drama I made earlier at mailing list and IRC channel. I am not a troll, I promise, I want to contribute to OpenBSD in any way I can, please give me a chance. All this time I had a depression and recently I've visited a doctor and now I am taking

Re: Keepassx without gtk

2019-02-04 Thread Antoine Jacoutot
On Mon, Feb 04, 2019 at 02:39:28PM +0300, Isimsiz wrote: > Good day, sirs > Is it possible to install keepassx without gtk+? > For some reason keepassx depends on qt4 and gtk+3 > I use packages. Maybe i need to compile to exclude gtk support or its > impossible at all? I doesn't depend on gtk+. I

Keepassx without gtk

2019-02-04 Thread Isimsiz
Good day, sirs Is it possible to install keepassx without gtk+? For some reason keepassx depends on qt4 and gtk+3 I use packages. Maybe i need to compile to exclude gtk support or its impossible at all?

Re: Keepassx without gtk

2019-02-04 Thread lists
Mon, 4 Feb 2019 15:50:38 +0300 Isimsiz > Nope, thank you, i'll look closer on it, > > > I'm not sure what problem you're trying to solve > I dont understand what cause to install gtk+3 for keepassx or even Hi misc@, I would also like to use a slimmer GUI toolkit keepassx, e.g. with FLTK. Any

Re: I am sorry

2019-02-04 Thread Chris Cappuccio
Leonid Bobrov [mazoc...@disroot.org] wrote: > Hi, dear OpenBSD community. > > Please forgive me for drama I made earlier at mailing list and > IRC channel. I am not a troll, I promise, I want to contribute to > OpenBSD in any way I can, please give me a chance. > This is the internet. Nobody

Re: 40G ixl nics

2019-02-04 Thread Chris Cappuccio
Tommy Nevtelen [to...@nevtelen.com] wrote: > > > > Any ideas ? > > Sorry, nope. > > But I don't think that there is support for any Intel NICs above 10G. > That's the whole point of ixl, to support these NICs. Tony, it's appropriate to start with a full dmesg and a report to b...@openbsd.org.

Re: I am sorry

2019-02-04 Thread Patrick Wildt
On Mon, Feb 04, 2019 at 12:52:48PM -0800, Chris Cappuccio wrote: > Leonid Bobrov [mazoc...@disroot.org] wrote: > > Hi, dear OpenBSD community. > > > > Please forgive me for drama I made earlier at mailing list and > > IRC channel. I am not a troll, I promise, I want to contribute to > > OpenBSD

Re: VMs loosing network connectivity for a few minutes on a daily basis

2019-02-04 Thread mabi
I was wondering if maybe this could have something to do with spanning tree on the bridge6 interface? An ifconfig on the bridge6 interface shows the following spanning tree settings: priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp Do I really need spanning tree here? and

Re: 40G ixl nics

2019-02-04 Thread Tommy Nevtelen
On 03/02/2019 19.09, Tony Sarendal wrote: Good evening, We inserted a 2x40G NIC into one of our old franken-pc's, and got this: ixl0 at pci2 dev 0 function 0 "Intel XL710 QSFP+" rev 0x02: port 0, FW 5.0.40043 API 1.5, msi, address 0c:c4:7a:5e:f9:c8 ixl0: unable to query phy types ixl1 at pci2

Re: I am sorry

2019-02-04 Thread Daniel Jakots
On Mon, 4 Feb 2019 12:52:48 -0800, Chris Cappuccio wrote: > Leonid Bobrov [mazoc...@disroot.org] wrote: > > Hi, dear OpenBSD community. > > > > Please forgive me for drama I made earlier at mailing list and > > IRC channel. I am not a troll, I promise, I want to contribute to > > OpenBSD in any

Re: Modern CPUs AES-NI enabling system wide

2019-02-04 Thread Denis
Thank you for answers. As I understand you right amd64 kernel supports AES-NI for ipsec, softraid, and LibreSSL only. Right? Just wonder, how to check softraid discipline exactly utilizes AES-NI instruction set on amd64 machine? Softraid created bioctl -r 8192 (for test purposes) works

Re: Modern CPUs AES-NI enabling system wide

2019-02-04 Thread Theo de Raadt
Denis wrote: > Thank you for answers. > > As I understand you right amd64 kernel supports AES-NI for ipsec, > softraid, and LibreSSL only. Right? That word "only" what does it mean... AES-NI isn't used to blink the cursor? Please be careful of what you imply. > Just wonder, how to check