Re: athn0: device timeout with AR9271

Encountered the same errors with AR9271 dongle (athn driver) as in previous posts: athn0: firmware command 0x17 timed out athn0: firmware command 0x18 timed out athn0 device timeout Kernel determined it as: athn0 at uhub1 port 4 configuration 1 interface 0 "ATHEROS USB2.0 WLAN" rev 2.00/1.08

Re: OpenBSD !HTTPS websites - why?

Hello, > hosted on various machines run by different people. I'm not sure if > there's any viable way to handle keys and certificates for this type > of situation. -->> ### letsencrypt: Can one domain have multiple servers

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

On 2018/01/23 20:12, Denis wrote: > Running namecoind 13.2 for about two years. OpenBSD 6.1amd64 is the last > version which supports it. > > On 6.2 I stuck with malloc() hardening. With no any malloc.conf options > I have these errors: > > namecoind (4563) malloc():bogus pointer (double free?)

Re: Disable external USB devices

On 2018-01-23, Stefan Wollny wrote: > Hi there! This is a purely academical question out of curiosity: Is it > possible to disable all external USB interfaces without cutting the wire > on OpenBSD? You've heard stories of laptops/servers/routers with other > OSes being infected

Re: Disable external USB devices

Disable USB in "BIOS" ? 2018-01-25 1:42 GMT+03:00 Stuart Henderson : > On 2018-01-23, Stefan Wollny wrote: >> Hi there! This is a purely academical question out of curiosity: Is it >> possible to disable all external USB interfaces without cutting the wire

Re: Kernel panic with openbsd 6.2

On 2018-01-24, who one wrote: > Could it be related to: > https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/ No. > ? > >> Sent: Friday, January 19, 2018 at 9:50 PM >> From: "Mik J" >> To:

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

It is clear, but what do now when potentially 'buggy' software must work? There is no any transient period provided. ln - s 'j' /etc/malloc.conf partially resolves the problem with buggy namecoind memory management. Sometimes it runs without malloc() errors. Thanks On 1/25/2018 12:57 AM, Stuart

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

It is software you use. So take responsibility for it Picking on random people to solve your problem is insane > This is distributed DNS, so must work 24/7. It will be fixed soon. > > No complaints, no jumps at all. > > On 1/25/2018 9:34 AM, Theo de Raadt wrote: > > So fix it, or pay someone

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

Hopefully, we found the issue. It isn't an OS problem. Safety tips will be done. Thank you for your support. On 1/25/2018 9:43 AM, Theo de Raadt wrote: > It is software you use. > > So take responsibility for it > > Picking on random people to solve your problem is insane > >> This is

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

So fix it, or pay someone to fix it. Do you think your complaints should make people jump to attention? > It is clear, but what do now when potentially 'buggy' software must > work? There is no any transient period provided. > > ln - s 'j' /etc/malloc.conf partially resolves the problem with

Re: After 6.1amd64 -> 6.2amd64 upgrade namecoind malloc(): free(): error

This is distributed DNS, so must work 24/7. It will be fixed soon. No complaints, no jumps at all. On 1/25/2018 9:34 AM, Theo de Raadt wrote: > So fix it, or pay someone to fix it. > > Do you think your complaints should make people jump to attention? > >> It is clear, but what do now when

Re: Kernel panic with openbsd 6.2

On Mon, January 22, 2018 10:47 am, Mik J wrote: > Hello Stuart, > For me it takes just a few days... > I have a crash every 3/4 days maybe (2 crashes so far) and my server does > not handle load. > Yes I read your reports this morning, although you wrote that there was a > combination with snmpd,

Re: Disable external USB devices

oh and lastly to understand a bit more about why you don't need to be an ultrasmart blackhat: even USB keyboards are dangerous and lots of things can pretend to be usb https://www.youtube.com/watch?v=00A36VABIA4 and postscript: for a usb firewall, so to speak,

Re: iwm errors with new snapshot

Quoting Vijay Sankar : Quoting Stefan Sperling : On Tue, Jan 23, 2018 at 11:50:28AM -0600, Vijay Sankar wrote: Over the weekend, I was trying to do some tests requested in tech@ (inteldrm). I downloaded the latest snapshot but had problems with iwm

Re: font path ignorance

On 24.01.18 06:20, Ed Ahlsen-Girard wrote: > Built a new system, and it didn't have all the fonts that were on the > old one. I looked for msttcorefonts as a package, and didn't find it. So > I went through ports and found it, and some other font sets that I > remembered from before, make, make

Re: Disable external USB devices

Hi stefan, i asked this a bit ago (or similar) 1. https://usbguard.github.io/ 2. you can just disable USB ports or controller in BIOS, but that's not exciting at all. 3. this diff, which one person used once: Index: sys/dev/usb/uhub.c

Re: font path ignorance

On Wed, Jan 24, 2018 at 06:20:32AM -0600, Ed Ahlsen-Girard wrote: > Built a new system, and it didn't have all the fonts that were on the > old one. I looked for msttcorefonts as a package, and didn't find it. So > I went through ports and found it, and some other font sets that I > remembered

Re: [6.2] pf nat-to ignoring static-port?

I tried both (pass out quick right below nat-to line and also let it go to the end of my rulebase) and it didnt change anything. Martin On Tue, Jan 23, 2018 at 3:19 PM, Michael Price wrote: > The lack of a quick keyword on that line makes me wonder if you have a later >

Re: font path ignorance

Ed Ahlsen-Girard writes: > What have I missed? In my ~/.xinitrc I have: xset +fp /usr/local/share/fonts/mscorefonts,/usr/local/share/fonts/ghostscript,/usr/local/share/fonts/extra Regards, Allan

Re: Native C written i2pd port for OpenBSD

i2pd-2.17.0 port for OpenBSD 6.2amd64. i2pd runs under _i2pd:_i2pd user. Tested. Works smoothly. Simply untar to /usr/ports/net and run from i2pd dir: # make # make install # make clean Please include into ports collection. Thanks. Denis On 7/21/2016 9:16 PM, Rafael Sadowski wrote: > On Thu

Re: History documentation

Hey, strange, there is 5.3 in https://cloudflare.cdn.openbsd.org/pub/OpenBSD/doc/history/ is this still maintained? Many thanks. > Sent: Saturday, January 20, 2018 at 1:21 PM > From: mazocomp > To: misc@openbsd.org > Subject: History documentation > > Hi! > Both

font path ignorance

Built a new system, and it didn't have all the fonts that were on the old one. I looked for msttcorefonts as a package, and didn't find it. So I went through ports and found it, and some other font sets that I remembered from before, make, make build, make install. At the end of each make install

Re: History documentation

On Wed, Jan 24, 2018 at 12:22:18PM +0100, who one wrote: > Hey, strange, there is 5.3 in > https://cloudflare.cdn.openbsd.org/pub/OpenBSD/doc/history/ > > is this still maintained? > > Many thanks. > > > Sent: Saturday, January 20, 2018 at 1:21 PM > > From: mazocomp > >

Re: message authentication code incorrect

Hello Jan, See https://marc.info/?l=openbsd-cvs=151673244010209=2 and https://marc.info/?l=openbsd-cvs=151673766411788=2. So it's probably fixed in the next snapshot. On 01/24/18 14:08, Jan Stary wrote: > On Jan 23 16:48:57, h...@stare.cz wrote: >> I just upgraded my current/amd64 and now con't

Re: message authentication code incorrect

On Jan 23 16:48:57, h...@stare.cz wrote: > I just upgraded my current/amd64 and now con't ssh to it In fact, I can't ssh _fom_ it either: $ ssh wherever write: Socket is not connected has something changed with ssh or sshd? Jan > from an amd64 machine running the Jan 19 snapshot: > >

Re: message authentication code incorrect

On Jan 23 16:48:57, h...@stare.cz wrote: > I just upgraded my current/amd64 and now con't ssh to it /var/log/authlog says: Protocol major versions differ for 147.32.79.165 port 51692: SSH-2.0-OpenSSH_7.6 vs. SSH-2.0-OpenSSH-7.6 147.32.79.165 is a MacOS machine trying to connect The

Re: message authentication code incorrect

On Wed, Jan 24 2018, Jan Stary wrote: > On Jan 23 16:48:57, h...@stare.cz wrote: >> I just upgraded my current/amd64 and now con't ssh to it > > In fact, I can't ssh _fom_ it either: > > $ ssh wherever > write: Socket is not connected > > has something changed with ssh or sshd?

Re: Kernel panic with openbsd 6.2

Could it be related to: https://newsroom.intel.com/news/root-cause-of-reboot-issue-identified-updated-guidance-for-customers-and-partners/ ? > Sent: Friday, January 19, 2018 at 9:50 PM > From: "Mik J" > To: Misc > Subject: Kernel panic with openbsd 6.2 >

Re: History documentation

On 01/24/18 08:12, mazocomp wrote: > On Wed, Jan 24, 2018 at 12:22:18PM +0100, who one wrote: >> Hey, strange, there is 5.3 in >> https://cloudflare.cdn.openbsd.org/pub/OpenBSD/doc/history/ >> >> is this still maintained? >> >> Many thanks. >> >> > Sent: Saturday, January 20, 2018 at 1:21 PM

Re: message authentication code incorrect

On Jan 24 14:13:56, openbsd+m...@list.imperialat.at wrote: > Hello Jan, > > See https://marc.info/?l=openbsd-cvs=151673244010209=2 and > https://marc.info/?l=openbsd-cvs=151673766411788=2. > So it's probably fixed in the next snapshot. Yes it is. Thanks. Jan