Free Alpine Linux Shell Accounts

Not_OlesNot_Oles Hosting ProviderContent Writer
edited March 2023 in Free Offers and Stuff

Update: Sorry, but this wonderful server has been returned to @Cloudie. I hope everyone gets the VPS they want! Best wishes! -- Tom a/k/a @Not_Oles

Friendly greetings to all! ๐ŸŒŽ๐ŸŒ

What's New?

  • IPv4 Ping Monitor

  • IPv6 Ping Monitor

    • Alpine Linux seems to have been installed on the MetalVPS antique Intel node at Hurricane Electric Fremont-2.

    • Want a free Alpine shell account? Maybe with sudo? ๐Ÿ‘ With all node resources shared, fair use? ๐ŸŽ‚ Right now plenty of server resources are available because only a few people are using the Fremont node. :)

Fremont Node Specs

  • Server: Intel S2600GZ

  • CPU: 2 x Xeon E5-2630L v2, 2 x 6 cores = 12 cores = 24 threads

  • RAM: 32 GB DDR3 ECC (upgrade to 64 GB expected this month)

  • Hard Drive: 1 x 500 GB SSD, 2 x 1 TB HDD

  • IP Addresses: IPv4/28, IPv6/48

  • Connection: 1 GBit/s port

  • Bandwidth: Fair use

  • Datacenter: Hardware rented from Cloudie Networks, LLC inside Hurricane Electric Fremont 2, Fremont, California USA ๐Ÿ‡บ๐Ÿ‡ธ

  • Node OS: Alpine Linux 3.17 edge! ๐Ÿคฉ NetBSD might or might not be coming soon! โค๏ธ

  • VM OS: Whatever you install!

Who?

  • MetalVPS is a project of @Not_Oles a/k/a Tom Miller a/k/a the cluelessโ„ข guy.

Where?

  • MetalVPS currently has nodes in Falkenstein, Germany ๐Ÿ‡ฉ๐Ÿ‡ช and Fremont, California USA. ๐Ÿ‡บ๐Ÿ‡ธ

  • This thread is for the Fremont node. ๐Ÿ‡บ๐Ÿ‡ธ

  • The Falkenstein node has its own offer thread.

Why?

  • Why not? It's fun to play with and learn about servers, operating systems, and the internet. :)

  • @Not_Oles uses very little of his MetalVPS servers' capacity. It's better to offer the extra capacity to others than to waste it.

Congrats!

Warnings!

  • Cluelessโ„ข administrator! ๐Ÿ˜€ @Not_Oles frequently messes up! ๐Ÿ˜ฑ

  • @Not_Oles is especially cluelessโ„ข about Alpine since he is an Alpine noob. ๐Ÿค—

  • Hey! Fremont runs Alpine 3.17 edge! ๐Ÿคฉ

  • Sometimes trusted MetalVPSians might or might not get sudo. ๐Ÿ™ˆ๐Ÿ™‰๐Ÿ™Š

  • MetalVPS has no billing panel and no server control panel. ๐Ÿ”œ It's all command line until you install a GUI or activate whatever pre-installed GUI you want. ๐Ÿ†•

  • MetalVPS has no onboarding and no knowledge base. โ™’๏ธŽ If you want to make an LXC or KVM VPS, please be willing to research about how to do it on the command line. ๐Ÿฅฐ

  • Account delivery might take awhile! ๐Ÿ˜ด

  • Accounts subject to cancellation at any time without advance notice! ๐Ÿ’ฅ

  • No warranty, to the extent permitted by applicable law. No service level agreement. Not for business use. Intended especially for computer learning and fun! ๐Ÿค‘

  • White Hat stuff only, please! No copyright violations, please. ๐Ÿ‘

  • @Not_Oles tries to keep the system updated. Frequent maintenance reboots are almost guaranteed! ๐ŸŒบ

  • Please make your own redundant, offsite backups! It's easy to download or sync or clone your backup to a safe place. Please also make sure that you actually can restore from your backups! Please think of your MetalVPS account as ephemeral! It might blow up! We or you might reinstall the node! ๐Ÿคฆโ€โ™‚๏ธ

  • MetalVPS.com is an indie project of @Not_Oles a/k/a Tom Miller with help from the MetalVPSians and many other friends. MetalVPS.com is not a project of lowendspirit.com, lowendtalk.com, or of Cloudie Networks, LLC. ๐Ÿ‘จโ€๐Ÿ’ปโ€‹

  • Other MetalVPSians can see your account name, some of the processes you are running, and much other information. So, please do not put confidential information on the server. ๐Ÿค”

How To Sign Up

  • Please post in this thread. Only if necessary, please PM @Not_Oles or use the email on @Not_Oles profile.

Support

  • Please post in this thread. Only if necessary, PM or use the email on @Not_Oles profile.

  • Additional communication channels might be available via Signal App, Discord, Jitsi, etc.

What People Are Saying

  • About MetalVPS

"This is really really cool."

"I enjoyed the section of the OP dedicated to complementary comments, including helpful links so they can be verified."

"MetalVPS used to be a high end provider, but it's becoming a sorority now."

"fun stuff indeed, appreciating the comfortable computing experience!"

"Liking my darkstar"

"Nice trial and results! Very interesting :)"

Metalvps recommended on OGF ๐Ÿ™ˆ

"It just crossed my mind that I've been using your server for over half a year! It's been an amazing experience! . . . Your services deserve much more attention. <3"

"Wow pretty nice ! Congrats excellent options thanks for being a part of the community"

"the terms seemed exceptionally fair"

"Kernel Linux 5.11 is now in much better shape for AMD <3"

"Yes, please. Iโ€™ll take that."

"it's really quite dedicated. not all dedicated are the same."

"MetalVPS-AX101 has a reasonable price"

"really need a testing ground badly now especially with dedicated core"

"the fastest VPS I ever used"

"I've been using this one from him. Highly recommend! His support is really amazing!"

"10/10 metalvps recommended"

"very powerful"

"premium stuff"

"Grab it while the hotel still has vacant rooms."

". . . very passionate and enthusiastic about everything. Not all businesses are made this way and it's very easy to see when you interact with them. You are giving the right impression with this industry and it's wonderful to see."

"I think MetalVPS is designed in between a dedicated and a regular VPS. Some use case cannot fill the capacity of a dedicated but need more CPU than a regular VPS, and it makes sense to use MetalVPS in such situation."


  • About Not_Oles

"I did want to thank @Not_Oles for always being so friendly. Makes me smile seeing how nice you are to everyone here."

"You are a great person."

"Possibly the most polite and enthusiastic personality in the entire LE* world with a genuine interest that runs so deep he even set up a business exclusively catering for LES. as a regular content writer for LES his articles frequently top the charts in terms of most viewed (according to google)"

"Really, you're the best person I've known on the internet."

"we've found that good, in-depth technical articles tend to drive user interaction and new sign-ups on the forum. @Not_Oles's Proxmox articles are evidence of this."

"It was a pleasure for me to collaborate with Tom, he really knows what he's doing :)"

"Thanks again to @Not_Oles for valiant testing."

"you've brought a smile on my face countless times "

"Good luck with your new project! :D Happy to have you around here!"

"I always love how you come up with new ideas :D Good luck, mate!

"May you continue to learn and inspire others."

"he is a great guy!"

"he is the sweetest guy in LES .."

"Everybody loves @Not_Oles! <3"

"resplendent as the Sonoran Sun"

"god bless not_oles ^^"

"every time I visit les and see that profile picture, it brightens up my day."

"As for the new administrator, I nominate @Not_Oles."

"I would love to see @Not_Oles as a moderator or a bigger role."

"I would also support @Not_Oles as admin :)"

Thanks

Thanks again and best wishes! ๐Ÿ‡บ๐Ÿ‡ธ๐Ÿ—ฝ๐Ÿ‡ฒ๐Ÿ‡ฝ๐Ÿœ๏ธ

I hope everyone gets the servers they want!

Thanked by (1)Ganonk
Tagged:
ยซ13456717

Comments

  • @Not_Oles this is awesome....

    I'd love to try one of them accounts and you know...
    Play with and learn about servers, operating systems, and the internet ๐Ÿ˜€

    Thanks

    Thanked by (1)Not_Oles
  • tarasistarasis OG
    edited December 2022

    I would also love to try one of the accounts. Thank you

    Thanked by (1)Not_Oles
  • iaecmiaecm OG
    edited December 2022

    @Not_Oles Quite interesting, I'd like to give it a try. =)

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @tarasis @localhost Could you guys each please post your ed25519 public key? Please check https://stackoverflow.com/questions/16158158/what-is-the-public-url-for-the-github-public-keys if you are concerned about posting your public key. But, if you prefer not to post your public key, it's okay to PM me. Thanks! :)

    Thanked by (1)tarasis

    I hope everyone gets the servers they want!

  • @Not_Oles said:
    @tarasis @localhost Could you guys each please post your ed25519 public key? Please check https://stackoverflow.com/questions/16158158/what-is-the-public-url-for-the-github-public-keys if you are concerned about posting your public key. But, if you prefer not to post your public key, it's okay to PM me. Thanks! :)

    DM'd

    Thanked by (1)Not_Oles
  • vyasvyas OG
    edited December 2022

    So does Darkstar fade in the dark
    While Alpine starts to shine?
    If true then my day turn sad,
    Though one hopes it won't be so bad.

    It's admin's call really, a decision not so tad,
    For changing operating systems on servers is nobody's fad.
    Metal, o! Metal, to see your Mettle,
    Will the apk prevail, and to see txz derail?


    composed by a Human. No AI or bots involved.

    Thanked by (2)tarasis Not_Oles

    โ€”โ€”โ€”-
    blog | exploring visually |

  • I want one.

    Thanked by (1)Not_Oles
  • Hi @Not_Oles ,

    I would also love to try this.
    Thank you.

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Hi Guys!

    So, in what I think was the default Alpine 3.17 edge install, I went to make an account for @tarasis. First I made a test account for myself.

    fmt:~# adduser -h /home/notoles -s /bin/ash notoles
      [ . . . ]
    fmt:~#
    

    Wow, I was quite surprised when I logged in to my new notoles account and found that su(1) worked for my new account despite my not having added myself to the wheel group!

    It seems:

    /home/notoles # which su
    /bin/su
    /home/notoles # ls -l /bin/su
    lrwxrwxrwx    1 root     root            11 Dec 11 05:07 /bin/su -> /bin/bbsuid
    /home/notoles # ls -l /bin/bbsuid
    ---s--x--x    1 root     root         14160 Nov 19 10:13 /bin/bbsuid
    /home/notoles # 
    

    Alpine seems to have a package called bbsuid, and the linked info page says "Obsolete package that can be removed." Nevertheless,

    /home/notoles # apk del bbsuid
    ERROR: No such package: bbsuid
    /home/notoles # 
    

    So, as it stands, it looks like any new account can become root.

    Might we have an Alpine freak who can explain to this Alpine noob the context of bbsuid? Maybe the "bb" means "busybox."

    What should be done here? One hack might be to change the ownership of /bin/bbsid so that only wheel group members could run it. Or just delete /bin/bbsuid? What happens to /bin/bbsuid when/if sudo is installed?

    @Not_Oles said: Cluelessโ„ข

    Aha!

    New accounts paused already until I figure this out myself or somebody hits me with the clue bat. :) Thanks! Friendly greetings!

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @iaecm said:
    @Not_Oles Quite interesting, I'd like to give it a try. =)

    Hi! Could you please post or PM me your ed25519 ssh public key? Thanks!

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @vyas said:
    So does Darkstar fade in the dark
    While Alpine starts to shine?
    If true then my day turn sad,
    Though one hopes it won't be so bad.

    It's admin's call really, a decision not so tad,
    For changing operating systems on servers is nobody's fad.
    Metal, o! Metal, to see your Mettle,
    Will the apk prevail, and to see txz derail?


    composed by a Human. No AI or bots involved.

    The thing about Darkstar is that, mysteriously, everything always seems to work. I remember awhile back when I was making several kinds of VMs on one of the AX line servers that I used to have. I just did Slackware as part of the test group. But then, everything worked out of the box on the test VM. So I put Slackware on Darkstar when I bought her. Since then everything seems to work including almost daily updates and compiling various kinds of stuff. So I do not expect to move Darkstar away from Slackware. Darkstar was not mentioned here because those accounts need to be advertised as LES Exclusive due to the pricing rules.

    I imagined from the beginning that I might put NetBSD on the new Fremont server. But, as usual, I always want to try various options. Alpine seems especially fun because it seems really fast. From the way it runs in RAM, I think.

    @vyas, you are Shakespeare reincarnate! Thank you for your poem! :)

    Thanked by (1)vyas

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @Not_Oles said: New accounts paused already until I figure this out myself or somebody hits me with the clue bat. Thanks! Friendly greetings!

    Maybe I got it. . . .

    fmt:~# apk search bbsuid
    busybox-suid-1.35.0-r29
    fmt:~# apk search busybox
    busybox-doc-1.35.0-r29
    busybox-1.35.0-r29
    busybox-suid-1.35.0-r29
    busybox-static-1.35.0-r29
    busybox-binsh-1.35.0-r29
    busybox-extras-1.35.0-r29
    busybox-extras-openrc-1.35.0-r29
    busybox-ifupdown-1.35.0-r29
    busybox-openrc-1.35.0-r29
    busybox-mdev-openrc-1.35.0-r29
    fmt:~# 
    

    I also found https://lists.alpinelinux.org/~alpine/aports/<[email protected]> but I'm unsure of the current status.

    Maybe I need to run something like apk del busybox-suid? Thanks!

    I hope everyone gets the servers they want!

  • @Not_Oles PM'd

    Thanked by (1)Not_Oles
  • I love Alpine,I have two machine with Alpine,It's small and powerful.
    Just a little bit: it can't be switch to google bbr,I am confused.

    Thanked by (1)Not_Oles
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    MMmmkay . . .

    On Darkstar

    tom@darkstar:~$ mkdir alpine
    tom@darkstar:~$ cd alpine/
    tom@darkstar:~$ wget https://gitlab.alpinelinux.org/alpine/aports/-/archive/master/aports-master.tar
      [ . . . ]
    tom@darkstar:~/alpine/aports-master/main/busybox$ less APKBUILD 
      [ . . . ]
    suid() {
            pkgdesc="suid binaries of Busybox"
            depends="$pkgname"
    
            cd "$_dyndir"
            mkdir -p "$subpkgdir"/bin
            install -m4111 bbsuid "$subpkgdir"/bin/bbsuid
    }
      [ . . . ]
    

    On fmt

    fmt:~# apk search bbsuid
    busybox-suid-1.35.0-r29
    fmt:~# apk search busybox
    busybox-doc-1.35.0-r29
    busybox-1.35.0-r29
    busybox-suid-1.35.0-r29
    busybox-static-1.35.0-r29
    busybox-binsh-1.35.0-r29
    busybox-extras-1.35.0-r29
    busybox-extras-openrc-1.35.0-r29
    busybox-ifupdown-1.35.0-r29
    busybox-openrc-1.35.0-r29
    busybox-mdev-openrc-1.35.0-r29
    fmt:~# ls -l /bin/su 
    lrwxrwxrwx    1 root     root            11 Dec 11 05:07 /bin/su -> /bin/bbsuid
    fmt:~# ls -l /bin/su /bin/bbsuid
    ---s--x--x    1 root     root         14160 Nov 19 10:13 /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 11 05:07 /bin/su -> /bin/bbsuid
    fmt:~# apk del busybox-suid
    World updated, but the following packages are not removed due to:
      busybox-suid: alpine-base
    
    OK: 148 MiB in 81 packages
    fmt:~# ls -l /bin/su /bin/bbsuid
    ---s--x--x    1 root     root         14160 Nov 19 10:13 /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 11 05:07 /bin/su -> /bin/bbsuid
    fmt:~# 
    

    So, how to remove a package that is part of alpine-base? No tips in https://wiki.alpinelinux.org/wiki/Alpine_Package_Keeper#Remove_a_Package.

    Friendly greetings! :)

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Maybe there is more information in the manpage!? :)

    fmt:~# apk add mandoc man-pages mandoc-apropos less less-doc
    (1/3) Installing less-doc (608-r0)
    (2/3) Installing mandoc (1.14.6-r6)
    (3/3) Installing mandoc-apropos (1.14.6-r6)
    Executing busybox-1.35.0-r29.trigger
    Executing mandoc-apropos-1.14.6-r6.trigger
    OK: 165 MiB in 86 packages
    fmt:~# man man
    fmt:~# man apk
    man: No entry for apk in the manual.
    fmt:~# 
    

    Oh! Cluelessโ„ข Haha! :)

    I hope everyone gets the servers they want!

  • I would like to have one please, when the new account pause is lifted.

    Thanked by (1)Not_Oles

    Why?

  • I would also like to have one, when it resumes.
    Thanks!

    Thanked by (1)Not_Oles
  • @Not_Oles said:

    @Not_Oles said: New accounts paused already until I figure this out myself or somebody hits me with the clue bat. Thanks! Friendly greetings!

    Maybe I got it. . . .

    fmt:~# apk search bbsuid
    busybox-suid-1.35.0-r29
    fmt:~# apk search busybox
    busybox-doc-1.35.0-r29
    busybox-1.35.0-r29
    busybox-suid-1.35.0-r29
    busybox-static-1.35.0-r29
    busybox-binsh-1.35.0-r29
    busybox-extras-1.35.0-r29
    busybox-extras-openrc-1.35.0-r29
    busybox-ifupdown-1.35.0-r29
    busybox-openrc-1.35.0-r29
    busybox-mdev-openrc-1.35.0-r29
    fmt:~# 
    

    I also found https://lists.alpinelinux.org/~alpine/aports/<[email protected]> but I'm unsure of the current status.

    Maybe I need to run something like apk del busybox-suid? Thanks!

    I've never used Alpine Linux, so I'm speaking at a distance, but their "About" page says, "Alpine Linux is built around musl libc and busybox". (See https://alpinelinux.org/about/ .) Given this statement alone, I don't think that it would be a good idea to delete busybox or any part of it!

    As a general analogy with BSD systems, one shouldn't mess with the base system :)

    My perception of Alpine Linux -- again, at a distance -- has always been that it wouldn't be the best choice for a traditional multi-user system where everyone has a shell account (but perhaps I'm mistaken about this). In my view, Slackware would fit this purpose much better

    "A single swap file or partition may be up to 128 MB in size. [...] [I]f you need 256 MB of swap, you can create two 128-MB swap partitions." (M. Welsh & L. Kaufman, Running Linux, 2e, 1996, p. 49)

  • @Not_Oles said:
    So, in what I think was the default Alpine 3.17 edge install, I went to make an account for @tarasis. First I made a test account for myself.

    fmt:~# adduser -h /home/notoles -s /bin/ash notoles
      [ . . . ]
    fmt:~#
    

    Wow, I was quite surprised when I logged in to my new notoles account and found that su(1) worked for my new account despite my not having added myself to the wheel group!

    It seems:

    /home/notoles # which su
    /bin/su
    /home/notoles # ls -l /bin/su
    lrwxrwxrwx    1 root     root            11 Dec 11 05:07 /bin/su -> /bin/bbsuid
    /home/notoles # ls -l /bin/bbsuid
    ---s--x--x    1 root     root         14160 Nov 19 10:13 /bin/bbsuid
    /home/notoles # 
    

    Alpine seems to have a package called bbsuid, and the linked info page says "Obsolete package that can be removed." Nevertheless,

    /home/notoles # apk del bbsuid
    ERROR: No such package: bbsuid
    /home/notoles # 
    

    So, as it stands, it looks like any new account can become root.

    Not good, of course

    In this respect, it's odd that the page https://wiki.alpinelinux.org/wiki/Setting_up_a_new_user suggests that this doesn't (or shouldn't) happen

    (Perhaps install doas and edit /etc/doas.d/doas.conf to deny the newly created user root access? But one shouldn't need to do this ...)

    "A single swap file or partition may be up to 128 MB in size. [...] [I]f you need 256 MB of swap, you can create two 128-MB swap partitions." (M. Welsh & L. Kaufman, Running Linux, 2e, 1996, p. 49)

  • sounds great , i would like to have a try

    Thanked by (1)Not_Oles
  • @Not_Oles said:
    Hi! Could you please post or PM me your ed25519 ssh public key? Thanks!

    Are ed25519 elliptic-curve SSH keys a technical requirement here, or just a preference to encourage good practice?

    Many people prefer to use smartcards for SSH access, which adds an extra physical dimension of security, but are often limited to RSA or, if supporting elliptic-curve, not ed25519.

    Thanked by (1)Not_Oles
  • rootroot OG
    edited December 2022

    This project reminds me of my first shell and first Linux learning machine. It was held by Nic-Nac-Project.de - now FreeShell.de - which offered free shells for postcards sent to the owner. I still have that account. These free shells are great ways to learn, test and spin stuff without the fear of breaking something as superuser.

    This is a great project @Not_Oles and I hope many newbies will get onboard to learn Linux. Maybe (as a recommendation if I may) you could setup for users some remote desktop based on something light and modern (like LXQT) instead of SSH access. This way users may feel more comfortable nowadays when testing and learning BASH scripting. Back in the days of free shells the problem was computing power and bandwidth, which nowadays might not be the case (just an idea).

  • I enjoyed the section of the OP dedicated to complementary comments, including helpful links so they can be verified.

    Thanked by (4)xleet Not_Oles tarasis Erisa
  • @Not_Oles is it OK really, as su isn't sudo ..? Just need strong root password.

    Thanked by (1)yoursunny
  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Hi Guys!

    Thanks for your comments above! <3 More on them soon. . . . :)

    Meanwhile, here are this morning's updates:

    fmt:~# date -u
    Mon Dec 12 17:29:03 UTC 2022
    fmt:~# apk -U upgrade
    fetch http://mirror.fcix.net/alpine/edge/main/x86_64/APKINDEX.tar.gz
    (1/6) Upgrading libcrypto3 (3.0.7-r0 -> 3.0.7-r1)
    (2/6) Upgrading libssl3 (3.0.7-r0 -> 3.0.7-r1)
    (3/6) Upgrading ncurses-terminfo-base (6.3_p20221203-r0 -> 6.3_p20221210-r0)
    (4/6) Upgrading ncurses-libs (6.3_p20221203-r0 -> 6.3_p20221210-r0)
    (5/6) Upgrading linux-lts (5.15.81-r0 -> 5.15.82-r0)
    (6/6) Upgrading openssl (3.0.7-r0 -> 3.0.7-r1)
    Executing busybox-1.35.0-r29.trigger
    Executing ca-certificates-20220614-r2.trigger
    Executing kmod-30-r1.trigger
    Executing mkinitfs-3.7.0-r0.trigger
    ==> initramfs: creating /boot/initramfs-lts
    Executing syslinux-6.04_pre1-r11.trigger
    /boot is device /dev/sdc1
    OK: 165 MiB in 86 packages
    fmt:~# 
    

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Where is bbsuid used in Alpine Linux 3.17 edge default install?

    This seems too many lines to post here on LES, but, if we look inside /bin, we see that almost all the /bin tools are symlinks to busybox. A few, however, maybe because they need SUID, are symlinked to bbsuid.

    Inside /bin

    fmt:~# ls -l /bin 
    total 1116
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 arch -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ash -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 base64 -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 bbconfig -> /bin/busybox
    ---s--x--x    1 root     root         14160 Nov 19 10:13 bbsuid
    -rwxr-xr-x    1 root     root        845488 Nov 19 10:13 busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 cat -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 chattr -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 chgrp -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 chmod -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 chown -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 cp -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 date -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 dd -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 df -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 dmesg -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 dnsdomainname -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 dumpkmap -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 echo -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ed -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 egrep -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 false -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 fatattr -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 fdflush -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 fgrep -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 fsync -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 getopt -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 grep -> /bin/busybox
    -rwxr-xr-x    1 root     root          2346 Apr  8  2022 gunzip
    -rwxr-xr-x    1 root     root         72520 Apr  8  2022 gzip
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 hostname -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ionice -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 iostat -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ipcalc -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 kbd_mode -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 kill -> /bin/busybox
    -rwxr-xr-x    1 root     root        145712 Aug  2 08:35 kmod
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 link -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 linux32 -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 linux64 -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ln -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 login -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ls -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 lsattr -> /bin/busybox
    lrwxrwxrwx    1 root     root             4 Dec 11 03:33 lsmod -> kmod
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 lzop -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 makemime -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 mkdir -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 mknod -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 mktemp -> /bin/busybox
    lrwxrwxrwx    1 root     root             4 Dec 11 03:33 modinfo -> kmod
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 more -> /bin/busybox
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 mount -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 mountpoint -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 mpstat -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 mv -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 netstat -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 nice -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 pidof -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ping -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ping6 -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 pipe_progress -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 printenv -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 ps -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 pwd -> /bin/busybox
    -rwxr-xr-x    1 root     root         34624 Dec  3 05:36 rc-status
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 reformime -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 rev -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 rm -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 rmdir -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 run-parts -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 sed -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 setpriv -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 setserial -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 03:25 sh -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 sleep -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 stat -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 stty -> /bin/busybox
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 su -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 sync -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 tar -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 touch -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 true -> /bin/busybox
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 umount -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 uname -> /bin/busybox
    -rwxr-xr-x    1 root     root         14160 Nov 22 10:47 uniso
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 usleep -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 watch -> /bin/busybox
    lrwxrwxrwx    1 root     root            12 Dec 11 02:00 zcat -> /bin/busybox
    fmt:~# 
    

    grep for bbsuid

    fmt:~# ls -l /bin | grep bbsuid
    ---s--x--x    1 root     root         14160 Nov 19 10:13 bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 mount -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 su -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 umount -> /bin/bbsuid
    fmt:~# 
    

    From lists.alpinelinux.org

    the suid binaries are only:
    "/bin/mount",
    "/bin/ping",
    "/bin/ping6",
    "/bin/umount",
    "/usr/bin/crontab",
    "/usr/bin/passwd",
    "/usr/bin/su",
    "/usr/bin/traceroute",

    So, grep for bbsuid inside /usr/bin

    fmt:~# ls -l /usr/bin | grep bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 crontab -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 passwd -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 traceroute -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 traceroute6 -> /bin/bbsuid
    lrwxrwxrwx    1 root     root            11 Dec 12 17:33 vlock -> /bin/bbsuid
    fmt:~# 
    

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    Hmm. might there be a way out which involves vlock?

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @brick2008 said:
    I love Alpine,I have two machine with Alpine,It's small and powerful.
    Just a little bit: it can't be switch to google bbr,I am confused.

    Hi @brick2008!

    I looked at https://github.com/google/bbr, the README.md says

    "This open source distribution contains documentation, scripts, and
    other materials related to the BBR congestion control algorithm."

    Can you please add some more details about why Alpine can't be swtched to BBR?

    Friendly greetings! :)

    I hope everyone gets the servers they want!

  • Not_OlesNot_Oles Hosting ProviderContent Writer

    @jmaxwell @sh97 @gomi Can you guys please post or PM your keys? Thanks!

    Thanked by (1)jmaxwell

    I hope everyone gets the servers they want!

Sign In or Register to comment.