Re: ASUS H97M-PLUS compat. question
> Van: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] Namens > Özgür Kazanççi > Verzonden: maandag 11 januari 2016 13:37 > Aan: misc@openbsd.org > Onderwerp: ASUS H97M-PLUS compat. question > > Greetings everyone. > > I'm planning to build a PC for Fileserver usage in a network. > The pc will run on OpenBSD 5.8. > > So for that need, I'd like to buy ASUS H97M-PLUS motherboard, it's > built on: > Intel?? H97 chipset > and it has a Intel?? I218V, 1 x Gigabit LAN NIC. > > Anyone ever tried this board with OpenBSD? > I'd like to know if there would be any compatibility (drivers?) > issue in OpenBSD. > > Thanks. I've run OpenBSD 5.7 and 5.8 on a Asus H97I-PLUS which is the mini-itx version of the same motherboard. It runs just fine, everything is detected. Gome 3.16 runs great with intel HD4600 gaphics. Tiemen Werkman
Re: chrome 68 and protonmail
> -Original Message- > From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf > Of vincent delft > Sent: Friday, September 14, 2018 7:39 AM > To: OpenBSD misc > Subject: chrome 68 and protonmail > > Hello, > > With the last version of Chrome (Chromium 68.0.3440.106) on -current, I > can > no more login in protonmail. > > In fact after the 2nd login screen chrome complains about an issue. > > By looking at the console, I see this message: > " > <--- Last few GCs ---> > > [13615:0x1b00ec7000]19499 ms: Scavenge 28.5 (34.8) -> 28.0 (34.8) > MB, > 0.7 / 0.0 ms (average mu = 1.000, current mu = 1.000) idle task > [13615:0x1b00ec7000]20552 ms: Scavenge 28.9 (34.8) -> 28.2 (34.8) > MB, > 4.9 / 0.2 ms (average mu = 1.000, current mu = 1.000) idle task > [13615:0x1b00ec7000]24816 ms: Scavenge 29.1 (34.8) -> 28.3 (33.8) > MB, > 2.2 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation > failure > > > <--- JS stacktrace ---> > > JS stack trace = > > 0: ExitFrame [pc: 0x30a55ec5c33d] > 1: InternalFrame [pc: 0x30a55ec1238c] > Security context: 0x2471c02cba29 https://mail.protonmail.com> > 2: new constructor(aka u) [0x6ed0e8a85b9] [ > https://mail.protonmail.com/openpgp.45fc464591fddb524fc0c8f83f781965944 > 76934.js:2] > [bytecode=0x23c4aa2110b1 offset=84](this=0x17ad66748f99 0xa7fcf3b2669>,e=0x17ad66748f41 ) > 3: ConstructFrame [pc: 0x3... > > " > > I've cleared cache, config, ... but the problem persist. > > Am I the only one having such problem ? > > Note: Firefox cannot work for protonmail because of javascript issue (I > do > not remember the exact problem). > Is there an another browser for protonmail ? > > regards Where is the latest version of chromium? I've just checked several mirrors and I can't seem to find it. Tiemen Werkman
Re: gnome crashes with current snapshot
> -Oorspronkelijk bericht- > Van: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] Namens > Tiemen Werkman > Verzonden: donderdag 4 februari 2016 17:49 > Aan: misc@openbsd.org > Onderwerp: gnome crashes with current snapshot > > >Synopsis:gnome crashes > >Environment: > System : OpenBSD 5.9 > Details : OpenBSD 5.9 (GENERIC.MP) #1868: Mon Feb 1 > 20:02:36 MST 2016 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.M > P > > Architecture: OpenBSD.amd64 > Machine : amd64 > >Description: > gnome crashes with the following error: > > "Oh no! Something has gone wrong. > A problem has occurred and the system can't recover. > please log out and try again." > > The only thing I've altered is to disable my ATI Radeon 270 > with the > following command: > # config -e -o /bsd /bsd > > disable radeondrm > > quit > # reboot > > The bios is set to use cpu graphics without multimonitor > support to > make sure that radeondrm isn't in some way interfering with > Xorg. > > I first installed snapshot version #1866 and updated each time > there > was a newer version. The current version I am running is #1868. > I've also tried it with and without uefi, but that didn't make > a > difference. UEFI runs fine btw. > > I've added the dmesg using sendbug run as root and Xorg.0.log > below. > > If somebody could help me out I would appreciate it. > If you need more information please let me know, I would be > happy to > provide anything you need. > I've been looking through all settings today and I finally made it work. The problem was the machdep.allowaperture was set to 2 in /etc/sysctl.conf. I commented out the line (the only line in sysctl.conf) and gnome started up without a hitch. I didn't create the sysctl.conf file, it was generated by the installer. I think the question about running X answered yes creates it. Anyway I'm happy everything works, I thought I'd let others know Tiemen Werkman
Re: OwnCloud - security/setup warnings etc.. Any help/advice would be massively appreciated.
> -Oorspronkelijk bericht- > Van: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] Namens > Antoine Jacoutot > Verzonden: maandag 18 april 2016 18:45 > Aan: Nick > CC: misc@openbsd.org > Onderwerp: Re: OwnCloud - security/setup warnings etc.. Any > help/advice would be massively appreciated. > > On Mon, Apr 18, 2016 at 11:32:32AM -0400, Nick wrote: > > ## I think this error can be safely ignored, is that correct? > OpenBSD > > changed the way environment variables are handled.. (?) 1. php > does not seem to be setup properly to query system environment > variables. The test with getenv("PATH") only returns an empty > response. > > > > ## This I'm not sure of, is it to do with the server needing > access to /etc/hosts and /etc/resolv? Would you recommend it? > > 2. This server has no working Internet connection. This means > that > > some of the features like mounting external storage, > notifications > > about updates or installation of third-party apps will not work. > Accessing files remotely and sending of notification emails might > not work, either. We suggest to enable Internet connection for this > server if you want to have all features. > > > > ## Is it safe to allow this to be readable by PHP? If so, what do > you think might be the best way to go about it? > > 3. /dev/urandom is not readable by PHP which is highly > discouraged for security reasons. Further information can be found > in our > [documentation](https://doc.owncloud.org/server/8.2/go.php?to=admin > -security). > > > > ## I have already set the server to direct to HTTPS using the > letsencrypt certs I created, so I figure that this is unnecessary > to change - would you agree? > > 4. The "Strict-Transport-Security" HTTP header is not configured > to least "15768000" seconds. For enhanced security we recommend > enabling HSTS as described in our [security > tips](https://nofacade.co.uk/owncloud/index.php/settings/admin#admi > n-tips). > > > > ## This one is a real pain to work out: > > 5. No memory cache has been configured. To enhance your > performance please configure a memcache if available. Further > information can be found in our > [documentation](https://doc.owncloud.org/server/8.2/go.php?to=admin > -performance). > > > > ## Reading through /usr/local/share/doc/pkg-readmes/owncloud- > 8.2.2p3 - it advises me to adapt and append the > ownloud/config/config.php file with: > > 'memcache.local' => '\OC\Memcache\Redis', 'redis' => array( > 'host' => > > 'localhost', 'port' => 6379, 'timeout' => 0.0, ), Problem is that > > after a server restart, I am blocked from accessing my owncloud > server. Until I remove the recommended code and restart. > > > > Here's what I have tried and which hasn't worked for me: > > ln -sf /etc/php-5.6.sample/redis.ini /etc/php-5.6/ > > That is documented. > > > pkg_add redis && rcctl enable redis && rcctl start redis > > I though it was kind of obvious that if you wanted redis support, > you should have a redis server... > Also it does not need to be on the same box. > > > rcctl restart httpd > > rcctl restart php56_fpm -df > > > > > > Thanks for taking the time to look through this. Cheers > > > > -- > Antoine For anyone interested, I just wrote this install guide for myself last week. It removes all the errors from owncloud except the urandom error. Tiemen Werkman # Owncloud Setup ### requirements - ssl certificates - database - php - owncloud - httpd - redis ### create self-signed ssl certificate and private key for owncloud see _create certificates.md_ ### install postgresql database server see _postgresql setup.md_ ### install phpPgAdmin see _phpPgAdmin setup.md_ ### install owncloud and php PostgreSQL drivers `$ pkg_add -iv owncloud php-pdo_pgsql redis` When promted, pick the latest version of php. After the installation has finished, create the symlinks as shown by `pkg_add`. Also check the pkg-readmes Open _php-fpm.conf_ and change the following lines: ;env[PATH] = /usr/local/bin:/usr/bin:/bin env[PATH] = /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:sbin ;pm.max_children = 5 pm.max_children = 10 Open `/var/www/owncloud/config/config.php` and add the following: 'datadirectory' => '/owncloud/data', 'updatechecker' => false, 'log_type' => 'syslog', 'syslog_tag' => 'owncloud', 'logfile' => '/var/log/owncloud', 'loglevel' =>