Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a VPS. I might be able to encrypt my partition but I havent tried. My VPS company I believe can reset my root password although the only SSH key I see is my own. With all my data I have it encrypted with encfs. Just in case a hacker gets some kind of access, encfs can only mount the drive if my password is correct (SSH keys won't mount it, resetting root password will not mount as the new password is an incorrect passphrase)

My question is can my VPS host break into my box? Physically the data is encrypted. I believe root can be changed without resetting the box? If so then they can have access to my already mounted filesystem? If another user with no permission is logged in can the user do something to access the ram and dump sensitive data? can the VPS host easily read the contents of my RAM?

Note: This is hypothetical. I'm thinking about if I have big clients I want to know how much security I can promise and this popped into mind. I'd rather not host a box at home nor have the pipes to support it.

share|improve this question
up vote 13 down vote accepted

As a general rule, physical access to the machine is all that's ever needed to compromise it. You are, after all, trusting that what the machine tells you is true; a person with physical access can void that trust. Consider that an attacker with physical access can theoretically do anything (including installation of hardware/firmware rootkits, etc).

If the data is encrypted, that's a good first step, but at every step (when you are entering your authentication to decrypt the volume, etc) you are trusting the computer not to lie to you. That is much more difficult when you do not have personal control over the physical machine.

As for some of your specific queries:

If another user with no permission is logged in can the user do something to access the ram and dump sensitive data?

In general, no. Raw memory access is a privileged operation.

can the vps host easily read the contents of my ram?

Yes. Isolation in a virtual environment means that you have no control over the external operating environment that the VPS is running within. This operating environment could indeed do this.

share|improve this answer
VMware, for example, allows you to take a snapshot of a running system, and dumps the RAM to a file which you can inspect. – LawrenceC Sep 10 '12 at 18:51

Since the data has to be decrypted to be usable, it will be available in an unencrypted state during runtime.

You should treat it as though the provider can access the live running system at any time without your knowledge. This includes data at rest on disk, data contained in memory (such as decryption keys) and even any keystrokes you send (i.e., assume any typed password can be observed and recorded).

share|improve this answer
I doubt keystrokes could be as ssh is encrypted end to end. Maybe if they tamper with my software with something like a rootkit they could – acidzombie24 Sep 8 '12 at 1:48
@acidzombie24: SSH is encrypted end-to-end, but they have access to one of the ends. – Mechanical snail Sep 8 '12 at 4:40
@bahamat: Well, technically there's homomorphic encryption, but currently it's too slow to be practical. – Mechanical snail Sep 8 '12 at 4:42
What do you mean by one of the ends? I'd notice if they change my private key. They cant copy if i did do this and encrypt the partition. I'm not sure if private keys can be extracted by looking at ram but maybe. – acidzombie24 Sep 8 '12 at 4:53
@acidzombie24, the VPS host has physical control over the machine running sshd. No software is secure against somebody who can monitor every byte that goes in or out of the CPU. – cjm Sep 8 '12 at 6:36

There is no way to be safe against a malicious hosting provider, they can access your data no matter how you try to avoid it. A few simple examples:

  1. Encrypted SSH traffic can be discovered by taking the host key from the host filesystem and putting another SSH server as a man-in-the-middle that decrypts the traffic and negotiates with your SSH server.
  2. Encrypting the root filesystem or the ssh host key would require you to enter the password at a terminal, and since the terminal is controlled by the provider, it cannot be considered safe.

The only reasonably safe method of having a server is buying, installing a box and putting it in your own cage in a shared or private hosting environment, setting up an encrypted filesystem, a trusted boot device, a physical lock on the cage, and secure console access.

Even this might have holes in it due to things like security issues in software versions, lockpicking (for the physical lock).

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.