Yearly Archives: 2007

Syntax highlighting in wordpress

Posted on by
Reply

As you can see a few posts earlier, I’m playing with a syntax highlighter for my blog.

title.pngFor the syntax hightlighting itself, I found GeSHi and I’m happy with the result of the hightlighting.

The integration with my wordpress blog is currently done with the WordPress GeSHi Plugin, but it does not produce an acceptable result for me. Open points for the syntax highlighting integration are:

  • Visual Editor must not destroy the format of the <code> part.
  • The pre element must be used, but it can not handle the word-wrap automatically at the end of the line. Maybe, I’ll use a IFrame for this.

Notebook is coming earlier

Posted on by
Reply

latit_d820.jpgJust now, I got a Mail from our administrator. The notebooks are on the way and the approximate delivery date is tuesday, the 06.03. :-)

We checked the most important tools for their compatibility to Windows Vista and all tools seem to have at least a patch. So lets start working with Vista!

Trac and the DiscussionPlugin

Posted on by
3

Today, I tried to integrate the DiscussionPlugin into my Trac 0.10.3 sandbox. But I must notice, that the DiscussionPlugin seems to be incompatible with the version and/or the WebadminPlugin. The discussion plugin where not found several times and disturbed the webadmin. So my last chance was to uninstall the plugin from the plugins folder. Tomorrow, I will try to install it on the python path to make it globally available. Maybe it works better this way.

How to integrate pam with winbind

Posted on by
Reply

To use samba with winbind for your pam authentication, you have to edit the process file (e.g. apache2) under /etc/pam.d/ and add the following lines:

  1. #%PAM-1.0
  2. auth    required        pam_winbind.so
  3. account required        pam_winbind.so

If you are already using a configuration, you can add the winbind authentication by simply changing “required” to “sufficient”. The order of the plugins in the file matters to the order of authentication.

The following configuration tries to authenticate against winbind and if this fails, against the unix module.

  1. auth    sufficient      pam_winbind.so
  2. auth    required        pam_unix.so

How to get mod_auth_pam running on Apache 2.2.x.

Posted on by
8

mod_auth_pam is not supported and/or developed any longer and the latest available version works only with apache 2.0.x. The new apache 2.2 uses a new authentication mechanism and the old mod_auth_pam does not work, if you only install it to your local apache and use it with the follow configuration:

  1.  AuthPAM_Enabled On
  2.   AuthPAM_FallThrough Off
  3.   AuthType Basic
  4.   AuthName "Testingarea"

You have to turn off the new apache 2.2 basic authentication to get the module up and running. You can do this in two different ways. The first one is to disable the hole module, the second and better one is to disable it through a directive.

For the first solution, you can use the tool a2dismod to disable the module mod_auth_basic.

For the second way, you have to add this lines to the configuration above.

  1. …
  2. AuthPAM_Enabled On
  3. AuthPAM_FallThrough Off
  4. AuthBasicAuthoritative Off
  5. …

In the second way, the error.log of apache shows the following lines:

  1. [Wed Feb 21 20:01:35 2007] [error] Internal error: pcfg_openfile() called with NULL filename
  2. [Wed Feb 21 20:01:35 2007] [error] [client 192.168.0.201] (9)Bad file descriptor: Could not open password file: (null)

The positive message is: you can ignore them ;-) It means, that the mod_auth_pam does not register an AuthBasicProvider and therefore it is null and crashes. Not nice, but it works.