Web page - Revision history

imported>Huston: /* Password protection */ openssl is easier than htpasswd, and everything is SSL enabled now so no cleartext worries.

2024-01-08T18:01:59Z

Password protection: openssl is easier than htpasswd, and everything is SSL enabled now so no cleartext worries.

← Older revision		Revision as of 18:01, 8 January 2024
Line 20:		Line 20:
	require valid-user		require valid-user

	Then your .htpasswd file. From a Linux workstation, run ~~'<tt>/usr/peyton/bin/htpasswd</tt>' to create the file (it should be in your $PATH already).~~ ~~'<tt>htpasswd~~ -~~c .htpasswd myfiles</tt>' will create the .htpasswd file in the current directory, and add a user 'myfiles'. You will then be asked for the password just like~~ passwd~~(1) does, and it will create the file. Now when you mouse over to that page, you'll get the nice popup window that says~~ "~~Please enter username and password for 'Whatever You Want To Call It'~~" ~~(or whatever you typed in for 'AuthName' in .htaccess). Enter the username you gave on the command line for htpasswd, and then the password, and it should let you view whatever is in that directory.~~		Then your .htpasswd file. From a Linux workstation, run:
			read -p "Username: " U ; P=`openssl passwd -apr1` ; echo "${U}:${P}"

	~~'''NOTE:'''~~		This will create the data that you should put in the .htpasswd file you specified in .htaccess. You will be asked for the user name and password. Create the .htpasswd file with that data, or add it to the existing file if you're creating another user/password combination. Now when you mouse over to that page, you'll get the nice popup window that says "Please enter username and password for 'Whatever You Want To Call It'" (or whatever you typed in for 'AuthName' in .htaccess). Enter the username you gave in the read/OpenSSL command above, and then the password, and it should let you view whatever is in that directory.
	: This user name/password combination ~~is transmitted~~ in ~~clear text (readable by anyone~~ in ~~between~~)~~, and so is not at all secure~~. ~~It will stop~~ the ~~casual browser from getting into your area~~, ~~however will do nothing to~~ the ~~determined cracker~~.

imported>Huston at 15:25, 7 January 2022

2022-01-07T15:25:31Z

← Older revision		Revision as of 15:25, 7 January 2022
Line 1:		Line 1:
	Every account in Peyton Hall can have its own ~~home page~~ for others to see. This article will teach you a little about how to set it up, and what kinds of things you can do.		Every account in Peyton Hall can have its own web site for others to see. This article will teach you a little about how to set it up, and what kinds of things you can do.


	== Getting started ==		== Getting started ==
	To create your ~~home page~~, create the directory ~/WWW/public: '<tt>mkdir -p ~/WWW/public</tt>' will do the trick. Some places use the more standard ~/public_html, but since our web server was setup a long time ago to use this directory for pages, the tradition has carried over. Any files you place in this directory will be viewable at <nowiki>http://www.astro.princeton.edu/~<your username>/</nowiki>. If you want a page to display by default when someone uses that URL, name that page '<tt>index.html</tt>'.		To create your web site, create the directory ~/WWW/public: '<tt>mkdir -p ~/WWW/public</tt>' will do the trick. Some places use the more standard ~/public_html, but since our web server was setup a long time ago to use this directory for pages, the tradition has carried over. Any files you place in this directory will be viewable at <nowiki>http://www.astro.princeton.edu/~<your username>/</nowiki>. If you want a page to display by default when someone uses that URL, name that page '<tt>index.html</tt>'.

imported>Huston: Huston moved page Home page to Web page: Nobody calls them home pages anymore

2022-01-07T15:23:03Z

Huston moved page Home page to Web page: Nobody calls them home pages anymore

← Older revision	Revision as of 15:23, 7 January 2022
(No difference)

imported>Huston at 20:30, 21 May 2007

2007-05-21T20:30:19Z

← Older revision		Revision as of 20:30, 21 May 2007
Line 9:		Line 9:
	If your page is not displaying, there's a few things to consider. Apache needs to be able to read the file itself, as it does not run as you but with its own user ID. This means that anyone needs to be able to access the directory and read the file, so having permissions set to lock out your home directory will also lock out Apache. Make sure that your home directory permissions are 755 (drwxr-xr-x) as are the subdirectories in question (~/WWW and ~/WWW/public). '<tt>chmod 755 ~ ~/WWW ~/WWW/public</tt>' will do that for you.		If your page is not displaying, there's a few things to consider. Apache needs to be able to read the file itself, as it does not run as you but with its own user ID. This means that anyone needs to be able to access the directory and read the file, so having permissions set to lock out your home directory will also lock out Apache. Make sure that your home directory permissions are 755 (drwxr-xr-x) as are the subdirectories in question (~/WWW and ~/WWW/public). '<tt>chmod 755 ~ ~/WWW ~/WWW/public</tt>' will do that for you.

	Also, the files themselves have to be readable by all, so make sure their mode is 644 (-rw-r--r--). Again, '<tt>chmod 644 index.html</tt>' is an example of how to do that.		Also, the files themselves have to be readable by all, so make sure their mode is 644 (-rw-r--r--). Again, '<tt>chmod 644 index.html</tt>' is an example of how to do that. See [[chmod]] for more information on file and directory modes.

imported>Huston: New page: Every account in Peyton Hall can have its own home page for others to see. This article will teach you a little about how to set it up, and what kinds of things you can do. == Getting s...

2007-05-21T16:27:40Z

New page: Every account in Peyton Hall can have its own home page for others to see. This article will teach you a little about how to set it up, and what kinds of things you can do. == Getting s...

New page

Every account in Peyton Hall can have its own home page for others to see. This article will teach you a little about how to set it up, and what kinds of things you can do.

== Getting started ==
To create your home page, create the directory ~/WWW/public: '<tt>mkdir -p ~/WWW/public</tt>' will do the trick. Some places use the more standard ~/public_html, but since our web server was setup a long time ago to use this directory for pages, the tradition has carried over. Any files you place in this directory will be viewable at <nowiki>http://www.astro.princeton.edu/~<your username>/</nowiki>. If you want a page to display by default when someone uses that URL, name that page '<tt>index.html</tt>'.

== Access problems ==
If your page is not displaying, there's a few things to consider. Apache needs to be able to read the file itself, as it does not run as you but with its own user ID. This means that anyone needs to be able to access the directory and read the file, so having permissions set to lock out your home directory will also lock out Apache. Make sure that your home directory permissions are 755 (drwxr-xr-x) as are the subdirectories in question (~/WWW and ~/WWW/public). '<tt>chmod 755 ~ ~/WWW ~/WWW/public</tt>' will do that for you.

Also, the files themselves have to be readable by all, so make sure their mode is 644 (-rw-r--r--). Again, '<tt>chmod 644 index.html</tt>' is an example of how to do that.

== Password protection ==
You can have your page, or parts of it, password protected so that someone needs to type a password to see it. This might be useful if you have some collaborators you wish to give access to some data, but not have it show up in search engines or viewable by the general public. Start by creating a directory, with normal permissions. Inside that directory, you'll want to create two files, .htaccess and .htpasswd. .htaccess should look something like this:

AuthUserFile /u/user/WWW/public/your/directory/.htpasswd
AuthName "Whatever You Want To Call It"
AuthType Basic
require valid-user

Then your .htpasswd file. From a Linux workstation, run '<tt>/usr/peyton/bin/htpasswd</tt>' to create the file (it should be in your $PATH already). '<tt>htpasswd -c .htpasswd myfiles</tt>' will create the .htpasswd file in the current directory, and add a user 'myfiles'. You will then be asked for the password just like passwd(1) does, and it will create the file. Now when you mouse over to that page, you'll get the nice popup window that says "Please enter username and password for 'Whatever You Want To Call It'" (or whatever you typed in for 'AuthName' in .htaccess). Enter the username you gave on the command line for htpasswd, and then the password, and it should let you view whatever is in that directory.

'''NOTE:'''
: This user name/password combination is transmitted in clear text (readable by anyone in between), and so is not at all secure. It will stop the casual browser from getting into your area, however will do nothing to the determined cracker.