I have a multi-TB btrfs made up of virtual disk images that live on NetApp NFS filers. The data are redundant at the NetApp level, so the btrfs is RAID-0.
In addition to providing redundancy, the NetApps do their own scrubbing for data integrity.
Because there is no redundancy at the btrfs level, checksum failures aren't automatically correctable, but I can recover damaged files from backups.
Is there value in doing my own scrubbing, or should I rely on the lower layers and save I/O?
I own a couple of domains where I currently have "WHOIS privacy", so my contact info is not revealed in the WHOIS database. I've learned that this arrangement has a significant pitfall, that is, it's the privacy company that really owns the domain, and they license it to me. That seems bad.
I'm not a business, so the only address I can currently list is my home address, which I'm uncomfortable doing.
Therefore, I was thinking about renting a small P.O. box and using that as the address of record. Are there any significant drawbacks of this approach?
One possibility is that people might actually send me snail mail that I need to see, meaning that I might need to actually check the P.O. box instead of ignoring it. Does this happen? (I haven't had any forwarded to me in ~10 years of owning a domain, but that could mean I just haven't caught the attention of folks who would do it.)
Are there other risks or drawbacks?
I have a few e-mail aliases that forward to external hosts. Currently, if the external host rejects a message, Exim generates a bounce message and sends it to the original sender. This is bad because if the external host rejects the message as spam (a common case), then I'm a source of backscatter spam.
Thus, if the sender is non-local, I'd like to send the bounce to postmaster (me) instead. Alternately, sending all bounces to postmaster would be good enough.
The Exim documentation hints that this can be done ("when a message fails to be delivered ... Exim sends a message to the original sender, or to an alternative configured address", emphasis added), but I couldn't find how.
For example, here is a log excerpt showing a backscatter spam being created (in this case, the purported source server isn't accepting connections). [email protected] is the purported sender of a spam e-mail to [email protected], which then forwards to [email protected]; GMail then rejects the message and my server creates a bounce to [email protected]. I want that bounce to go to [email protected] instead. (Usernames obfuscated; the rest of the log is verbatim.)
2011-10-03 12:03:08 1RAkyw-0000cj-45 <= [email protected] H=(gyajnj.com [113.190.35.111] P=esmtp S=33927 [email protected]
2011-10-03 12:03:09 1RAkyw-0000cj-45 ** [email protected] <[email protected]> R=dnslookup T=remote_smtp: SMTP error from remote mail server after end of data: host gmail-smtp-in.l.google.com [74.125.47.26]: 552-5.7.0 Our system detected an illegal attachment on your message. Please\n552-5.7.0 visit http://mail.google.com/support/bin/answer.py?answer=6590 to\n552 5.7.0 review our attachment guidelines. i3si13239001yhk.107
2011-10-03 12:03:09 1RAkyz-0000cm-H5 <= <> R=1RAkyw-0000cj-45 U=Debian-exim P=local S=35124
2011-10-03 12:03:09 1RAkyw-0000cj-45 Completed
2011-10-03 12:03:30 1RAkyz-0000cm-H5 nacha.net [64.212.215.180] Connection timed out
2011-10-03 12:03:30 1RAkyz-0000cm-H5 == [email protected] R=dnslookup T=remote_smtp defer (110): Connection timed out
Here is the relevant router:
dnslookup:
debug_print = "R: dnslookup for $local_part@$domain"
driver = dnslookup
domains = ! +local_domains
transport = remote_smtp
same_domain_copy_routing = yes
# ignore private rfc1918 and APIPA addresses
ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8 : 192.168.0.0/16 :\
172.16.0.0/12 : 10.0.0.0/8 : 169.254.0.0/16 :\
255.255.255.255
no_more
We have Tomcat 5.5 running behind and Apache 2.2 mod_proxy. We would like prettier URLs. For example, this is more or less how our URLs look now:
http://example.com/foo/app/home (home page)
http://example.com/foo/app/bar (other parts of the web app)
http://example.com/foo/api/qux (API hooks)
http://example.com/foo/quux (misc)
We would like the publically exposed URLs to be simpler, e.g.:
http://example.com/ (home page)
http://example.com/bar (other parts of the web app)
http://example.com/api/qux (API hooks)
http://example.com/quux (misc)
I know how to have Apache rewrite the incoming URLs into the longer ones Tomcat uses, but I'm concerned that this might confuse Tomcat. I am reasonably experienced with Apache but a Tomcat newbie.
Also, we want to do this with rewriting, not redirects (e.g., http://example.com/ should not simply redirect to http://example.com/foo/app/home), as we want to keep the ugly URLs out of the address bar entirely.
The new Firefox extension Firesheep highlights the fact that HTTP login sessions can be easily hijacked if the data can be sniffed, which is trivial on an open WiFi network.
I would like to set up something to mitigate this risk for my family. I have a small VPS (256M, currently running lighttpd and SpamAssassin) which I can leverage for this purpose, the basic idea being that when we are using an untrusted network, traffic (at least HTTP) goes over an encrypted tunnel to the VPS before being released onto the open internet.
What are my options given these resources? The clients are all Macs, if that matters. The possibilities I'm aware of are OpenVPN (the key issue being that in the tunnel-all-traffic configuration, it destroys the route to the open network's DHCP server) and an HTTP proxy (of which I know nothing). Are there other options? What considerations and gotchas should I be aware of?
I'd like something on the clients that is easy to just turn on (I am a technical person but the rest of my family is not), and that works for all websites regardless of whether they support HTTPS.