OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[Martin]

I'm looking for relatively cheap VPS with OpenBSD installation support and with 
~1Tb of unfiltered traffic. In any words all in/out VPS ports must be opened by 
default.
Any recommendations?

Martin.

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[Dumitru Moldovan]

On Fri, Apr 10, 2020 at 09:51:41AM +, Martin wrote:

I'm looking for relatively cheap VPS with OpenBSD installation support and with 
~1Tb of unfiltered traffic. In any words all in/out VPS ports must be opened by 
default.
Any recommendations?


Vultr is close to that.  Last time I created a new VPS with them, I
think they filtered port 25, but it was no big deal to get rid of that.

Still running 2 productions VMs on Vultr, they are cheap, have great
support, and reasonable uptimes.  Not OpenBSD-based unfortunately, even
though they support it officially.

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[Martin]

I know about vultr, but they are filtering 25, 465 for sure and some other 
ports. Especially, I need 25 port open for mail server I'm going to implement.

I mostly interesting in a small hoster with soft customer policies for long 
term OpenBSD VPS hosting. It can be any ISP based VPS hoster or any.

Martin

‐‐‐ Original Message ‐‐‐
On Friday, April 10, 2020 10:59 AM, Dumitru Moldovan  wrote:

> On Fri, Apr 10, 2020 at 09:51:41AM +, Martin wrote:
>
> > I'm looking for relatively cheap VPS with OpenBSD installation support and 
> > with ~1Tb of unfiltered traffic. In any words all in/out VPS ports must be 
> > opened by default.
> > Any recommendations?
>
> Vultr is close to that. Last time I created a new VPS with them, I
> think they filtered port 25, but it was no big deal to get rid of that.
>
> Still running 2 productions VMs on Vultr, they are cheap, have great
> support, and reasonable uptimes. Not OpenBSD-based unfortunately, even
> though they support it officially.

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[Peter Nicolai Mathias Hansteen]

> 10. apr. 2020 kl. 11:51 skrev Martin :
> 
> I'm looking for relatively cheap VPS with OpenBSD installation support and 
> with ~1Tb of unfiltered traffic. In any words all in/out VPS ports must be 
> opened by default.
> Any recommendations?

I would personally recommend the place where bsdly.net  
lives — Terrahost (https://terrahost.no ), which offers 
a range of options from minimal KVM based VMs through dedicated physical 
servers, with unfiltered connectivity and your choice of OS.

They’re based in Norway (Sandefjord to be exact) so likely not the cheapest 
you’ll find but they have been most excellent and very responsive when I needed 
to get things done quickly a couple of years back.

All the best,
Peter


—
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.






signature.asc
Description: Message signed with OpenPGP

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[mabi]

‐‐‐ Original Message ‐‐‐
On Friday, April 10, 2020 12:59 PM, Dumitru Moldovan  wrote:


> Vultr is close to that. Last time I created a new VPS with them, I
> think they filtered port 25, but it was no big deal to get rid of that.
>
> Still running 2 productions VMs on Vultr, they are cheap, have great
> support, and reasonable uptimes. Not OpenBSD-based unfortunately, even
> though they support it officially.

Here https://oriented.net/server/openbsd-virtual-machine they provide OpenBSD 
native VPS and traffic seems to be unlimited/unfiltered.

why the c99 mandate?

[Mayuresh Kathe]

i am not a c hotshot, so pardon my ignorance.
i read that all new code under openbsd has to be c99.
may i know what's so special about c99 over c89 which has been under heavy
use for so long?
also, does the mandate hold true for modifications to old (c89) code?
thank you.

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[Oliver Leaver-Smith]

I run a few OpenBSD servers on vultr. They block outbound 25 by default like 
most providers, but as long as you say you aren’t going to spam, they open it 
for you no problem. 1000GB bandwidth on smaller VPS, 6000 on larger ones

-ols
--
Oliver Leaver-Smith
+44(0)114 360 1337
TZ=Europe/London

> On 10 Apr 2020, at 10:52, Martin  wrote:
> 
> I'm looking for relatively cheap VPS with OpenBSD installation support and 
> with ~1Tb of unfiltered traffic. In any words all in/out VPS ports must be 
> opened by default.
> Any recommendations?
> 
> Martin.

i386 kernel relinking

[Nick Holland]

Question about kernel randomization and relinking...

It seems to take a fair amount of RAM, at least for systems that
are forced to run i386.  And I mean real RAM -- swap doesn't seem
to cut it.  

I discovered that several machines I was intending on using for
minimal purposes just couldn't complete relinking.  So I built a
VM and started playing with the RAM.

Built with 1G RAM, default was a 1.2G swap, worked fine.
Reduced to 256MB RAM, Kernel failed to relink.  As with my old
junk.

The magic number seemed to be between 320MB (failed) and 384MB 
(worked) of RAM.  Ok, fine.  

Kernel relinking is important, I get that.  Probably time to
start tossing old junk.  I get that, too.  I'm not complaining
about the forcible retirement of some of my old junk.  I'm just
curious why swap didn't "fix" this problem.

But that VM failed at 320MB RAM, even though it had 1.2G of swap,
mostly unused (MOSTLY.  Yes, it was going into swap).  Is there a
semi-layperson's explanation of this?  Or is this a "if you got
to ask, you won't understand" kind of thing?

And here's the relink log from my VM, but the ones from my physical
boxes looked pretty similiar.

$ cat relink.log   
(SHA256) /bsd: OK
LD="ld" LDFLAGS="-g" sh makegap.sh 0x gapdummy.o
ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o ${OBJS}
textdatabss dec hex
0   0   0   0   0
mv newbsd newbsd.gdb
ctfstrip -S -o newbsd newbsd.gdb
strip: there are no sections to be copied!
rm -f bsd.gdb
mv -f newbsd bsd
mv: newbsd: No such file or directory
*** Error 1 in /usr/share/relink/kernel/GENERIC.MP (Makefile:1131 'newbsd')

I also found that a 320MB machine could not build the kernel from scratch.
Nothing used much memory until the ld step, which started using large amounts
of memory and some swap, and errored out the same way:

LD="ld" LDFLAGS="-g" sh makegap.sh 0x gapdummy.o
ld -T ld.script -X --warn-common -nopie -o bsd ${SYSTEM_HEAD} vers.o ${OBJS}
textdatabss dec hex
0   0   0   0   0
mv bsd bsd.gdb
ctfstrip -S -o bsd bsd.gdb
strip: there are no sections to be copied!

Thanks!

Nick.

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

[ceidem]

I'm using Vultr to host my mail server. All it requires is a note to support 
asking all mail ports be opened and they will comply. $5 US a month and they 
support OpenBSD.

You could also look into https://openbsd.amsterdam/ for your hosting needs. 
They seem to be just what you are looking for.

 - chris

On April 10, 2020 6:23:03 AM CDT, Martin  wrote:
>I know about vultr, but they are filtering 25, 465 for sure and some
>other ports. Especially, I need 25 port open for mail server I'm going
>to implement.
>
>I mostly interesting in a small hoster with soft customer policies for
>long term OpenBSD VPS hosting. It can be any ISP based VPS hoster or
>any.
>
>Martin
>
>‐‐‐ Original Message ‐‐‐
>On Friday, April 10, 2020 10:59 AM, Dumitru Moldovan 
>wrote:
>
>> On Fri, Apr 10, 2020 at 09:51:41AM +, Martin wrote:
>>
>> > I'm looking for relatively cheap VPS with OpenBSD installation
>support and with ~1Tb of unfiltered traffic. In any words all in/out
>VPS ports must be opened by default.
>> > Any recommendations?
>>
>> Vultr is close to that. Last time I created a new VPS with them, I
>> think they filtered port 25, but it was no big deal to get rid of
>that.
>>
>> Still running 2 productions VMs on Vultr, they are cheap, have great
>> support, and reasonable uptimes. Not OpenBSD-based unfortunately,
>even
>> though they support it officially.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: i386 kernel relinking

[Stefan Sperling]

On Fri, Apr 10, 2020 at 09:35:16AM -0400, Nick Holland wrote:
> Question about kernel randomization and relinking...
> 
> It seems to take a fair amount of RAM, at least for systems that
> are forced to run i386.  And I mean real RAM -- swap doesn't seem
> to cut it.  
> 
> I discovered that several machines I was intending on using for
> minimal purposes just couldn't complete relinking.  So I built a
> VM and started playing with the RAM.
> 
> Built with 1G RAM, default was a 1.2G swap, worked fine.
> Reduced to 256MB RAM, Kernel failed to relink.  As with my old
> junk.
>
> The magic number seemed to be between 320MB (failed) and 384MB 
> (worked) of RAM.  Ok, fine.  

FWIW, my soekris net5501 with 256MB of RAM and 512MB swap does manage
to relink a kernel (on 6.6 + syspatches).

# ls -l relink.log
-rw-r--r--  1 root  wheel  -  507B Apr 10 13:33 relink.log
# cat relink.log   
(SHA256) /bsd: OK
LD="ld" LDFLAGS="-g" sh makegap.sh 0x gapdummy.o
ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o ${OBJS}
textdatabss dec hex
11815507267748  1101824 13185079c93037
mv newbsd newbsd.gdb
ctfstrip -S -o newbsd newbsd.gdb
rm -f bsd.gdb
mv -f newbsd bsd
install -F -m 700 bsd /bsd && sha256 -h /var/db/kernel.SHA256 /bsd

Kernel has been relinked and is active on next reboot.

SHA256 (/bsd) = a940ce989d708e5b87a1186ee81bd624066baeabe67b8405b52e4fa2988b565


# dislabel -pm wd0
#size   offset  fstype [fsize bsize   cpg]
  a:   353.0M   64  4.2BSD   2048 16384  5624 # /
  b:   511.1M   722944swap# none
  c: 15280.0M0  unused
  d:   444.8M  1769728  4.2BSD   2048 16384  7116 # /tmp
  e:   607.7M  2680576  4.2BSD   2048 16384  9685 # /var
  f:  1703.0M  3925216  4.2BSD   2048 16384 12958 # /usr
  g:   505.8M  7412896  4.2BSD   2048 16384  8060 # /usr/X11R6
  h:  1632.9M  8448736  4.2BSD   2048 16384 12958 # /usr/local
  i:  1381.2M 11792960  4.2BSD   2048 16384 12958 # /usr/src
  j:  5282.4M 14621632  4.2BSD   2048 16384 12958 # /usr/obj
  k:  2850.9M 25439936  4.2BSD   2048 16384 12958 # /home

Re: why the c99 mandate?

[Marc Espie]

On Fri, Apr 10, 2020 at 11:55:00AM +, Mayuresh Kathe wrote:
> i am not a c hotshot, so pardon my ignorance.
> i read that all new code under openbsd has to be c99.
> may i know what's so special about c99 over c89 which has been under heavy
> use for so long?

Like duh, ISO-C99 bis mostly improvements on ISO-C90.  And it's fully 
supported now.  Why not use it ?

Pre-C90 C has also been under heavy use, but most people were very happy
to get rid of it.

I would recommend reading the C standards, looking at what changed between
K&R/C90/C99, and making your own *informed* opinion.

As for C99, huge improvements in built-in types immediately comes to mind.

Smart initializers as well...

Re: i386 kernel relinking

[Nick Holland]

On 2020-04-10 10:10, Stefan Sperling wrote:
> On Fri, Apr 10, 2020 at 09:35:16AM -0400, Nick Holland wrote:
>> Question about kernel randomization and relinking...
>> 
>> It seems to take a fair amount of RAM, at least for systems that
>> are forced to run i386.  And I mean real RAM -- swap doesn't seem
>> to cut it.  
>> 
>> I discovered that several machines I was intending on using for
>> minimal purposes just couldn't complete relinking.  So I built a
>> VM and started playing with the RAM.
>> 
>> Built with 1G RAM, default was a 1.2G swap, worked fine.
>> Reduced to 256MB RAM, Kernel failed to relink.  As with my old
>> junk.
>>
>> The magic number seemed to be between 320MB (failed) and 384MB 
>> (worked) of RAM.  Ok, fine.  
> 
> FWIW, my soekris net5501 with 256MB of RAM and 512MB swap does manage
> to relink a kernel (on 6.6 + syspatches).

Whoops.  Guess I should have mentioned, that was -current, as of
yesterday 
OpenBSD 6.7-beta (GENERIC.MP) #110: Thu Apr  9 01:20:52 MDT 2020
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
real mem  = 334970880 (319MB)
avail mem = 313077760 (298MB)

and probably a couple weeks ago for the real (old) hw.

I'm curious if your Soekris can handle 6.7-beta.

Nick.


> 
> # ls -l relink.log
> -rw-r--r--  1 root  wheel  -  507B Apr 10 13:33 relink.log
> # cat relink.log   
> (SHA256) /bsd: OK
> LD="ld" LDFLAGS="-g" sh makegap.sh 0x gapdummy.o
> ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o 
> ${OBJS}
> textdatabss dec hex
> 11815507267748  1101824 13185079c93037
> mv newbsd newbsd.gdb
> ctfstrip -S -o newbsd newbsd.gdb
> rm -f bsd.gdb
> mv -f newbsd bsd
> install -F -m 700 bsd /bsd && sha256 -h /var/db/kernel.SHA256 /bsd
> 
> Kernel has been relinked and is active on next reboot.
> 
> SHA256 (/bsd) = 
> a940ce989d708e5b87a1186ee81bd624066baeabe67b8405b52e4fa2988b565
> 
> 
> # dislabel -pm wd0
> #size   offset  fstype [fsize bsize   cpg]
>   a:   353.0M   64  4.2BSD   2048 16384  5624 # /
>   b:   511.1M   722944swap# none
>   c: 15280.0M0  unused
>   d:   444.8M  1769728  4.2BSD   2048 16384  7116 # /tmp
>   e:   607.7M  2680576  4.2BSD   2048 16384  9685 # /var
>   f:  1703.0M  3925216  4.2BSD   2048 16384 12958 # /usr
>   g:   505.8M  7412896  4.2BSD   2048 16384  8060 # /usr/X11R6
>   h:  1632.9M  8448736  4.2BSD   2048 16384 12958 # /usr/local
>   i:  1381.2M 11792960  4.2BSD   2048 16384 12958 # /usr/src
>   j:  5282.4M 14621632  4.2BSD   2048 16384 12958 # /usr/obj
>   k:  2850.9M 25439936  4.2BSD   2048 16384 12958 # /home
> 

strncasecmp

[Roderick]

From the man page:


"
These functions compare the NUL-terminated strings s1 and s2 and
return an [...].

strncasecmp() and strncasecmp_l() compare at most len characters.
"

Why NULL-terminated when comparing at most len characters?!

Rod.

Re: strncasecmp

[Theo de Raadt]

Because either string could be shorter than len.

 strncasecmp() and strncasecmp_l() compare at most len characters.
   ^^^

"NUL-terminated string" is firmly explaining to people that in C,
a string is only a string if it ends in a NUL.  There's a large
contingent of folk who don't get it. 

Roderick  wrote:

> 
> 
> From the man page:
> 
> "
> These functions compare the NUL-terminated strings s1 and s2 and
> return an [...].
> 
> strncasecmp() and strncasecmp_l() compare at most len characters.
> "
> 
> Why NULL-terminated when comparing at most len characters?!
> 
> Rod.
> 

RE: strncasecmp

[zeurkous]

theo wrote:
> Because either string could be shorter than len.
>
>  strncasecmp() and strncasecmp_l() compare at most len characters.
>  ^^^
>
> "NUL-terminated string" is firmly explaining to people that in C,
> a string is only a string if it ends in a NUL. There's a large
> contingent of folk who don't get it.

As an example of what happens when folks don't get it: [0].

In general, me'd strongly suggest that we speak of an 'array' when it's
not zero-terminated (that again should be redundant information here,
but yeah).

Baai,

--zeurkous.

[0] 'https://doomwiki.org/wiki/Absurd texture name in error message'

-- 
Friggin' Machines!

Re: news from my hacked box

[Rudolf Leitgeb]

> Yes could be, he has a "social engineering" approach to people. He places 
> people and
> himself on the same level of machines. Then he searches vulnerability on 
> persons.
> He makes extensive use of corruption to take advantage on his personal war. 
> From this
> point of view also a vpn provider could be very vulnerable because as many 
> people know
> vpn providers are not big rich companies.

You would use a VPN to escape the claws of your own government, but not the 
claws of
some corrupt individual in your country. Therefore I see no reason, why you 
would use
a VPN, and its required software to use it would just increase your attack 
surface.

> About authorities it would be my next step when I'll find proofs of what I'm 
> saying.
> Because as you saw the first thing they think it will be "this guy is 
> paranoid".

That's the great benefit of virtual machines with snap shoting: unless the 
"evil hackers"
can not only control your running system, but can also break through the 
boundaries set
by your virtual machine, you have reasonable ways to collect evidence. Just 
create snaps
whenever your system feels strange, and you can inspect these snapshots at a 
later, more
convenient moment. You can also perform comparisons between snap shots.

> Yes I thought to try to use vm on linux, but you know the linux kernel is 
> hole with some
> code around.

Yes, they say all kinds of nasty stuff about linux, but overall it works well, 
and the
vast majority of public facing servers run linux.

Your best bet will probably be some kind of variety of systems: linux, windows, 
freebsd,
maybe throw some openbsd into the pool. if "evil hackers" have to check your 
system first,
and probably throw some non-working exploits at it before breaking through, 
then you have
a good chance of catching them in the act. make your setup as unpredictable as 
you can,
and "they" will leave undeniable traces.

Once you have these traces, you can probably learn more about the hacker's 
methods and
develop a strategy to get rid of them for good.

PS: It would probably attract more helpful talent here, if people had reason to 
assume,
that your efforts serve some common goal and are not some private quest for 
free security
consulting. Care to share, why you think your computers are under attack?

Re: i386 kernel relinking

[Theo de Raadt]

I am succesfully relinking kernels on a landisk with 128MB of ram.

I think this conversation is ridiculous:

If a machine is too small, then it is too small.  Do I have to paypal
a $0.05 to some users?

Nick Holland  wrote:

> 
> 
> 
> On 2020-04-10 10:10, Stefan Sperling wrote:
> > On Fri, Apr 10, 2020 at 09:35:16AM -0400, Nick Holland wrote:
> >> Question about kernel randomization and relinking...
> >> 
> >> It seems to take a fair amount of RAM, at least for systems that
> >> are forced to run i386.  And I mean real RAM -- swap doesn't seem
> >> to cut it.  
> >> 
> >> I discovered that several machines I was intending on using for
> >> minimal purposes just couldn't complete relinking.  So I built a
> >> VM and started playing with the RAM.
> >> 
> >> Built with 1G RAM, default was a 1.2G swap, worked fine.
> >> Reduced to 256MB RAM, Kernel failed to relink.  As with my old
> >> junk.
> >>
> >> The magic number seemed to be between 320MB (failed) and 384MB 
> >> (worked) of RAM.  Ok, fine.  
> > 
> > FWIW, my soekris net5501 with 256MB of RAM and 512MB swap does manage
> > to relink a kernel (on 6.6 + syspatches).
> 
> Whoops.  Guess I should have mentioned, that was -current, as of
> yesterday 
> OpenBSD 6.7-beta (GENERIC.MP) #110: Thu Apr  9 01:20:52 MDT 2020
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> real mem  = 334970880 (319MB)
> avail mem = 313077760 (298MB)
> 
> and probably a couple weeks ago for the real (old) hw.
> 
> I'm curious if your Soekris can handle 6.7-beta.
> 
> Nick.
> 
> 
> > 
> > # ls -l relink.log
> > -rw-r--r--  1 root  wheel  -  507B Apr 10 13:33 relink.log
> > # cat relink.log   
> > (SHA256) /bsd: OK
> > LD="ld" LDFLAGS="-g" sh makegap.sh 0x gapdummy.o
> > ld -T ld.script -X --warn-common -nopie -o newbsd ${SYSTEM_HEAD} vers.o 
> > ${OBJS}
> > textdatabss dec hex
> > 11815507267748  1101824 13185079c93037
> > mv newbsd newbsd.gdb
> > ctfstrip -S -o newbsd newbsd.gdb
> > rm -f bsd.gdb
> > mv -f newbsd bsd
> > install -F -m 700 bsd /bsd && sha256 -h /var/db/kernel.SHA256 /bsd
> > 
> > Kernel has been relinked and is active on next reboot.
> > 
> > SHA256 (/bsd) = 
> > a940ce989d708e5b87a1186ee81bd624066baeabe67b8405b52e4fa2988b565
> > 
> > 
> > # dislabel -pm wd0
> > #size   offset  fstype [fsize bsize   cpg]
> >   a:   353.0M   64  4.2BSD   2048 16384  5624 # /
> >   b:   511.1M   722944swap# none
> >   c: 15280.0M0  unused
> >   d:   444.8M  1769728  4.2BSD   2048 16384  7116 # /tmp
> >   e:   607.7M  2680576  4.2BSD   2048 16384  9685 # /var
> >   f:  1703.0M  3925216  4.2BSD   2048 16384 12958 # /usr
> >   g:   505.8M  7412896  4.2BSD   2048 16384  8060 # 
> > /usr/X11R6
> >   h:  1632.9M  8448736  4.2BSD   2048 16384 12958 # 
> > /usr/local
> >   i:  1381.2M 11792960  4.2BSD   2048 16384 12958 # /usr/src
> >   j:  5282.4M 14621632  4.2BSD   2048 16384 12958 # /usr/obj
> >   k:  2850.9M 25439936  4.2BSD   2048 16384 12958 # /home
> > 
> 

Openbsd mirrors in Kazakhstan?

[Никита Степанов]

Openbsd mirrors in Kazakhstan?

Re: strncasecmp

[Roderick]

On Fri, 10 Apr 2020, Theo de Raadt wrote:


Because either string could be shorter than len.


Thanks. I get it. :) My non-strings do not have a '\0' in the
first len bytes and I need a case insensitive comparison.
Of course I could ignore strncasecmp and use tolower() to write
the trivial function, ...


"NUL-terminated string" is firmly explaining to people that in C,
a string is only a string if it ends in a NUL.  There's a large
contingent of folk who don't get it.


The word "string" is also found in the man pages of bcmp and memcmp.
Wrote by that large contingent?

Rod.

RE: strncasecmp

[zeurkous]

"Roderick"  wrote:
>
> On Fri, 10 Apr 2020, Theo de Raadt wrote:
>
>> Because either string could be shorter than len.
>
> Thanks. I get it. :) My non-strings do not have a '\0' in the
> first len bytes and I need a case insensitive comparison.
> Of course I could ignore strncasecmp and use tolower() to write
> the trivial function, ...

UNIX, in its current form, is just messy like that...

>> "NUL-terminated string" is firmly explaining to people that in C,
>> a string is only a string if it ends in a NUL. There's a large
>> contingent of folk who don't get it.
>
> The word "string" is also found in the man pages of bcmp and memcmp.
> Wrote by that large contingent?

Hysterical confusion (akin to the 'tty' confusion: terminal or simple
serial port?). They would better be changed to speak of arrays.

> Rod.

Baai,

--zeurkous.

-- 
Friggin' Machines!

Openbsd mirrors in Kazakhstan?

[Nikita Stepanov]

Openbsd mirrors in Kazakhstan?

Nvidia driver for OpenBSD?

[Nikita Stepanov]

on "underpowered" machines (was: Re: i386 kernel relinking)

[zeurkous]

theo wrote:
> I think this conversation is ridiculous:
>
> If a machine is too small, then it is too small. Do I have to paypal
> a $0.05 to some users?

Yes, me! Pretty please? *kitty eyes*

Seriously: sometimes, a machine is perfectly adequate, except for one
task that eats disproportionate amounts of resources. Questioning the
apropriateness of that task would seem to be a reasonable step to
undertake, before running to the store waving your credit card (not to
speak of the waste problem). 

Apart from the fact that many people on this planet *are*
really-terribly-out-of-pocket, there are still other issues than money. 

   --zeurkous.

-- 
Friggin' Machines!

RE: strncasecmp

[zeurkous]

Haai,

> From the man page:
>
> "
> These functions compare the NUL-terminated strings s1 and s2 and
> return an [...].
>
> strncasecmp() and strncasecmp_l() compare at most len characters.
> "
>
> Why NULL-terminated when comparing at most len characters?!

Since, by design, one's not supposed to be aware of the actual length of
the string, only of the buffer containing it (if that).

The 'NUL' vs 'NULL' can be confusing; indeed, mealways describes such
strings as 'zero-terminated' in nnx (exactly what that means is
described in a manual page for the type).

Though nnx tends to use bounded arrays { char *a, *e; bool v; } instead
(this has the pleasant side effect that a 0 may occour inside a string,
and the seperate 'bool v' allows for use of the complete address space,
NULL included).

(Here, me's using the nnx stuff as a vehicle to point out design
problems in UNIX: as always, YMMV, and no ad intended).

> Rod.

Hope the above has enlightened,

--zeurkous.

P.S.: Please don't address misc@ blindly: instead, address it in 'To:'
  or 'Cc:'.

-- 
Friggin' Machines!

Re: Nvidia driver for OpenBSD?

[Christopher Turkel]

None exist or are likely to ever exist.

On Friday, April 10, 2020, Nikita Stepanov 
wrote:

>

Re: Openbsd mirrors in Kazakhstan?

[j3s]

On 4/10/20 12:11 PM, Nikita Stepanov wrote:

Openbsd mirrors in Kazakhstan?


https://www.openbsd.org/ftp.html


doesn't look like it, you may be able to find one somewhat close though.

Openbsd supports pae?

[Nikita Stepanov]

Re: OpenBSD VPS hoster with unlimited/limited nonfiltered traffic

Another one is the "transip.eu" from Netherlands. Native OpenBSD support,
tcp 25 blocked by default but you can change it whenever you want. KVM
based.

On Fri, Apr 10, 2020, 17:04  wrote:

> I'm using Vultr to host my mail server. All it requires is a note to
> support asking all mail ports be opened and they will comply. $5 US a month
> and they support OpenBSD.
>
> You could also look into https://openbsd.amsterdam/ for your hosting
> needs. They seem to be just what you are looking for.
>
>  - chris
>
> On April 10, 2020 6:23:03 AM CDT, Martin  wrote:
> >I know about vultr, but they are filtering 25, 465 for sure and some
> >other ports. Especially, I need 25 port open for mail server I'm going
> >to implement.
> >
> >I mostly interesting in a small hoster with soft customer policies for
> >long term OpenBSD VPS hosting. It can be any ISP based VPS hoster or
> >any.
> >
> >Martin
> >
> >‐‐‐ Original Message ‐‐‐
> >On Friday, April 10, 2020 10:59 AM, Dumitru Moldovan 
> >wrote:
> >
> >> On Fri, Apr 10, 2020 at 09:51:41AM +, Martin wrote:
> >>
> >> > I'm looking for relatively cheap VPS with OpenBSD installation
> >support and with ~1Tb of unfiltered traffic. In any words all in/out
> >VPS ports must be opened by default.
> >> > Any recommendations?
> >>
> >> Vultr is close to that. Last time I created a new VPS with them, I
> >> think they filtered port 25, but it was no big deal to get rid of
> >that.
> >>
> >> Still running 2 productions VMs on Vultr, they are cheap, have great
> >> support, and reasonable uptimes. Not OpenBSD-based unfortunately,
> >even
> >> though they support it officially.
>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>

Re: Openbsd mirrors in Kazakhstan?

[Jordan Geoghegan]

On 2020-04-10 10:11, Nikita Stepanov wrote:

Openbsd mirrors in Kazakhstan?


The Russian mirror is hosted by Yandex. Moscow is likely the closest 
mirror to Kazakhstan, otherwise I would recommend trying one of the CDN 
options

Re: Nvidia driver for OpenBSD?

[Ingo Schwarze]

Hi,

Christopher Turkel wrote on Fri, Apr 10, 2020 at 02:49:56PM -0400:
> On Friday, April 10, 2020, Nikita Stepanov wrote:

>> Subject: Nvidia driver for OpenBSD?

> None exist or are likely to ever exist.

The question from the original poster was so imprecise and lazy
that no one else bothered to answer, but your answer is just plain
wrong, so it has to be corrected.

Here is a better answer, and even that is likely incomplete:

  https://man.openbsd.org/?query=nvidia&apropos=1

That said, OpenBSD developers typically strongly discourage buying
NVIDIA graphics cards because NVIDIA traditionally doesn't provide
hardware documentation for the graphics cards they produce, so
drivers for NVIDIA graphics cards are typically of vastly lower
quality than for intel(4) and radeon(4) cards.  In particular - but
that's far from the only problem as far as i heard - there is no
drm(4) support for NVIDIA cards.

Yours,
  Ingo

Re: Nvidia driver for OpenBSD?

[Nikita Stepanov]

I found� https://man.openbsd.org/man4/nv.4

0:49, 11 апреля 2020 г., Christopher Turkel
:

  None exist or are likely to ever exist.� 

  On Friday, April 10, 2020, Nikita Stepanov 
  wrote:



--
Отправлено из мобильного приложения
Яндекс.Почты

RE: Nvidia driver for OpenBSD?

[zeurkous]

"Nikita Stepanov"  wrote:
> I found https://man.openbsd.org/man4/nv.4

Then WTH did you ask?

Nevermind; n00bs gonna n00b, meguesses.

--zeurkous.

-- 
Friggin' Machines.

Re: Openbsd supports pae?

[Stuart Henderson]

On 2020-04-10, Nikita Stepanov  wrote:
>
>

It does, it's used for the NX bit for userland and kernel W^X.
But your question is not precise - if you mean "does OpenBSD support
RAM above 4GB on i386" the answer is no.

Re: Openbsd supports pae?

[Nikita Stepanov]

Why?

1:34, 11 апреля 2020 г., Nikita Stepanov
:

RE: Openbsd supports pae?

[zeurkous]

"Nikita Stepanov" 
> Why?

'Cause the sun went dry, and the flowers said "bye".

Nasty of them, isn't it?

--zeur.

> 1:34, 11 aprelya 2020 g., Nikita Stepanov
> :

-- 
Friggin' Machines!

Apr 9 snapshot bsd.mp fails on VMware

[j]

Upgrading from a 3-month old snapshot.  Files from cdn.openbsd.org.

Upon boot in a VMware VM, it loads the kernel then fails to even
show the OpenBSD banner.  After OpenBSD/amd64 BOOT 3.47 banner, booting
hd0a:/bsd: etc etc, then VMware reports an error.  "A fault has
occurred causing a virtual CPU to enter the shutdown state.  If
this fault had occured outside of a virtual machine, it would have
caused the physical machine to restart"

Same current- works on real hardware (dell workstation). Apr 9.
But see below.

Poking around, the /usr/share/relink/kernel/GENERIC.MP/ directory
had only Makefile, nothing else.

So I rebooted the bsd.booted kernel, it seemed to finish the upgrade
(a few sysmerge reports), but upon reboot same symptoms.

So I started the 6.7-beta bsd.rd and (U)pgraded it again.  And upon
reboot the same symptom (no OpenBSD banner, VMware reports a fail.)
The kernel/relink directory now has expected files in it, but no
relink log file.

VMware config: (Windows 10 host, VMware workstation 12 player, 12.65.9
build-7535481)

VM config: 480MB, 2 processors, IDE hard disk, IDE CD/DVD, one
network adapter (em0).

Same symptom with 512MB memory.

Booting bsd.sp succeeds but reordering kernel fails again.


# ls -l /usr/share/relink/kernel/GENERIC
total 4
-rw-r--r--  1 root  wheel  95 Apr 11 00:44 relink.log
o67snap# cat /usr/share/relink/kernel/GENERIC/relink.log
(SHA256) /bsd: OK
make: don't know how to make newbsd
Stop in /usr/share/relink/kernel/GENERIC
(the directory is empty of course, no Makefile, not .o files).

Here is the dmesg with 512MB memory, single processor:

OpenBSD 6.7-beta (GENERIC) #114: Thu Apr  9 10:39:39 MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 520028160 (495MB)
avail mem = 491810816 (469MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe0010 (242 entries)
bios0: vendor Phoenix Technologies LTD version "6.00" date 07/02/2015
bios0: VMware, Inc. VMware Virtual Platform
acpi0 at bios0: ACPI 4.0
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT FACP BOOT APIC MCFG SRAT HPET WAET
acpi0: wakeup devices PCI0(S3) USB_(S1) P2P0(S3) S1F0(S3) S2F0(S3) S8F0(S3) 
S16F(S3) S17F(S3) S18F(S3) S22F(S3) S23F(S3) S24F(S3) S25F(S3) PE40(S3) 
S1F0(S3) PE50(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz, 2303.89 MHz, 06-4e-03
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,MMX,FXSR,SSE,SSE2,SS,SSE3,PCLMUL,SSSE3,FMA3,CX16,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,HV,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 65MHz
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 1 pa 0xfec0, version 11, 24 pins
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-127
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001
acpicmos0 at acpi0
"PNP0A05" at acpi0 not configured
acpiac0 at acpi0: AC unit online
cpu0: using Skylake AVX MDS workaround
pvbus0 at mainbus0: VMware
vmt0 at pvbus0
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82443BX AGP" rev 0x01
ppb0 at pci0 dev 1 function 0 "Intel 82443BX AGP" rev 0x01
pci1 at ppb0 bus 1
pcib0 at pci0 dev 7 function 0 "Intel 82371AB PIIX4 ISA" rev 0x08
pciide0 at pci0 dev 7 function 1 "Intel 82371AB IDE" rev 0x01: DMA, channel 0 
configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: 
wd0: 64-sector PIO, LBA, 14336MB, 29360128 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
atapiscsi0 at pciide0 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0:  removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
piixpm0 at pci0 dev 7 function 3 "Intel 82371AB Power" rev 0x08: SMBus disabled
"VMware VMCI" rev 0x10 at pci0 dev 7 function 7 not configured
vga1 at pci0 dev 15 function 0 "VMware SVGA II" rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
mpi0 at pci0 dev 16 function 0 "Symbios Logic 53c1030" rev 0x01: apic 1 int 17
mpi0: 0, firmware 1.3.41.32
scsibus2 at mpi0: 16 targets, initiator 7
ppb1 at pci0 dev 17 function 0 "VMware PCI" rev 0x02
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel 82545EM" rev 0x01: apic 1 int 18, address 
00:0c:29:05:5e:fd
eap0 at pci2 dev 1 function 0 "Ensoniq AudioPCI97" rev 0x02: apic 1 int 19
ac97: codec id 0x43525913 (Cirrus Logic CS4297A rev 3)
aud

Re: Openbsd supports pae?

[Bryan Steele]

Why should any of us exert more effort than you're willing to
put into writing an email?

Nikita Stepanov wrote:
> Why?

Re: Openbsd supports pae?

[Philip Guenther]

Because it would be a total PITA now and in the future and benefit only
that small set of machines that have >4GB of memory but that can't run
64bit.

Since you like one-liner questions: why do you care?