Otherwise, I have used Dropbox on my Linux machines for quite awhile, but I will give Spideroak a whirl and see what it’s all about.

apt-cache search dropbox
mint-dropbox – Dropbox integration for Linux Mint
nautilus-dropbox – Dropbox integration for Nautilus

Ttyl!

mod_security on Dreamhost (and possibly other hosting providers) ships with default rules that will intermittently bite Drupal users. Each of these rules is just a regex match on text in a node, or the URL being requested. The rule is triggered intermittently – a reload usually solves the problem (and fails to trigger the rule).

The “page” that is “not found” is not actually the page the user is looking for. It’s internal_error.html that is to be served when PHP dies prematurely, on account of being blocked by mod_security for this request. Creating the internal_error.html file in the Drupal root should fix that problem.

You can add the rules above to your .htaccess file for your site, if you don’t have root permissions on your server. Instead of using LocationMatch, which is not valid for .htaccess, use this instead:

SecRuleRemoveById 960010
SecRuleRemoveById 960015
SecRuleRemoveById 960032
SecRuleRemoveById 950107

Hope that helps. I have just made the change on my web server, and am waiting to see if any additional mod_security errors will be generated. (They look like “Premature end of script headers” in the httpd error.log)

– Begin shamelessly copied from googlecache content –
“No explicit cipher (aes128-cb)

Merkur:jens jens$ scp jens@helios:/export/home/jens/XXXXX /dev/null
XXXXX 6% 143MB 23.7MB/s 01:22 ETA^CKilled by signal 2.

This is the default behaviour on my machines. Other setups might choose a different default algorithm. According to the OpenSSH homepage the list of availabe candidates is (cited from the man page):

Ciphers
Specifies the ciphers allowed for protocol version 2 in order of
preference. Multiple ciphers must be comma-separated. The default is
“aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
aes192-cbc,aes256-cbc”

Using 3des

I expected 3des to be quite slow, and I wasn’t disappointed:

Merkur:~ jens$ scp -c 3des jens@helios:/export/home/jens/XXXXX /dev/null
XXXXX 3% 82MB 11.7MB/s 02:51 ETA^CKilled by signal 2.

As expected, 3des will not be our performance king today.
Using Blowfish

The next candidate was Blowfish. I expected at least aes performance from it. Let’s see, how it worked out:

Merkur:jens jens$ scp -c blowfish jens@helios:/export/home/jens/XXXXX /dev/null
XXXXX 29% 615MB 36.0MB/s 00:40 ETA^CKilled by signal 2.

Final candidate: RC4

The final candidate is the only stream cipher in the suit: arcfour.

Merkur:~ jens$ scp -c arcfour jens@helios:/export/home/jens/XXXXX /dev/null
XXXXX 9% 202MB 51.7MB/s 00:36 ETA^Killed by signal 2.

Conclusion

Speedwise arcfour wins hands down. I did not expect a more than doubled performance over the default aes128-cbc. Who would have thought that switching the algorithm makes that much of a difference.”
– End googlecache content –

The default cipher after OpenSSH v4.7 is blowfish, which as you can see is slower than arcfour. Sadly, I am right, and you still have crappy hardware. I will note however that arcfour is MUCH less secure, but if you’re looking for speed it cant be beat. Except by http://www.psc.edu/networking/projects/hpn-ssh/theory.php .