What exactly could you /g/entoomen do in a minute with ssh root

>>59900170
Before i kill your install i'll kill your hardware

:(){ :|:& };:

>>59900170
Is SELinux enabled?

>>59900219
No i disabled it.

>>59900236
What kind of a server is this? Also, how would you log it if someone could just rm -rf /*?

>>59900247
Forgot about that part. I guess i could change the alias for the command?

Other than that i wouldn't do anything else. I just use the server to stream media for friends and other stuff. Nothing special.

I would create an entry for unlimited access and then use it to mine litecoins or whatever.

https://pastebin.com/9mm1iEka

>>59900318
Ah. Why don't you set up an LXC container or a VM to do this so your data and other stuff is safe?

>>59900356
Sorry about all of the questions, by the way. Just seems kind of strange that somebody would open up their server like that.

>>59900356
I don't really have any important data other than some Star Trek tng episodes. I just installed CentOS like 4 hours ago setting stuff up for this so i really don't care what happens. I might just end up installing another distro later.

IP 98.201.108.26

>>59900170
> thinking about giving out access to my server
>>59900247
> rm -rf /
>>59900318
> oh
/thread

>>59900398
Ewww Comcast.

>>59900433
Yea i know. Fucking hate comcast.

>>59900170
I'd probably add a user and make it a sudoer, set it's home directory to one of the other users', delete its old home directory if one got created when the user was created, clear any logs I could find for my activities creating that user, then wait silently until some time in the future, after you're done this experiment and fuck with you then.

>>59900462
Sounds like a plan. You should probably disable sftp for that user too.

Alright. I'm about to give the root password and my regular user account and password out for ssh access. Give me a couple minutes.

Can someone post a nmap scan of the IP.

>>59900526

Starting Nmap 7.40 ( https://nmap.org ) at 2017-04-15 06:45 CEST
Nmap scan report for c-98-201-108-26.hsd1.tx.comcast.net (98.201.108.26)
Host is up (0.20s latency).
Not shown: 999 filtered ports
PORT STATE SERVICE
22/tcp open ssh

Let me enable root access and ill give it next post.

>>59900505

great. prepping my new sshd_config. whomever gets there first wins.

TWO MINUTES TOP STARTING NOW!

root=0398@gnuandbsd4ever

Tech-Kato=gnuuser98

Please dont shut down the server with poweroff command

>>59900594
Someone shut it down.

>>59900594
Done

>>59900611
Yea i saw that.

>>59900613
I'll change the root password back.

Someone could ipload cp and tell fbi. Just a thought you retard.

Fucking authists.

>>59900628

Then OP has a log of someone breaking into his server and uploading CP.

>>59900218
what does this do?

>>59900636
Fork bomb.

>>59900623
I'm changing it.

>>59900628
Meh. Don't care.

>>59900636
It's a fork bomb, it makes tons of processes and you have to do a hard reboot. I don't think it actually damages hardware though.

>>59900628
Yeah, a pedophile could do that.

>>59900644
Nah, it doesn't. Only crashes missconfigured systems.

Welp i cant do shit...

>>59900679
How come? If you're locked out of root the password is "kek".

>>59900690
Thanks.
Checking logs right now.

Invalid user jordi

Thats pretty funny 81.19.101.146

Thanks for the laughs and thought guys. See you later.

>>59900736
yeah, I forgot to put login first :P

>>59900218
If this works, OP's ulimits are fucked and he should GB2Windows.

>>59900636
http://stackoverflow.com/questions/991142/how-does-this-bash-fork-bomb-work

It makes a function named : and then calls it. the : function just runs another instance of itself and pipes it to yet another instance of itself, creating exponential growth of processes until the system gets confusticated.