Digital Base – Blog » System Administration

it’s actually quite easy to setup a pptp vpn server for windows/*nix client on a ubuntu serverÂ

first off all we install pptpd ( PoPToP Point to Point Tunneling Server)

[code]install pptpd[/code]

 after that we edit /etc/pptpd.conf

[code]pptpd.conf[/code]

then we edit /etc/ppp/options

[code]options[/code]

and then we edit /etc/ppp/pptpd-options

[code]pptpd-options[/code]

and as last we edit the user file /etc/ppp/chap-secrets

[code]chap-secrets[/code]

and finaly we restart the pptpd using the command:

[code]restart pptpd[/code]

so you see … it’s not that hard to install a microsoft vpn tunnel server on a ubuntu server Â

Because we love the Symfony Open-source PHP Web Framework, we have developed multiple applications with it. For those wo are not familiar with Symfony, take a look at their website for more information.

The scripts of the web directory are the entry points to the application. To be able to access them from the Internet or any given webpage, the web server must be correctly configured. In your development server, as well as in a professional hosting solution, you probably have access to the Apache configuration and you can set up a virtual host :

1
2
3
4
5
6
7
8
9
10
11
12
13
14

<VirtualHost *:80>
 ServerName www.domain.com
 DocumentRoot "/home/diba/myproject/web"
 DirectoryIndex index.php
 Alias /sf /$sf_symfony_data_dir/web/sf
 <Directory "/$sf_symfony_data_dir/web/sf">
   AllowOverride All
   Allow from All
 </Directory>
 <Directory "/home/diba/myproject/web">
   AllowOverride All
   Allow from All
 </Directory>
</VirtualHost>

Setting up an web application on a shared host is a little bit trickier, since
the host usually has a specific directory layout that you can't change, except when you have a webserver at your disposal of course. Let's imagine that your shared host requires that the web folder is named public_html instead of web, and that it doesn't give you access to the httpd.conf file, but only to an .htaccess file in the web folder.

In directadmin you have the option to change/update the virtualhost of a certain domain. The downside of this solution is that whenever you change data related to this domain (safe mode, open basedir, add new domain), the virtualhost will get rewritten, causing your changed to be lost. There is a solution for this, although it requires a small symfony hack.

In a symfony project, every path to a directory is configurable. You can
still rename the web directory to public_html and
have the application take it into account by changing the
configuration. These lines are to be added to
the end of the application config.php file:

1
2
3
4
5
6

$sf_root_dir = sfConfig::get('sf_root_dir');
sfConfig::add(array(
 'sf_web_dir_name' => $sf_web_dir_name = 'public_html',
 'sf_web_dir'      => $sf_root_dir.DIRECTORY_SEPARATOR.$sf_web_dir_name,
 'sf_upload_dir'   => $sf_root_dir.DIRECTORY_SEPARATOR.$sf_web_dir_name.DIRECTORY_SEPARATOR.sfConfig::get('sf_upload_dir_name'),
));

And that's it! Your webapplication will now get it's public content from public_html, and the Symfony framework is smart enough to know that all the other files are one dir above this one. All hail to Sensiolabs!

P.S. If you are doing this because of the directadmin limitations, there is a post you should read.

One of our customers, where we had to build an Intranet system already had a Windows Network, including NT Servers and SQL databases. All the user credentials were stored in the local Active Directory. So, it would be nice to use all this information for the intranet, so Administrators and staff employees did not need to insert and maintain the same information twice. This is were SSPI comes in.

mod_auth_sspi is a module written for Apache webserver. It allows Microsoft Internet Explorer, and Windows clients to authenticate using any of the authentication protocols built into the Windows Security Support Provider Interface (SSPI), for example in combination with Active Directory and Windows Domains. So it allows an Apache/NT web server administrator to use the existing NT security infrastructure to authenticate users.

Mod_auth_sspi processes user access restrictions just like the rest of Apache. That is, you put a require directive into the appropriate .htaccess or configuration section, and authentication will be performed.

[code]sspi apache[/code]

Mod_auth_sspi is probably most useful in intranets. Authentication can happen transparently, using the user's current username and password – however, basic authentication is still supported.

SourceForge SSPI module website

By default the scp/sftp support is not installed when running krusader in a gnome environment). If your 'new net connection' only lists ftp, this is the case for you.

This means you are missing some kde libraries allowing krusader (or other kde apps) to use the scp/sftp protocol

[code]gutsy - krusader fix[/code]

This should do the trick..