26 Sep
Posted by jj as Web Server, Windows
Depending on how your server is set up, you may or may not have Microsoft IIS installed. IIS is a mandatory install if you want to use Helm. It is used to host the Helm website, and will also host any websites you wish to create.
Note:- These are guidelines only. We will not provide support for IIS or any other 3rd party applications directly.
1.) Go to Start > Control Panel > Add/Remove Programs > Add/Remove Windows Components.
2.) Double-click Application Server.
3.) You will see that Internet Information Services (IIS) is not checked. Check the box. Press “OK”.
Read the rest of this entry »
This guide will walk you through the setup process and installation steps for eFront version 3.1.3. SiteGround and cPanel were selected as reference, but the procedure is pretty much the same for any hosting provider. The guide assumes you have some experience in using cPanel as well as setting up a domain. For the sake of the examples, we will use the “venakis.org” domain.
Read the rest of this entry »
What is XAMPP?
I decided that the quickest way to get you up and running with your own web server would be to use Apache Friend’s XAMPP. XAMPP is an application that combines Apache (the web server), MySQL (database), PHP (scripting language) and phpMyAdmin (database administration) all into one.
Read the rest of this entry »
How to create & maintain a “Virtual Home Page” on the Elks.org web site. What is a Virtual Home Page? A Virtual Home Page (VHP) is a fast, simple, and inexpensive way to put your lodge on the Internet. Just submit a few simple online forms, and you’ll have an effective web presence within the Grand Lodge web site, http://www.elks.org. What kind of information can we post on our lodge Virtual Home Page? Each Virtual Home Page includes space for: • Lodge News.
Read the rest of this entry »
16 Feb
Posted by jj as Security, Web Server
Lock down the box! Solution: 1. Turn on encryption 2. Lock down console line 3. Lock down telnet / ssh / ACL for access 4. Configuring local usernames and secret passwords 5. The QUICK N DIRTY Script 1. Turn on encryption To ensure that passwords are not shown in the config files in clear text, turn on password encryption.
Read the rest of this entry »
16 Feb
Posted by jj as Security, Web Server
This tutorial demonstrates how to use the SSH Secure File Transfer client for Windows to copy files from a local computer to the Student Organizations Server. The example uses http://www.clubs.psu.edu/up/clubs_example/, as the Web address for an example organization at University Park. Organizations that use http://www.greeks.psu.edu/ in their Web address have “up” as their campus code. A fraternity with a Web address of http://www.greeks.psu.edu/ifc/aaa/ has the directory path /clubs/up/aaa.
Read the rest of this entry »
Remotely logging on to machines is a very common task The most common programs to login were telnet, rsh and rlogin Networks, and LANs in particular, are insecure If a group of computers are connected in a lab, any computer in the lab can see all the data sent across the network Authentication is the process of proving an identity To access a computer, you provide an account name and something that proves you are allowed to access it Passwords are the normal method for authentication Passwords must be protected and this is difficult across a network telnet and friends send login names and passwords in plain text
Read the rest of this entry »
16 Feb
Posted by jj as Security, Web Server
Secure shell (SSH) can safely be called one of the rare successes in which a more secure technology has largely replaced a less secure but entrenched tool: telnet. We perform a market analysis to determine how and why SSH succeeded despite the existence of an entrenched legacy tool while similar technologies such as secure file transfer protocols have been far less successful. We show that network externalities, usually a first order effect, were not a significant factor impeding the adoption of SSH, and that SSH offered equivalent functionality and greater ease of use. We argue that these factors were the primary consideration in the willingness to change.
Read the rest of this entry »