I googled a lot about configuring SVN repository with Apache server and thought that I should write my experience on how i succeeded in configuring it

A Preface:
I earlier used SVN server with IIS by running a SVN service, it really messed up a lot(or atleast with the info that I had) and most of the time I happen to netwrk-share my SVN repos directory and connect from other machines, then we decided to move our SVN to a apache web server…so here is the configuration details…

What you need ?
1) Apache 2.x
2) SVN
3) Tortoise SVN Client

1) Install apache – you can change the default port number(80) if you have IIS running on that machine.
http://httpd.apache.org/download.cgi
2) Install SVN – i used this MSI for installation Setup-Subversion-1.6.4.msi
3) Install Tortoise SVN – On the client machine – we dont need this on teh server unless you want to have a working directory(for build purpose, more of this in my next article) on your server
tortoisesvn.net/downloads

– after all this restart your machine once(not needed if you are using a windows server, if you are using XP then restart is advisable)

Create repository -this is the easiest of all the tasks
Create a directory – C:\SourceCodeRepos
once you have installed SVN you will find the bin folder contains svnadmin, use this to create a repos
open command Prompt> svnadmin create “C:\SourceCodeRepos”
(if you get an error bad command or filename then add the SVN bin path to the environment variables Mycomputer –> right click –> props –> Env Variables –> Path –> Edit –> dont overwrite the existing one–> copy the bin path of SVN in the end.)

Configure APACHE – a little less easier than the prev one
apache step 1)
Create a folder c:\etc — this directory will hold the config files of your SVN repos and apache auth files.

Create three files inside this directory (c:\etc)
a) File name: subversion.conf
Content of the file

DAV svn
SVNPath C:\SourceCodeRepos

AuthType Basic
AuthName “Subversion Kinetics repository”
AuthUserFile c:/etc/svn-auth-file

Require valid-user

AuthzSVNAccessFile c:/etc/svn-acl

b) File Name: svn-acl
Content:
# groups foes here
[groups]
developers = username1,username2,username3

# developers group has a read/write access to source code repository
[SourceCodeRepos:/]
@developers = rw
* = r

c) File name: svn-auth-file
no content for this file…

apache step 2)
copy the modules “mod_authz_svn.so” and “mod_dav_svn.so” to your apache modules directory
c:\Program Files\Apache Software Foundation\Apache2.2\modules\

apache step 3)
Add these lines to you httpd.conf (located at c\Program Files\Apache Software Foundation\Apache2.2\conf)
LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so

apache step 4) add this line to the end of the same file (httpd.conf)
Include c:/etc/subversion.conf
#this step will load the SVN configuration of our repos to apache

restart your apache server…

we are almost done…
the final step is to create usernames and store them in the auth file
here is the step to create username using htpasswd

htpasswd -m “c:\etc\svn-auth-file” ausername
a help link is here
http://httpd.apache.org/docs/2.0/programs/htpasswd.html
(the htpasswd is available under the apache directory)

Check the URL by typing
http://localhost/SourceCodeRepos – you must be prompted with a username and password, if it is so then you have succeeded, congratulations !!

now from any client machine you can access the repos using the url
http://servername/SourceCodeRepos…
use TortoiseSVN to access the repos URL…

I will be glad to help you in any step, do let me know…

APACHE!

For min gamle kollega og venn Rune Gerhardsen kommer høydepunktet tidlig denne uken. Det kommer allerede i kveld. For i kveld er det Shadows-konsert i Oslo Spektrum. Og Rune og kona sto først i billettkøen, og slo kloa i de to første billettene da salget startet. Tar jeg ikke feil blir det nachspiel hjemme på Nordseter etter konserten med Rune selv i rollen som Hank Marvin (sologitarist).

Få grupper har drevet på like lenge som Shadows, og få har like mange hits. Den største er instrumentallåten ”Apache”. Den skal Rune ha i begravelsen sin. Jeg håper det blir lenge til.

Hold fast og hold ut!

Hans

Ord: Hans Geelmuyden
Hele kalenderen for uke 48 finner du her

You can install SSL on default services(http, exim, imap, pop3, cpanel/WHM) from your WHM but you require root login details to

The all cert information save in following path

/var/cpanel/ssl/

You can install the certificate from your WHM >>  Main >> Service Configuration >> Manage Service SSL Certificates

เวลาเอา web app ที่เขียนด้วย cakephp ไปใส่ใน userdir เช่น /home/veer/public_html/myapp (ซึ่งมักจะไปตรงกับ url http://hostname/~veer/myapp) มักจะมีปัญหากับ mod_rewrite ขึ้นมา แต่ก็แก้ไม่ยาก เพียงแต่แก้ .htaccess ใน myapp กับ myapp/app/webroot

เดิมทีจะเขียนไว้ประมาณนี้ (ใน myapp กับ myapp/app/webroot ไม่เหมือนกัน แต่ก็แก้เหมือนกัน)

   RewriteEngine on
   RewriteRule    ^$ app/webroot/    [L]
   RewriteRule    (.*) app/webroot/$1 [L]

ก็แก้โดยใส่ RewriteBase เข้าไปเป็นแบบนี้

   RewriteEngine on
   RewriteBase    /~veer/myapp
   RewriteRule    ^$ app/webroot/    [L]
   RewriteRule    (.*) app/webroot/$1 [L]

เสร็จแล้ว

Have been very busy at work lately.  We made the decision about a month ago to switch (most|all) new projects over to use Python 3 with Apache, mod_wsgi, and AppStruct.  You may know what the first 3 are, but the 4th??

Special thanks goes to Graham Dumpleton behind mod_wsgi, and James William Pye behind Python>>Postgresql.   They are not involved or affiliated with AppCove or AppStruct (aside from great mailing list support) BUT if it were not for them, this framework would not exist.

AppStruct is a component of Shank, a meta-framework.  A stand-alone component in it’s own right, it represents the AppCove approach to web-application development.  Most of it is in planning, but the parts that have materialized are really, really cool.

Briefly, I’ll cover the two emerging areas of interest:

AppStruct.WSGI

This is a very pythonic (in my opinion) web application framework targeted toward Python 3.1 (a challenge in itself at this point).  We really wanted to base new development on Python 3.1+, as well as PostgreSQL using the excellent Python3/PostgreSQL library at http://python.projects.postgresql.org/.  However, none of the popular frameworks that I am aware of support Python 3, and most (if not all) of them have a lot of baggage I do not want to bring to the party.

Werkzeug was the most promising, but alas, I could not find Python 3 support for it either.  In fact, I intend to utilize a good bit of code from Werkzeug in finishing off AppStruct.WSGI.  (Don’t you just love good OSS licences?  AppStruct will be released under one of those also).

HTTP is just not that complicated.  It dosen’t need bundled up into n layers of indecipherable framework upon framework layers.   It doesn’t need abstracted to death.  I just needs to be streamlined a bit (with regard to request routing, reading headers, etc…).

Python is an amazing OO language.  It’s object model (or data model) is one of (if not the) most well conceived of any similar language, ever.  I want to use that to our advantage…

Inheritance, including multiple inheritance, has very simple rules in Python.  Want to use that as well.

Wish to provide developers with access to the low level guts they need for 2% of the requests, but not make them do extra work for the 98% of requests.

Speed is of the essence.  Servers are not cheap, and if you can increase your throughput by 5x, then that’s a lot less servers you need to pay for.

So, how does it work?

Well, those details can wait for another post.  But at this point the library is < 1000 lines of code, and does a lot of interesting things.

• A fully compliant WSGI application object
• 1 to 1 request routing to Python packages/modules/classes
• All request classes derived from AppStruct.WSGI.Request

The application maps requests like /some/path/here to objects, like Project.WSGI.some.path.here.  If there is a trailing slash, then the application assumes that the class is named Index.  The object that is found is verified to be a subclass of AppStruct.WSGI.Request, and then…

Wait!  What about security?

Yes, yes, very important.  A couple things to point out.  First, the URLs are passed through a regular expression that ensures that they adhere to only the characters that may be used in valid python identifiers (not starting with _), delimited by “/”.  Second, the import and attribute lookup verify that any object (eg class) found is a subclass of the right thing.  And so on and so forth…

But you may say “wait, what about my/fancy-shmancy/urls/that-i-am-used-to-seeing?  Ever hear of mod_rewrite?  Yep.  Not trying to re-invent the wheel.  Use apache for what it was made for, not just a dumb request handler.

What about these request objects?

They are quite straightforward.  There are several attributes which represent request data, the environment, query string variables, post variables, and more.  There is a .Response attribute which maps to a very lightweight response object.

Speaking of it — it has only 4 attributes: [Status, Header, Iterator, Length].  As you see, it’s pretty low-level-wsgi-stuff.  But the developer would rarely interact with it, other than to call a method like .Response.Redirect(‘http://somewhere-else.com’, 302)

Once the application finds the class responsible for handling the URL, it simply does this (sans exception catching code):

RequestObject = Request(...)

with RequestObject:
   RequestObject.Code()
   RequestObject.Data()

return RequestObject.Response

Wow, that’s simple.  Let me point out one more detail.  The default implementation of Data() does this:

def Data(self):
   self.Response.Iterator = [self.Text()]
   self.Response.Length = len(self.Response.Iterator[0])

So the only thing really required of this Request class is to override Text() and return some text?  Yep, that simple.

But typically, you would at some point mixin a template class that would do something like this:

class GoodLookingLayout:
   def Text(self):
      return ( 
         """<html><head>...</head><body><menu>""" +
         self.Menu() +
         """</menu><div>""" +
         self.Body() +
         """</div></body></html>"""
         )

And then it would be up to the developer to override Menu and Body (each returning the appropriate content for the page).

Ohh, you may say.  What about templating engine X?  Well, it didn’t support Python 3, and I probabally didn’t want it anyway (for 9 reasons)…  If it’s really, really good and fits this structure, drop me a line, please.

What about that Code() method?

Yeah, that’s the place that any “logic” of UI interaction should go.  I’m not advocating mixing logic and content here, but you could do that if you wanted.  You will find in our code, a seperate package for application business logic and data access that the request classes will call upon.  But again, if you are writing a one page wonder, why go to all the trouble?

The only requirement for the Code() method is that it calls super().Code() at the top.  Since the idea is that the class .Foo.Bar.Baz.Index will inherit from the class .Foo.Bar.Index, this gives you a very flexible point of creating .htaccess style initialization/access-control code in one place.  So in /Admin/Index, you could put a bit of code in Code() which ensures the user is logged in.  This code will be run by all sub-pages, therefore ensuring that access control is maintained.  Relative imports are important for this task.

from .. import Index as PARENT
from AppStruct.WSGI.Util import *

class Index(PARENT):
   def Code(self):
      super().Code()
      self.Name = self.Post.FirstName + " " + self.Post.LastName
      # some other init stuff
   def Body(self):
      return "Hello there " + HS(self.Name) + "!"

Summary of AppStruct.WSGI…

To get up and running with a web-app using this library:

1. A couple mod_wsgi lines in httpd.conf
2. A .wsgi file that has 1 import and 1 line of code
3. A request class in a package that matches an expected URI (myproject.wsgi.admin.foo ==  /admin/foo)

Speed?

With no database calls, it’s pushing over 2,000 requests per second on a dev server.  With a couple PostgreSQL calls, it is pushing out ~ 800 per second.

AppStruct.Database.PostgreSQL

This is not nearly as deep as the WSGI side of AppStruct, but still really cool.  To start off, I’d like to say that James William Pye has created an amazing Postgresql connection library in Python 3.  I mean just amazing.  In fact, almost so amazing that I didn’t want to change it (but then again…)

What we did here was subclass the Connection, PreparedStatement, and Row classes.  (well, actually replaced the Row class).

Once these were subclassed, we simply added a couple useful features.  Keep in mind that all of the great functionality of the underlying library is retained.

Connection.CachePrepare(SQL)
Connection._PS_Cache

Simply a dictionary of {SQL: PreparedStatementObject} that resides on the connection object.  When you directly or indirectly invoke CachePrepare, it says “if this SQL is in the cache, return the associated object.  Otherwise, prepare it, cache it, and return it”.  This approach really simplifies the storing of prepared statement objects in a multi-threaded environment, where there is really no good place to store them (and be thread safe, connection-failure safe, etc…)

Connection.Value(SQL, *args, **kwargs)
Connection.Row(SQL, *args, **kwargs)

These simple functions take (SQL, *args, **kwargs) and return either a single value or a single row.  They will raise an exception is != 1 row is found.  They make use of CachePrepare(), so you get the performance benefits of prepared statements without the hassle.  More on *args, **kwargs later under PrePrepare()

Connection.ValueList(SQL, *args, **kwargs)
Connection.RowList(SQL, *args, **kwargs)

Same as above, except returns an iterator (or list, not sure) of  zero or more values or rows.

Row class

Simply a dictionary that also supports attribute style access of items.  After evaluating the Tuple that behaves like a mapping, I decided for our needs, a simple dict would be a better representation of a row.

Connection.PrePreprepare(SQL, args, kwargs) -> (SQL, args)

Ok, so what’s the big deal?  Well, the big deal is that we don’t like positional parameters.  They are confusing to write, read, analyze, and see what the heck is going on when you get about 30 fields in an insert statement.  Feel free to argue, but maybe I’m not as young as I once was.

We do like keyword parameters.  But postgresql prepared statement api uses numeric positional parameters.  Not changing that…

The most simple use case is to pass SQL and keyword arguments.

"SELECT a,b,c FROM table WHERE id = $id AND name = $name"
dict(id=100, name='joe')

It returns

"SELECT a,b,c FROM table WHERE id = $1 AND name = $2"
(100, "joe")

Which is suitable for passing directly into the Connection.prepare() method that came with the underlying library.

I don’t know about you, but we find this to be very, very useful.

If you pass tuples of (field, value) as positional arguments, then they will replace [Field], [Value], and [Field=Value] (in the SQL) with lists of fields, lists of values (eg $1, $2), or lists of field=values (eg name=$1, age=$2).  That really takes the verbosity out of INSERT and UPDATE statements with long field lists.

Conclusion

This is just in the early stages, and has a good deal of polishing to be done (especially on the WSGI side).  My purpose here was to introduce you to what you can expect to get with AppStruct, some of the rationale behind it, and that it’s really not that hard to take the bull by the horns and make software do what you want it to (especially if you use python).

Feel free to comment.

Então, agora estou de volta ao quarto. O zumbi já foi embora.

– É a última vez Luciano. Você entende? Última vez que a gente transa.

Líria me fala isso olhando fixamente para meus olhos. Os seus tem uma linda coloração que oscila entre o verde e o amarelo. Desnecessariamente aponta o dedo para meu rosto. Toda a coisa tem um tom de ameaça. Eu só penso em como seus seios são duros, e como os desejo senti-los junto a mim.

– Ok. Última vez Líria. Sem problema. Dá pra continuar a viver assim. Só acho meio anticlimático você falar isso agora…

– É só pra você saber. Acho importante que você saiba. É a ultima vez.

Sinto-me automaticamente impotente. Queria acender um cigarro antes de começarmos. Mas acho difícil que Líria aceite essa pausa. Penso que se é a última vez, devo fazer a melhor apresentação da minha vida. Memorável. Mas não sei lidar bem a pressão.

– Ai, para Lu. Você tá muito afoito. Parece um adolescente. Que que tá pegando?

Líria não sabe, mas minha cabeça está longe dali. Mui longe. Penso que não estou sendo afoito. Estou sendo voluptuoso. Isso costumava agradar as moças.

(escrevendo sobre isso, com o distanciamento que o tempo impõe… Tudo muito estranho).

Nelson R. senta na cama. Sendo um escritor morto em 1980 (e meu irmão d´alma) ele é em preto-e-branco. Se bem que toda a atmosfera do quarto está escura.

- Luciano, acho que você devia ir pra casa (acendo um de seus indefectíveis mata-ratos). Na realidade, eu não existo. Disso você sabe, sou só uma representação literária da sua esquizofrenia dormente. Aquele que você queria dialogar, nos muitos momentos em que duvida. Nas muitas horas em que acha que nenhum ser vivo vai te entender. Mas como estamos numa página de ficção, eu posso te aconselhar. Vai embora daqui.

– Nelson, agora não. Dá-me um trago e vai embora (falo isso durante a cópula. Vez em quando percebo um tom de enfado nos lindos olhos de Líria).

- Luciano. Escuta. É importante que você me escute. Você sabe que eu assisti a morte do meu irmão Roberto. Assassinado. Lembra aquela vez em que você sonhou que eu estava ao seu lado, materialmente físico? Então. Naquele sonho eu te contei isso. A morte de Roberto me marcou eternamente. Ver ele baleado, como um cão sarnento… Essas coisas ficam pra sempre.

– Porra Nelson, eu to transando velho! Saí fora. Para de falar em morte, cacete! Tu é mórbido pacas!

- Claro que eu sou mórbido. Você já leu tudo que eu escrevi. Sempre acaba em desgraça. Mas escuta, acho melhor você ir pra casa, e…

-Puta merda! SAI FORA!

Sinto o jorro dormente dentro de meu órgão do sexo, prestes a eclodir. Com um pré medo da vergonha, do medo de decepcionar Líria, o seguro inutilmente.

– Não, pelo amor de Deus, agora não.

– Hahahaha.

Líria solta aquela sua risada sonora, de encher o ambiente. Dá-me um beijo carinhoso.

– É Luciano. Essa sua última vez foi rápida hein?  Pelo menos foi bom pra você?

Paralisado de prazer, simplesmente fico de bruços, e enfio minha cara no travesseiro de Líria. Lembro-me com ternura nostálgica que algumas das meninas da minha vida, sempre elogiavam meu cheiro, que ficava presente em suas roupas de cama. Mesmo depois que eu já era lembrança, há muito tempo.

Peço desculpas a Líria. Ela não entende que seu nome remete a muita coisa. Que ela é ela (e a amei por um momento), e que ela é todas. Vejo-a andar pelo quarto, nua. É muito bela. É bonita pra caralho. Iria vê-la cerca de três dias depois. Quando as coisas estariam muito diferentes. Foi um encontro fortuito, daqueles com a câmera pegando a gente do outro lado da rua, que nem naquele filme do Woody Allen. Indicando que a intimidade (tão rápida!) já havia morrido. Porém, enquanto eu descia as escadas eu tinha certeza que não há veria mais.

Chego ao carro. Cato os bolsos em busca do meu maço. Lembro que o esqueci em cima do criado-mudo do quarto de Líria. Nunca que eu subiria novamente. Peço um dos mata-ratos de Nelson R.

– Porra Nelson, você foi me aparecer no momento mais foda né? Precisava? Hein? Logo que? Logo que?

(aspira profundamente o cigarro. Nenhum homem vivo ou morto já sentiu regojizo igual ao fumar um cigarro).

- Então Lu. Eu to aqui pra ajudar a conduzir essas suas lembranças. Esse negócio de usar um poeta morto pra acompanhar o protagonista é artifício velho. O Dante já usou com o Virgilio, lá no Inferno dele, há mais de quatrocentos anos.

– O que você quer dizer?

- Que a gente deve acender essa beata que você tem no porta luvas, e irmos pra casa. Num próximo capitulo dessa história, nós vamos ter uma nova conversa no Rio, onde deixamos o Fábio e o Carlos Drummond. Mas por enquanto temos que ir pra casa. É lá que está acontecendo a crise que vai motivar a escrita desse texto, daqui um mês.

Nelson acende o baseado. Dá um trago, e me passa a bola. Vou dirigindo, atravesso um pequeno trecho de Avenida Amazonas e volto pela Praça da Assembléia. Voltamos mudos, eu e Nelson, já sabendo o que vou encontrar quando chegar em casa.

Paro o Uno no estacionamento. Caminho como para o abate. Nelson já não está do meu lado. Com a cabeça em Líria, não dou atenção para duas mulheres que começam a mexer comigo. Não tenho paciência para falar com elas. Me acham antipático e vão gritando comigo, durante todo o trajeto até minha casa.

O saguão do prédio está escuro. São cerca de duas da manhã. Decido subir de escada. A subirei e descerei várias vezes ainda essa noite.

Chego em casa, minha mãe está no tanque, lavando um pedaço de pano. Reconheço ser uma camisa regata de meu pai.

-Pô mãe, lavando roupa essa hora da madrugada? Vai dormir mãe.

- Dormir como filho? Seu pai ta passando mal. Seu pai ta passando mal.

(continua…)

When passing a website using a reverse proxy , you might encounter an 503 error when the site you try to pass on is for some reason not available.
You can monitor this behavior by implementing your own 503 reporting system.
First you take on a line that will catch these errors.

Alias /error /srv/www/htdocs/error
ErrorDocument 503 /error/503.php

After this you can put together your own 503.php script

<?php
ob_start();
header('HTTP/1.1 503');
header('Status: 503');
$error=503
?>
<html>
 <title>Example.com Page Reported <? echo $error ?></title>
 <body>
 <br>
 <center><img src=/error/images/logo.png></center>
 <br>
 <center> Technical Problem Encountered</center>
 </body>
</html>
<?
// Retrieve the URL requested
function curPageURL() {
  $isHTTPS = (isset($_SERVER["HTTPS"]) && $_SERVER["HTTPS"] == "on");
  $port = (isset($_SERVER["SERVER_PORT"]) && ((!$isHTTPS && $_SERVER["SERVER_PORT"] != "80") || ($isHTTPS && $_SERVER["SERVER_PORT"] != "443")));
  $port = ($port) ? ':'.$_SERVER["SERVER_PORT"] : '';
  $url = ($isHTTPS ? 'https://' : 'http://').$_SERVER["SERVER_NAME"].$port.$_SERVER["REQUEST_URI"];
  return $url;
}

// Fill basic variables
  $page=curPageUrl();
  $today = date("F j, Y, G:i");
  $ip=$_SERVER['REMOTE_ADDR'];

  $headers  = 'MIME-Version: 1.0' . "\r\n";
  $headers .= 'Content-type: text/html; charset=iso-8859-1' . "\r\n";
// E-mailadres to inform
  $to='webmaster@example.com';

  $subject='ERROR '.$error.' Reported on '.$page;

  $message = '
  <html>
  <body>
    <table>
      <tr>
       <td>Requested URL</td><td>'.$page.'</td>
      </tr>
      <tr>
       <td>Requested By</td><td>'.$ip.'</td>
      </tr>
      <tr>
       <td>Requested On</td><td>'.$today.'</td>
      </tr>
    </table>
    </table>
  </body>
  </html>
  ';
// Mail the error
  mail($to, $subject, $message, $headers);
?>

Offcourse you can use this same code to report on different errors reported aswell .

Per poter gestire un web-server, ed in modo più generale per manipolare qualsiasi servizio è necessario saper trarre dati rilevanti dai file di Log. Apache fornisce vari strumenti e possibilità di configurazione dei file di log.

Immediatamente una considerazione sulla sicurezza. E’ importante non concedere ad utenti alcuni la possibilità di scrivere all’interno della cartella che detiene i file di log del web-server, potrebbe arrivare ad ottenere i privilegi dell’utente che esegue il primo avvio del demone (solitamente root). Altra considerazione all’interno dei file di log potrebbero essere presenti anche informazioni confidenziali, è bene valutare anche l’accesso in lettura.

Error Log, questo tipo di log raccoglie tutti gli errori che vengono generati dal web server. Il nome e la locazione di tale file di log viene indicata dalla direttiva ErrorLog, e di norma il file di riferimento è error_log, all’interno della cartella dei log di apache. Tale file di log non è personalizzabile, il formato è standard. Ecco un esempio:

[Sun Nov 15 07:31:45 2009] [error] [client 66.249.65.251] File does not exist: /var/www/default/components

Access Log, questo tipo di file raccoglie invece tutte le richieste processate dal web server. La locazione del file di log e il suo formato vengono controllati dalla direttiva CustomLog. L’utilizzo dei file di log solitamente non è mai fine a se stessa, ma o è utile per ritrovare errori o malfunzionamenti nel servizio oppure con programmi appositi si possono generare delle statistiche per capire:

• carico del web server
• tipi di client web che si connettono
• quante connessioni sono attive in un determinato lasso temporale
• etc…

La creazione di statistiche in relazione al server web esula da questa trattazione, è comunque utile ricordare come un buon formato di file di log aiuta i programmi automatici di generazione delle statistiche, come per esempio awstats (http://awstats.sourceforge.net/)

Analizzeremo ora due formati di Log:

• Common Log Format
• Combined Log Format

Il primo si indica nel modo seguente:

LogFormat “%h %l %u %t \”%r\” %>s %b” common
CustomLog logs/access_log common

e produce un output simile:

127.0.0.1 – frank [10/Oct/2000:13:55:36 -0700] “GET /apache_pb.gif HTTP/1.0″ 200 2326

Analizziamo nel dettaglio le voci:

• 127.0.0.1 (%h) → Indirizzo IP del client che ha effettuato la richiesta
• - (%1) → il meno indica che l’informazione richiesta non è disponibile. La risorsa non disponibile in questo caso è l’identità del client (RFC 1413) determinata da identd
• frank (%u) → corrisponde allo userid dell’utente che ha effettuato la richiesta dopo una autenticazione http. Nel caso in cui non ci fosse stata autenticazione il valore assegnato sarebbe stato -
• [10/Oct/2000:13:55:36 -0700] (%t) → la data in cui la richiesta è arrivata
• “GET /apache_pb.gif HTTP/1.0″ (\”%r\”) → ciò che il client ha fatto, in questo caso ha richiesto l’immagine apache_pb.gif
• 200 (%>s) → Il codice di stato del server web in risposta alla richiesta del client. Ricordo che i codici si differenziano a grandi linee i 4 modi:
  • codici che cominciano con 2 → risposta data con successo
  • codici che cominciano con 3 → redirect
  • codici che cominciano con 4 → errore causato dal client
  • codici che cominciano con 5 → errore nel server
• 2326(%b) → indica la dimensione dell’oggetto restituito al client

Il Combined Log Format, è molto simile al formato appena affrontato, con l’aggiunta di due opzioni; ecco di seguito come viene espresso:

LogFormat “%h %l %u %t \”%r\” %>s %b \”%{Referer}i\” \”%{User-agent}i\”" combined
CustomLog log/access_log combined

e cosa produce:

127.0.0.1 – frank [10/Oct/2000:13:55:36 -0700] “GET /apache_pb.gif HTTP/1.0″ 200 2326 “http://www.example.com/start.html” “Mozilla/4.08 [en] (Win98; I ;Nav)”

Analizziamo nel dettaglio le voci aggiuntive:

• “http://www.example.com/start.html” (\”%{Referer}i\”) → si riferisce alla pagina dalla quale è avvenuta la richiesta del client
• “Mozilla/4.08 [en] (Win98; I ;Nav)” (\”%{User-agent}i\”) → dettagli del client

Rotazione dei Log – La dimensione dei file di log di apache cresce molto velocemente. Dato il numero di informazioni salvate il file di accesso cresce in media di 1 MB per 10.000 richieste. E’ bene quindi adottare un metodo di rotazione per eliminare i vecchi file di log con una accortezza, dato che apache continuerà a scrivere sul vecchio file di log finché non sarà riavviato.

La politica corretta da adottare durante la rotazione dei log e quella di effettuare la rotazione rinominando il vecchio file di log in access_log.1, creando il nuovo file access_log e riavviare in modo leggero apache (per esempio il comando apache2ctl graceful o apache2 reload).

In questo caso tutte le operazioni pendenti verranno concluse loggando le attività sul vecchio file di log, mentre le nuove istanze scriveranno sul nuovo file di log.

Va considerato per il metodo di rotazione un demone molto ben costruito come logrotate, che per sistemi debian ha già una configurazione ottimale (gestisce il riavvio dolce di apache durante la rotazione).

Piped log – L’espressione piped Log si utilizza quando apache fornisce i dati di accesso e di errore ad un programma terzo, che in base alla propria configurazione gestisce i dati in input.

L’utilizzo di questa procedura incrementa in modo notevole la flessibilità dei file di log e scarica il server web dalla gestione dei medesimi file. Come contro però si deve gestire un altro programma che sia in grado di intercettare i dati di apache.

Per quanto riguarda i virtual host invece

Virtual Host – Ci sono vari modi per gestire il logging dei virtual host. E’ possibile inserire tutte le informazioni di log degli host virtuali all’interno del file principale, oppure è possibile indicare per ogni virtual host uno specifico file di log. In questo ultimo caso è molto più semplice ricavare statistiche in relazione al singolo sito.

L’utilizzo di molti Virtual Host con assegnati specifici log può andare incontro ad un problema, ovvero si rischia di raggiungere il limite massimo di file descriptor aperti.

In sistemi Linux per ogni processo vengono allocati un massimo di 64 file descriptor, apache ne occupa una decina per uso interno e uno per ogni file di log. Con una trentina di virual host si potrebbe essere al limite delle risorse. Le soluzioni sono due:

• limitare il numero di file di log (inserenti in un unico file tutte le informazioni manipolando la scrittura dei dati in modo da taggate quelli che provengono da un tale VirtualHost)
• Incrementare il numero di file descriptor per processo

To catch all traffic which requests an APEX admin page like 4550 , you can include these RewriteRules in your Apache Reverse Proxy configuration.
When not set on the first entry point ( in this case the reverse proxy ), you might run into the problem that all traffic received on your back-end server seem to come from an internal adres( your reverse proxy server)
and can therefor not be filtered using the build-in security feature in APEX. So be implementing these rules your site can be made more secure again.

# Set Engine on
RewriteEngine On

# 403 error will be thrown if met
# exclude the password change page for apex users
RewriteCond %{REQUEST_URI}%{QUERY_STRING} !/(apex|builder)/f?p=4155:.*
RewriteCond %{REQUEST_URI}%{QUERY_STRING} /(apex|builder)/f?p=(4[0-9]{3}:.*)
# Making it available still from 127.0.0.1 and 10.0.0.x
RewriteCond %{REMOTE_ADDR}        !^(127\.0\.0\.1|10\.0\.0\.[0-9]{1,3})$

# Else , let request go threw
RewriteRule /(apex|builder)/ - [F]

If you want to catch these 403 errors and show a nice error message for it, you can set these lines aswell

  alias /error /srv/www/htdocs/error

  ErrorDocument 403 /error/forbidden.html

Now place a forbidden.html file in /srv/www/htdocs/error/ and you are all set.

“Mi objetivo es trabajar con los surfistas que son serios al aceptar el consejo que les llevará al siguiente nivel. Ofrezco diseño de alta calidad y artesanía, mi atención personal, tecnología innovadora, integridad, un precio justo y rápidos resultados.

Normalmente la mayoría de las empresas se reservan este tipo de servicio para los “pros” y “elite”. Me gusta hacer las tablas de muchos de los surfistas con más talento del mundo, y sus comentarios me impulsan como diseñador de tablas para que respondan a las más altas exigencias de rendimiento – Llevo el mismo nivel de calidad y atención a ti, el surfista medio que busca la tabla “mágica”.

Recuerde – los mejores surfistas del mundo son las que obtienen más diversión!
Es tu tabla … habla con tu shaper.”

Todd Proctor

Esta es la introducción que aparece en su web, Proctor Surfboards es un taller de tablas (a la americana, es decir a lo grande) en Ventura, California y presume de dar un trato directo y personalizado a cada surfista.

Lo que me llama la atención es el particular diseño de sus tablas. Sin ir más lejos, el modelo “Apache” combina formas y conceptos que resultan en un auténtico cohete para olas pequeñas. Tiene muchos otros modelos interesantes. Mis preferidos son los incluídos en “Rascal Series” pero para los que prefieran algo más radical tiene verdaderas virguerías como el  modelo Parabolic, o la Lacerator. Como muestra, el quiver de Jarrah Tutton para el 2010…

También ofrece la posibilidad de crear, junto con el shaper, un nuevo concepto de tabla combinando tus gustos y necesidades en formas y medidas, con el saber hacer del shaper (para que luego flote).

En definitiva, un gran taller que innova, crea y además ofrece un trato directo, como antes de que llegara la era del epoxy.

How do I log only INFO statments on console and all DEBUG statements in log file? This was a question infront of me.
If you know log4j a bit you might expect it to be very simple to do (even I thought the same). You could do this very easily by using two different loggers
for INFO and DEBUG statements which is kind of annoying. I wanted to have any class-level logger to log its INFO and DEBUG seperately. Below is what I want to achieve.

public class LoggerTest {
	public static void main(String args[]){
		Logger log = Logger.getLogger(LoggerTest.class);
		log.info("I should go to console");
		log.debug("I should go to a log file");
	}
}

Finally, I came to a solution which worked very well for me.
log4j.properties has some limitations like, you cannot specify filters in it. Hence I used log4j.xml.

  <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd" >
<log4j:configuration>
	<appender name="debugfile"
		class="org.apache.log4j.RollingFileAppender">
		<param name="maxFileSize" value="500KB" />
		<param name="maxBackupIndex" value="5" />
		<param name="File" value="debug.log" />
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern"
				value="%d{HH:mm:ss} %5p %5M.%C - %m%n" />
		</layout>
		<filter class="org.apache.log4j.varia.LevelRangeFilter">
			<param name="LevelMin" value="debug" />
			<param name="LevelMax" value="debug" />
		</filter>
	</appender>

	<appender name="stdout" class="org.apache.log4j.ConsoleAppender">
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern"
				value="%d{HH:mm:ss} %5p %5M.%C - %m%n" />
		</layout>
	<!-- Apply filter to output only INFO logs in the console -->
		<filter class="org.apache.log4j.varia.LevelRangeFilter">
			<param name="LevelMin" value="info" />
			<param name="LevelMax" value="info" />
		</filter>
	</appender>
<!--Configured "com.abc" to log only DEBUG statements to the log file
	It will ignore all other statements since we have set the level to DEBUG (least priority)
	-->
	<logger name="com.abc" >
		<level value="debug" />
		<appender-ref ref="debugfile" />
	</logger>
<!--Configured Root to log only INFO statements into STDOUT since we want
	 only INFO statements to be displayed in the console.
	-->
	<root>
		<level value="info" />
		<appender-ref ref="stdout" />
	</root>
</log4j:configuration>

Configure a logger of your root of the package hierarchy to log in a debug file. For example, if your package hierarchy starts with say com.abc then configure a logger named “com.abc” to log in a debug file.
This will make every class-level logger inside com.abc pkg to log its debug statements in a debug file. Okay at this point we are done with the first requirement.

Now, lets look how to log info statements to console. For this, we dont have to create another logger. We can utilize RootLogger which is the parent of all loggers in log4j.
Since we have configured “com.abc” to log only debug statements it will ignore the info statements. Those statements are the bubbled up the hierarchy and respected by the RootLogger which we have
configured to log INFOs to the console. Mission accomplished

It’s funny the turns Life takes.

I started programming in the eartly 1980s, on Timex Sinclair, Commodore 64 and TRS-80 computers in short order.  In those wild days when high-level languages were really coming into their own, free and open source software seemed more readily available than retail equivalents.  Hobbyist magazines, online bulletin boards and even the fledgling internet (pre WWW) were stuffed with code just waiting for eager learners like to me to take and tweak.  There wasn’t much in the way of formal free and open source protocol at the time– that evolved soon enough though.

But as I evolved myself, from hobbyist to ad hoc developer for various employers, I found myself drawn in deeper and deeper to the closed source world.  I discovered I had a liking and knack for Visual Basic and thus fell into the Microsoft development vortex.

It’s a seductive and powerful sucker, too.  It was all too easy to be “bought off” by events with (ironically) free training, free food and even giveaways of free software.  I ultimately joined a Microsoft program that dumped thousands of dollars of tools in my lap for an embarrassingly small outlay.  Resistance was futile.

Yep, I was assimilated.

Flash forward to 2005 when Nokia hired me to do data mining/management for factory quality assurance.  At first it was the usual: Microsoft SQL Server, the Office suite, VB.NET and even Oracle.  The only real challenge I faced at the time was ramping up SQL skills to an enterprise level.

Then, as I’ve mentioned in previous articles, the Nokia 770 internet tablet burst into my life.

At first it was an utterly alien object, this Linux-driven refugee from an old Star Trek show.  I only knew it mobilized the Internet like nothing else at the time… and I wanted to put it to work.

I eventually took on a new role as quality engineer for certain Nokia products and that included the 770 and then the N800, which I helped launch.  Supporting the tablets meant getting acquainted with something I had marvelled at from afar but never touched until then:

Linux.

At first I had to perform all device flashing from a Linux command line.  A helpful colleague introduced me to Ubuntu and after acquiring a laptop for the work I dug in.  Just not too deeply– I was still using Windows tools for the bulk of my labors so I didn’t really have time to invest in becoming a Linux guru… although the desire was certainly there.

And now a few years and turns later, I find myself in another role where the old trusted tools need not apply.  I haven’t even coded in VB for over a year!  Couple that with my current employer’s strong desire to save money and wham!  I’m back in the open source world.

Which is fine because I’m embarrassed that after a few years embedded in the Maemo culture I’ve barely picked up anything.  I want to do more application testing and even some development but I still lack the foundation.

So I’m excited by the opportunity I have in my employment to investigate a process workflow solution (more on that in another article) that’s completely open source and takes full advantage of the open source ecosystem (MySQL, Apache, OpenBravo, Knowledgetree, Zimbra).  This is my chance to pull free of the Microsoft vortex, at least a little bit, and gain some proficiency in what I think will ultimately become the status quo.

I’m ready now to get into Qt… Python… and whatever else looks useful.  How-To posts like those at talk.maemo.org showing how to get Windows developers onto Maemo devices are just adding irresistable fuel to the fire.

Hello (open source) World, here I (finally) come!

For the first time, when I try to deploy a project using Netbeans, i got this message,

Web development today

Web development today isn’t just HTML editing or basic php scripts. Web development and programming today is usually achieved with a wide set of tools — any popular website around today uses a wide set of tools. For example,

• reddit.com — reddit uses Python and PostgreSQL, which spit out html (of xhtml syntax), javascript and CSS.
• slashdot.com — slashdot.com uses Perl and MySQL, sitting on top of Apache.
• microsoft.com — microsoft.com uses a combination of ASP.NET, running on top of IIS. The output is html (xhtml syntax), css and javascript.

The tools

Web Developer / Firefox Extension

Firefox Web Developer Extension is a useful tool for being able to disable various features on a page, manage cookies, view specific css information using a picker tool for any specific elements and being able to manager userstyles. You can also manage images and various other tools including the ability to view generated source.

You can download it at Mozilla Add-ons

ColorZilla / Firefox Extension

ColorZilla is an extension to firefox that adds a color picker tool to the browser UI. It is then possible to return information for a given pixel on a website.

You can download it at the Mozilla Add-ons site.

MeasureIT / Firefox Extension

The measureIT Firefox extension adds a measuring tool that appears as an overlay on any webpage you need to use it on.

You can download measureIT at the Mozilla Add-ons site

DOM Inspector / Firefox Extension

The Document Object Model Inspector is a tool to inspect the DOM of any webpage. It often comes with the default install of firefox as an option.

You can download DOM Inspector at https://developer.mozilla.org/en/dom_inspector

Firebug / Firefox Extension

Firebug is an extension which is useful for editing css, html or javascript elements within a webpage.

You can download Firebug at the Mozilla Add-ons site.

Google page speed / Firebug Extension

Google page speed is a Firebug extension that is able to give you a wealth of information on the download speeds and execution time of your website. It can also give you tips on how to reduce overheads and improve code.

You can download the Google page speed Firebug extension at the google page speed site.

Notepad++

Notepad++ is a tool I often use when working on smaller projects where I do not need a full IDE.

Notepad++ is a free (as in “free speech” and also as in “free beer”) source code editor and Notepad replacement that supports several languages. Running in the MS Windows environment, its use is governed by GPL License.
Based on a powerful editing component Scintilla, Notepad++ is written in C++ and uses pure Win32 API and STL which ensures a higher execution speed and smaller program size.

You can download it over at the notepad++ sourceforge project site.

Netbeans with PHP Development plugin

Netbeans is a Java IDE developed by Sun. It supports various plugins — one being PHP development extensions. When working on large projects, Netbeans proves useful.

You can download it at the Netbeans site.

Visual SVN

VisualSVN is a SVN server for Windows. It is quick and easy to use and requires little previous knowledge of server administration or svn experience, but it can also be quite powerful.

You can download it at the VisualSVN Server site. It is free for both personal and commercial use.

Tortoise SVN

TortoiseSVN is an SVN client that interfaces with Windows Explorer to interface with SVN.

You can download it at the TortoiseSVN site.

XAMPP

XAMPP is a quick and easy way to get an apache server, MySQL daemon and PHP all running on Windows for a development environment. It also supports an FTP server and a few other things.

You can download it at the XAMPP site.

Forums
You can come and discuss web development, get website reviews and also SEO information at the Transcendental Labs forum.

I was struggling to install mod_python with apache on my windows machine since last 2 days, and today finally when I succeeded I thought I must share it with all of you.

First of all we need compatible versions of all three of the following.

• Apache Web Server
• Python environment
• mod_python

In my case I have used

• Apache 2.2 (http://httpd.apache.org/download.cgi)
• ActivePython 2.5 (http://www.activestate.com/activepython/)
• mod_python 3.3.1 (http://httpd.apache.org/modules/python-download.cgi)

First install Apache and python. Python can also be downloaded from official website of Python (http://www.python.org/). While downloading mod_python take care of your Python and Apache version.After installing mod_python goto “apache/conf/” and edit httpd.conf.

Add,

LoadModule python_module modules/mod_python.so

where all the local modules are listed. Then add

<Directory /some/directory/>
AddHandler mod_python .py
PythonHandler mod_python.publisher
PythonDebug On
</Directory>

(Substitute /some/directory above for something applicable to your system, usually your Apache ServerRoot).
This redirects all requests for URLs ending in .py to the mod_python handler. mod_python receives those requests and looks for an appropriate PythonHandler to handle them.

Restart your Apache Server ,your mod_python is configured and now you can move to testing. Create a file named hello.py in your root directory paste the following code in it

from mod_python import apache
def handler(req):
 req.content_type = 'text/plain'
 req.write("Hello World!")
 return apache.OK

Point your browser to the URL referring to the hello.py; you should see “Hello World!“

If you were to change your website to a new domain or changed the location of an existing file, and you have your url indexed by search engines. If the pages are redirected you could end up loosing a lot of traffic by users getting the 404 error.

You can sort those by using redirection. This can be achieved by http-equiv, javascript or by using some server side code. But the simplest way is by using .htaccess 301 redirect.

This method is search engine friendly and is the easiest way around.

Just add the following code to your .htaccess file placed in your old site.

Redirect 301 /olddirectory/oldfile.html http://yoursite.com/newdirectory/newfile.html

redirect 301 (the instruction that the page has moved)

/old/old.htm (the original folder path and file name)

http://www.yoursite.com/newdirectory/newdirectory/newfile.html (new path and file name)

Test  immediately after implementing 301 redirects. If you find anything wrong, remove the redirect immediately.

Introducción

Hoy vamos a aprender a establecer un nivel de seguridad en nuestro servidor Apache, corriendo bajo Ubuntu, aunque como siempre digo podemos usar cualquier distribución para seguir el tutorial. Constará de una autenticación mediante un usuario y contraseña. Para este tutorial voy a crear un nuevo Host basado en IP. Dicho esto, vamos a ello.

Creando el nuevo Host

Como ya he comentado antes, voy a crear un nuevo Host basado en IP, para ello abrimos el terminal y tecleamos lo siguiente:

sudo mkdir /var/www/passwordhost

Una vez creado el directorio que alojará el nuevo Host, vamos a crear el index.html, por lo que tecleamos en el terminal:

sudo gedit /var/www/passwordhost/index.html

Una vez con gedit abierto, escribimos un código HTML básico, como el siguiente:

<html>
     <head>
          <title>Ejemplo de host con password</title>
     </head>
     <body bgcolor="#008080">
          <h1>Ejemplo de host con seguridad básica</h1>
     </body>
</html>

Genial, ya tenemos creado el Host con su index. Como lo estamos haciendo mediante IP, ahora debemos crear una interfaz virtual. Si mal no recuerdo, nuestra interfaz se llamaba eth2, para comprobarlo tecleamos en el terminal:

ifconfig

Ahora ya sabemos que estaba en lo cierto, nuestra interfaz se llama eth2 (en amarillo ), eth2:1 y eth2:2 (en azul) son las interfaces virtuales que creamos en el anterior tutorial, dicho esto, vamos a crear la interfaz nueva a partir de eth2, nos vamos al terminal y escribimos:

sudo ifconfig eth2:3 172.16.100.30 netmask 255.255.0.0

En la imagen he marcado en rojo la nueva intrfaz, eth2:3.

Ahora vamos a crear el archivo propio del Host dentro del directorio de configuración de Apache. Nos vamos a un terminal y escribimos:

sudo gedit /etc/apache2/sites-available/passwordhost

Y dentro de este archivo escribimos lo siguiente:

<VirtualHost 172.16.100.30>
     ServerName www.passwordhost.com
     DocumentRoot /var/www/passwordhost
</VirtualHost>

Una vez creado el Host, con su archivo de configuración y demás, vamos a darlo de alta, para ello tecleamos en el terminal:

sudo a2ensite passwordhost

Estableciendo los niveles de seguridad

Una vez con el Host creado, vamos a establecer un nivel de seguridad básico para la página web. Antes de nada debemos crear el directorio que alojará la información referente a los usuarios y sus contraseñas. Vamos a crear tres usuarios y dos grupos, cada uno en su respectivo grupo. Los usuarios y grupos serán:

• policia, del grupo buenos.
• testigo, del grupo buenos.
• ladron, del grupo malos.

A ser posible, para prevenir posibles problemas de compatibilidad, evitaremos poner tildes y carácteres raros (ñ, %, &…) en el nombre del usuario.

Pasemos ahora a crear dicho directorio, en el terminal tecleamos:

sudo mkdir /var/www/password

Estupendo, una vez creado el directorio vamos a crear el primer usuario, volvemos al terminal y tecleamos:

sudo htpasswd -c /var/www/password/.pass_user policia

Ya tenemos creado el primer usuario, policia. Ahora crearemos los siguientes usuarios.

NOTA: Una vez tenemos creado el primer usuario, para los usuarios que creemos posteriormente no debemos poner el -c en la consola, ya que le indicaríamos al comando htpasswd que volvemos a crear el primer usuario, y machacará la entrada del usuario policia.

Ahora que sabemos lo anterior, volvemos a la consola y creamos los demás usuarios:

• Usuario testigo:

sudo htpasswd /var/www/password/.pass_user testigo

• Usuario ladron:

sudo htpasswd /var/www/password/.pass_user ladron

Ahora ya tenemos creados los tres usuarios a los que daremos (o no) permiso permiso para visualizar el contenido de nuestro sitio web.

Pasemos ahora a crear los dos grupos, buenos y malos. Para crear un grupo nos vamos al terminal y tecleamos lo siguiente:

sudo htpasswd -c /var/www/password/.pass_group buenos

Un grupo se crea de la misma forma que se crea un usuario, incluso teniendo en cuenta el parámetro -c para el primer grupo. Cuando ya tenemos creado el primer grupo, entonces creamos el segundo:

sudo htpasswd /var/www/password/.pass_group malos

Cuando ya hemos creado el segundo grupo, abrimos el archivo de grupos con gedit, por lo que escribimos en una consola esto:

sudo gedit /var/www/password/.pass_group

Una vez con el archivo abierto, esto será lo que veamos:

Tenemos que borrar los caracteres incoherentes y dejar el archivo de la siguiente forma:

Guardamos el archivo y listo. Ahora volvemos al terminal, y tecleamos lo siguiente para crear el próximo archivo en el que configuraremos qué grupos y usuarios tienen acceso al Host passwordhost.

sudo gedit /var/www/passwordhost/.htaccess

Una vez con gedit, rellenamos el archivo con lo siguiente:

AuthType         Basic
AuthName         "Acceso a mi host"
AuthUserFile     /var/www/password/.pass_user
AuthGroupFile    /var/www/password/.pass_group
require group    buenos

Pulsamos en guardar, y vamos ahora a editar el último archivo. Volvemos al terminal y tecleamos:

sudo gedit /etc/apache2/sites-available/default

Nos vamos hacia el final del archivo, después de que cierre la última etiqueta <Directory>, escribimos lo mismo que en la imagen:

<Directory /var/www/passwoardhost>
     AllowOverride    AuthConfig
     Order    allow,deny
     Allow    from all
</Directory>

Una vez añadido eso al archivo default, ya sólo queda reiniciar apache, volvemos al terminal y tecleamos:

sudo apache2ctl restart

Verificando el funcionamiento

Ahora ya tenemos nuestro Host protegido, y hemos establecido los permisos para los usuarios que hemos querido, ahora sólo queda comprobar que todo funciona como debe.

Abrimos Firefox (o nuestro navegador habitual), y visitamos la siguiente dirección:

• 172.16.100.30

Si  todo marcha bien, esto será lo que veamos:

Ahora introducimos cualquier usuario de los que tengan permiso, por ejemplo, policia.

• En Nombre de Usuario: policia
• En Contraseña: soypoli

Esos son los datos que yo use para crear el usuario, como es obvio, vosotros debéis introducir los que usasteis.

El usuario policia, al estar definido en el grupo buenos (único grupo autorizado para entrar al Host) pues ha podido entrar sin problemas.

Lo mismo debe de ocurrir con el usuario testigo, sin embargo, al usuario ladron no le permitirá entrar ya que no se encuentra en el grupo buenos, y por lo tanto no está autorizado.

Si el nombre de usuario que introducimos es erróneo o no está autorizado, al pulsar en Aceptar, nos volverá a salir la misma ventana de logeo, sin embargo, al pulsar en Cancelar, obtendremos el siguiente mensaje de error:

Eso significa que nuestro Host está correctamente protegido.

Bibliografía

• Apuntes de clase.

]]>