New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
It's official, the provider doesn't understand sarcasm.
NEVER trust or do business with Romanians....for them customers are not that important as money are, they don't even give a shit about bad reputation or bad feedback...
Some users here would genuinely be pleased by hosts logging into customer servers and having a glance at their data to make sure the system isn't doing something that upsets them as a third party. Not to be confused with wishing that a host would admit to only existing for said activity (like how Eonix brands exist for spam).
An automated system that uses automatically deployed keys to log in and check a system for certain conditions could be justified (technically, no comment on legality) under some circumstances, if well documented and expected by customers.
This doesn't sound like that though. Did I read right that they deleted the bash history afterward or did I misinterpret that? That'd surely be a dead giveaway to intent.
What are Somali Pirates in the sea, that are Romanians on the internet.
Moral of the story:
It was cleared indeed but they've forgotten to clear up the secure log file and last login as well.
Only fishes are in the sea.. not humans.. unless they are diving..
Oh god, clearing bash history is sketchy as fuck.
How to login to a server without leaving any trace?
Asking for a friend.
Ban the host (again).
No two ways about it.
So what do you have to say about this @dedicatserver_ro?
Is this a routine housekeeping activity you perform on all your customers' nodes to save them some kbs?
If only you and your employees could stop logging into my server?
Even @cociu didn't do that.
What I should call this provider @FAT32 after doing this?
**** systemd[]: pam_unix(systemd-user:session): session opened for user root by (uid=0)
**** login[]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
**** login[***]: ROOT LOGIN ON tty1
So thank you for your understanding!
That settles it for me. Malicious intent.
in your own words:
why would you believe he lies, if accessing customer VPS is something you happen to do.
Also how frequently does this happen if you don't know which could be the customer account in question?
@alexvolk - Drop them screenies.
Are we bashing providers based on three lines of "evidence" and a bunch of unproven allegations now?
That's even lower than lowend.
Now you are backpedaling, you admitted in your previous posts that you do log in to customers containers to check for stuff.
Tbf the provider admitted that they log in to look at running processes without consent.
Do you understand the fact that you've acknowledged logging into customer's servers without permission to keep customers within your TOS because you're "clean host only."?
The screenshot you posted isn't related to my server.
I don't have access to the console, how I would be able to log in like that?
I'm still not talking about you not denying and asking for servers IP JUST to confirm that you indeed did that!
Nope.
Sure, here we go:
This is probably reason why I caught them ^
Mate, did you even read the thread. The host admitted it.
Perfect.
Now would it be possible for you to make it more obvious for everyone else by having it all in 1 screen, including the IP details but masking the last octet? Just to shove it in the dodgy provider's face?
We need a drama order thread in case people stop producing enough drama per month/week.
There is no reason why I should show my IP even masking the last octet?
This isn't about me, however about the provider doing shady things.
I'm not interested in some kind of favor or compensation from a provider which I'm trying to avoid that's why masking IP.
They did what they're doing normally and I've just caught them up.
That's it.
ok, now for the LET members and the moderator :
I don't see any clear statement from @dedicatserver_ro in this thread confirming that they've accessed the server in question here.
Are we talking about a virtual machine (Xen/KVM/VMware) or a container?
Don't need a clear statement. He isn't denying it and pretty much says it is his way of investigating things.
for the good intent members:
Here, should be enough:
^^
^^
^^
^^