Home / user-188995

John Crawford's questions

Martin Hope
John Crawford
Asked: 2015-07-31 05:27:13 +0800 CST
  • 0

I currently have the following in my config file:

ServerName example.com
ServerAlias www.example.com
ServerAlias www.example.org
ServerAlias www.example.co.uk

This all works great because if I go to www.example.org/something I get redirected to http://example.com/something The only problem is that the redirection that occurs is "temporary" ie: 302 instead of 301.

How can I change this so that it will be a 301 instead while still using the very popular ServerAlias command?

redirect
Martin Hope
John Crawford
Asked: 2013-10-30 13:51:36 +0800 CST
  • 127

I've just update my Apache server to Apache/2.4.6 which is running under Ubuntu 13.04. I used to have a vhost file that had the following:

<Directory "/home/john/development/foobar/web">
    AllowOverride All 
</Directory>

But when I ran that I got a "Forbidden. You don't have permission to access /"

After doing a little bit of googling I found out that to get my site working again I needed to add the following line "Require all granted" so that my vhost looked like this:

<Directory "/home/john/development/foobar/web">
    AllowOverride All 
    Require all granted
</Directory>

I want to know if this is "safe" and does not bring in any security issues. I read on Apache's page that this "mimics the functionality the was previously provided by the 'Allow from all' and 'Deny from all' directives. This provider can take one of two arguments which are 'granted' or 'denied'. The following examples will grant or deny access to all requests."

But it didn't say if this was a security issue of some sort or why we now have to do it when in the past you did not have to.

apache-2.2
Martin Hope
John Crawford
Asked: 2013-09-15 13:07:38 +0800 CST
  • 0

I took a look at the Canonical Topics ServerFault has and sadly the one I was after "Apache vHost" was on the list of unanswered questions. I found this a little surprising as there are loads of people asking just that question.

Anyway, my question isn't so much about "how" but rather what are the "best practises" to use in a Virtual Host configuration file? I have the following virtual host:

<VirtualHost *:80>
    ServerName example.com
    DocumentRoot /home/webmaster/examplesite.com/htdocs
    ErrorLog /home/webmaster/examplesite.com/logfiles/error.log
    CustomLog /home/webmaster/examplesite.com/logfiles/access.log combined
</VirtualHost>

It does the job and gets things working, however I wanted to know if I could improve on it. In particular I would like to make sure that the following issues are dealt with:

  • How secure is my site?
  • I would like to have an "uploads" folder where users can post images to. Do I need to add something to the vHost file?
  • Does the above setting optimise my website, or can I optimise it further?
  • Anything else I may have missed?
apache-2.2
Martin Hope
John Crawford
Asked: 2013-09-15 01:13:26 +0800 CST
  • 48

What does the ServerAliveCountMax in SSH actually do?

I am trying to ensure that when I connect to my server via SSH that the connection remains open for a long period of time instead of the connection dying after a short period of inactivity. This is the example 

Host *
    ServerAliveInterval 60
    ServerAliveCountMax 2

I've heard from one source that the above setting will always send a response to the server every 60 seconds so long as the server receives that response. However if for whatever reason the response doesn't go through to the server, it will try and send another message. If that message fails too, then it will close the connection. (I feel this is wrong)

The second and third source however say something different. They claim that a message will be sent to the server every 60 seconds if there is a period of inactivity, but it will only send through 2 requests and then it will close the connection.

So what exactly does ServerAliveCountMax do?

ssh
Martin Hope
John Crawford
Asked: 2013-09-08 04:29:48 +0800 CST
  • 1

I have written a script that installs a LAMP environment and a few other helpful programs. All of this has been installed under root.

I would now like to create a new user called webmaster that will only be responsible for rendering my website located under: /home/webmaster/htdocs. As such I have created a new user called "webmaster".

When I run a "ls" on the htdocs folder I get the following output:

-rw-rw-r--  1 webmaster www-data  1843 Aug 26 21:12 composer.json
drwxrwsr-x  3 webmaster www-data  4096 Aug 26 21:12 src

Should the group really be owned by www-data or should I change the group to www-data and then simply add the Apache user, www-data, to the "webmaster" group? What is the best method with regards to security?

apache-2.2