426 reputation
1722
bio website bitlucid.com
location New York, NY
age 34
visits member for 4 years, 10 months
seen Jul 3 at 22:22

I'm hirable at bitlucid.com, train ninjas at ninjawars.net, do crazy art when I can at dnaexmosn.deviantart.com, and code stuff at github.com/tchalvak

Code in:

  • html/css (come on, tell me webdesign isn't coding, dare ya)
  • javascript
  • php

Want to code in: - Clojure

Want to code on: - node.js

Formerly Tchalvak


Jul
25
comment Our security auditor is an idiot. How do I give him the information he wants?
@Reid Oh no, what a waste of the digitals! All those tubes!
Jul
23
comment Our security auditor is an idiot. How do I give him the information he wants?
I disagree with giving anything to this clearly unsecure individual.
Jul
7
comment Dealing with development subdomains
Whoops, I was wrong, that password-protected the main site as well.
Jul
7
comment Dealing with development subdomains
Looks like I had to specify the url in the virtualhost as per: <VirtualHost dev.shermanbrothers.com:80>`, but it was indeed messing with the virtualhost line that solved it.
Jul
6
comment Dealing with development subdomains
I don't believe so because I have to specifically add each and every domain (annoyingly). Perhaps it's a problem with that default virtualhost being met first, though. Not sure of what slick way to solve it that is.
Jul
6
comment Dealing with development subdomains
Yeah, I just put the site back into my question, easier that way. (It's dev.shermanbrothers.com and shermanbrothers.com).
Jul
6
comment Dealing with development subdomains
Yeah, I should have specified that going to the url shows the same result. Hell, I'll just put the url in the question. I updated the question to explain that the same result is being displayed for dev.shermanbrothers.com and shermanbrothers.com
Jul
6
comment Dealing with development subdomains
No difference if it's in my hosts file pointed at the server's ip address.
Jul
6
comment Dealing with development subdomains
Sorry, should have clarified that it it showing the same content as example.com. I'll add the dev url to my hosts and see what happens.
Jul
6
comment Dealing with development subdomains
Ah, a tool for creating the symlink in the /etc/apache2/sites-enabled/ directory, yeah, I've got a manually created symlink in there that maps to the latter config.
Jul
6
comment Dealing with development subdomains
I have indeed restarted apache. a2ensite I haven't heard of before, so I expect no. I am wondering whether I have to set up a wildcard subdomain with the DNS or whatever. Not sure what is best practice there.
Jun
24
comment How do I protect my company from my IT guy?
-1 for: "I made sure they didn't change anything without us knowing about it."
May
23
comment How do I configure the default email sender properties on a debian server?
Using /etc/email-addresses definitely ended up solving my problem, gracias.
May
20
comment Via logwatch, I get messages that root is opening sessions “-> nobody”. Is this a security concern, or normal operation?
Hmmm, okay, so that may be indicative of the configuration still allowing attempts on the root account's password, good to know.
May
20
comment logwatch explanation
A default install of denyhosts will slow down that type of cracking attempt as well.
May
20
comment Via logwatch, I get messages that root is opening sessions “-> nobody”. Is this a security concern, or normal operation?
Ok, just wanted to make sure. Just a little bit of a follow up question, even in the cases where root login is disabled (my intent and the way that I have configured ssh, as well as denyhost), do those authentication failure messages still occur?
May
11
comment apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
For the -default- virtualhost, not just a specific virtualhost.
May
4
comment non-www domains prevent hosting of static content on the same domain, correct?
I don't really see the cost of another domain as the biggest issue, more like the maintenance & monitoring of another domain. Certainly it's not a major difference, but it's one I'm trying to quantify.
May
4
comment non-www domains prevent hosting of static content on the same domain, correct?
Fair enough, that sounds about right.
May
3
comment non-www domains prevent hosting of static content on the same domain, correct?
That is true. I guess what I meant was: If you use example.com as your canonical url, and you use cookies, then the cookie will be set to use example.com as it's base. Which I will rephrase. Certainly this isn't a problem for sites that don't use cookies at all, and won't ever use cookies in the future.