Re: Firefox's trouble on snapshot #1960

> Firefox doesn't run on snapshot. [snip] Yes, there is an ABI/API/buildsystem transition under way. That's how we get from clip-clop-clip-clop to wroom-wroom.

Firefox's trouble on snapshot #1960

Hello misc@ Firefox doesn't run on snapshot. shupikov@balamut:~$ uname -a OpenBSD balamut.td.kms 5.9 GENERIC.MP#1960 amd64 shupikov@balamut:~$ firefox XPCOMGlueLoad error for file /usr/local/lib/firefox-45.0.1/libxul.so.63.0: Cannot load specified object Couldn't load XPCOM.

Gogs PostgreSQL

Hi Misc, Is anybody running Gogs https://gogs.io/ in production on OpenBSD using PostgreSQL as a backend. Any chance to share the installation/configuration notes with me? Predrag

Re: firefox and ssh(1) -D behaviour vs. localhost

Hello, In the options menu when you set the proxy address there is a field with addresses that should not use the proxy. From my memory, localhost is in it by default, you should remove it. Kind regards Le 24 mars 2016 23:03:58 GMT+01:00, Adam Thompson a écrit :

Re: Relayd TLS client mode CA verification

Maybe I will post example of what I am doing. OpenBSD-current amd64 March 16th, 2016. Getmail and imap over TLS. $ cat /etc/relayd.conf tcp protocol proto_wp { tls ca file "/etc/ssl/cert.pem" pass } relay connect_to_mail_wp { protocol proto_wp listen on

firefox and ssh(1) -D behaviour vs. localhost

When using "ssh -D" to establish a SOCKS-type proxy, I can specify the bind_address for the local end of the connection, but how do I control the bind address on the far end? I'm accustomed to using -D to remotely administer various web services that are behind a firewall/bastion-host instead

Re: HTTPS Only 3.1 (Detailed Analysis, Browser Security, Open Source, Python)

On Thu, 24 Mar 2016, Kevin Chadwick wrote: > BTW, only allowing Javascript to come from the primary domain over SSL > would be a far saner idea, but lets see you get that past Google, > facebook and all the other tracking sites? It's possible with content security

Re: HTTPS Only 3.1 (Detailed Analysis, Browser Security, Open Source, Python)

> Now, let's look at threats: > 1. Man in the middle - it's fixed. > 2. Phishing always requires the browser to load attacker's website, so it's > permanently dead here. > 3. Drive-by Download - dead(if applied strictly, unable to download the > executable) > 4. Clickjacking - dead(attacker's

Re: HTTPS Only 3.1 (Detailed Analysis, Browser Security, Open Source, Python)

> To secure browser which is very fragile, the approach of HTTPS Only 3.1 is > exceptionally simple: Please help make widespread browsers "Simple" firefox now takes > 200M mem without any tabs open and chrome is > 70M to download. Xombrero uses 30-45 M of mem > 1. Only HTTPS URLs(no other

Heads up: ART enabled in -current

I just enabled ART [0] in -current, it will be the default routing table backend in the next snapshots. The plan is to squash the possible regressions with this new routing table backend then when we're confident enough, take its route lookup out of the KERNEL_LOCK(). Yes, this is one of the big