cmeerw
cmeerw
About
- Username
- cmeerw
- Joined
- Visits
- 8,331
- Last Active
- Roles
- Member
- Thanked
- 314
Comments
-
(Quote) How about getting a provider tag first, before posting offers here?
-
(Quote) Yes... but first you need to get root access to the host machine. And to do that you need to use the IPMI vulnerability, but the host also needs to have a completely insecure boot manager that lets you boot into something like init=/bin/bash…
-
Could someone explain the attack vector here. As far as I understand, they got access to IPMI. Is that essentially allowing access to the console? So they would then reboot the server and then boot into something like init=/bin/bash to get root acce…
-
(Quote) That's not very low-end as the maximum allowed here is $7 per month. How come others can offer so much cheaper packages?
-
(Quote) Not much really, just noticed a small glitch in the network setup in my NetBSD 10 image. But it's probably really just cosmetic - it adds "alias" flags to the addresses when it shouldn't. Just something to keep in mind for the 10.1…
-
(Quote) Or not installing security fixes.
-
(Quote) Will they even have a provider tag by Black Friday? And to continue the list: Do you allow setting RDNS records for both IPv4 and IPv6? Do you block any ports (25)? Do you have clean IP space? Do you allow sending spam? Do you allow port s…
-
Also got it now. I think this is important: (Quote) Thanks for that!
-
(Quote) But what's the conclusion here? Has anything been done to avoid a repeat of this situation? Will @crunchbits act on such a report in the future again? Has the reporter been warned not to blindly send abuse reports where the source IP address…
-
Discourse seems to be quite popular with technical forums. But I really prefer good old NNTP where you can have everything you care about in one place (btw, Gmane is really great to follow mailing lists).
-
BTW, has anyone had any more success with using a NetBSD KASLR kernel? Using the instructions from https://wiki.netbsd.org/security/kaslr/ only results in a page fault: (Image)
-
BTW, a few weeks ago I mentioned the cpuid tool - as of cpuid 20241023 my changes for NetBSD have been integrated, so it now also works on NetBSD.
-
Could someone post an update how this was resolved/handled?
-
(Quote) https://btxx.org/posts/openbsd-linveo/ actually seems to use the amd64 image.
-
(Quote) You mean the tunefs -m? That won't do anything to fix the inodes issue - it only allows non-root users to use a bit more of the filesystem space.
-
(Quote) Interesting, I only ever get as far as this with OpenBSD: (Image) Not that I really want to use OpenBSD, was just curious...
-
(Quote) You can always limit the build job to a single core and/or periodically send it SIGSTOP/SIGCONT signals to pause it for a bit.
-
(Quote) So it would have worked with the new filesystem settings with the original disk space allocation. (Quote) Well... there is a 512 MB swap partition you could use as a temporary alternative root filesystem.
-
(Quote) Yes, that's the inodes/filesystem overhead (and there is a 512 MB swap partition). BTW, you can also look at the partitions with gpt show ld0 and dkctl ld0 listwedges
-
(Quote) BTW, I actually tried booting into the OpenBSD 7.6 installer (via netboot.xyz) when it was released, but it did hang just before getting to user space.
-
(Quote) I believe your version of the image might actually just resize the partition and file system on the next reboot (that's because in the first version I didn't mount the filesystem with the "log" option). Later versions now use the …
-
BTW, the actual maximum number of inodes is 3117310 (3100457 was the number of available inodes on my system), but I think df only shows that number when using df -G / (and the values are currently swapped around on 10.0).
-
(Quote) Sorry... that's just the (max) number of inodes you will get when re-installing NetBSD from my template on that particular VM. See the newfs man page: -i bytes-per-inode This specifies the density of inodes in the file syst…
-
(Quote) Was actually wondering how many inodes you had used compared to the new max of 3100457 - your 795510 will still comfortably fit into that max.
-
(Quote) Most likely memory reserved by RH kernels for kdump.
-
(Quote) Looks like you didn't start with the new NetBSD template, which would have given you maybe 4 GB more space on the file system (not sure if that would have been enough space). Just out of interest, how many inodes are you using? df -hi / Fi…
-
(Quote) Thanks so much. The NetBSD 10 image works as expected. The NetBSD 9.4 image works, except that it doesn't see any configuration data, so no network or SSH keys are configured. I am not sure if this an issue with NetBSD 9.4 or if that config…
-
(Quote) This is what you get with a new NetBSD 10 install: # df -mi /Filesystem 1M-blocks Used Avail %Cap iUsed iAvail %iCap Mounted on/dev/dk2 24316 441 22659 1% 15723 3101587 0% /
-
OpenBSD 7.6 has been released.
-
(Quote) Yes, your image will be affected, a quick way to tell is to run df -mi / In the iAvail column it will likely show something like 20 million inodes (instead of maybe 3 million), but in the 1M-blocks column you'll likely only see around 20000…