sabato 31 marzo 2007

Q10064 - HOWTO: Reset Cache Mode in Outlook

thanks
http://www.lanlogic.net/support/docs/article.aspx?id=10064

You may need to turn off cache mode and turn it back on if your Outlook
client is running slow, or if you are suddenly unable to send or receive
emails. Going through the steps will essentially remove the Outlook
cache from your computer, and then rebuild it. The cache is the local
copies of your emails.

1. Turn Off Cache Mode

1. Open Outlook
2. Tools
3. Email Accounts
4. Select View or change existing e-mail accounts
5. Next
6. With "Microsoft Exchange Server" selected, Click "Change"
7. Uncheck the box for "Use Cached Exchange Mode"
8. Next
9. In the box that pops up, click on OK
10. Click Finish

2. Close Outlook
1. File
2. Exit

3. Delete OST files from hard drive
1. Start
2. Search
3. For Files or folders
4. All files and Folders
5. Expand "More Advanced Options"
6. Check the box next to "Search hidden files and folders"
7. Leave the other options at default
8. In the top box for "All or part of the file name", type in
"*.ost"
9. Look in should be "Local Hard Drives"
10. Click Search
11. It'll find files such as outlook.ost, outlook001.ost, etc.
Select all the files it finds and select delete. This will
delete all the offline emails from your computer, but they
are still on the server so you won't lose anything.

4. Turn On Cache Mode

1. Open Outlook
2. Tools
3. Email Accounts
4. Select View or change existing e-mail accounts
5. Next
6. With "Microsoft Exchange Server" selected, Click "Change"
7. Check the box for "Use Cached Exchange Mode"
8. Next
9. In the box that pops up, click on OK
10. Click Finish

5. Restart Outlook

Once Outlook is restarted, all of your emails will download to your
computer again. It may take awhile, depending on the number of emails
you have. You can watch the progress in the lower right corner of your
Outlook screen… it will show the folders as they update.

Outlook (xp or 2003) slow to open mails

thanks to http://www.brichet.be/?p=139

Try first to launch Outlook in safe mode (Outlook /safe).
If the problem disappear in safe mode, try first disabling add ins and
then try renaming cache files (source : newsgroups)

Locate and rename the Outlook cache files
(frmcache.dat,outcmd.dat,extend.dat) one by one.
————————————————–

1. Quit Outlook.
2. Click Start -> Search -> For Files and folders
3. Click Tools -> Folder Options.
4. Select View tab, select Show hidden files and folders, uncheck Hide
extensions for known file types, and click OK.
5. Click All files and folders.
6. Type "frmcache.dat,outcmd.dat,extend.dat,views.dat" (without the
quotation marks) in the filename box, and then select Local Hard Drives.
7. Click More advanced options, check Search hidden files and
folders, and
click Search.
8. After the search has finished, renames files in .old
NOTE: We may find multiple files for each name. Please rename them all.
9. Restart Outlook.

giovedì 29 marzo 2007

Eseguire uno script al logoff o logout senza un dominio e le group policy

Start -> Esegui... -> gpedit.msc
è lo stesso pannello delle gpo

mercoledì 28 marzo 2007

DRIVER_IRQL_NOT_LESS_OR_EQUAL error

DRIVER_IRQL_NOT_LESS_OR_EQUAL:
chissà a quanti di voi sarà capitato di vedere improvvisamente questa
schermata blu con riportato in cima questa scritta, beh la soluzione è
alquanto semplice, generalmente il problema è causato dalla RAM che è o
difettosa o incompatibile con la scheda madre, oppure sono impostati dei
timings troppo aggressivi per cui bisogna alzarli.

In caso invece vi fossero problemi hardware di altra natura, consiglio
la consultazione delle seguenti pagine Microsoft:

Hardware and Software Third-Party Vendor Contact List, A-K
<http://support.microsoft.com/?kbid=65416>
Hardware and Software Third-Party Vendor Contact List, L-P
<http://support.microsoft.com/?kbid=60781>
Hardware and Software Third-Party Vendor Contact List, Q-Z
<http://support.microsoft.com/?kbid=60782>

In qualche altra circostanza la causa del problema potrebbe dipendere
dal file di paginazione, e visto che non costa nulla, provare questa
procedura:

1. destro mouse su risorse del PC / proprietà /avanzate / impostazioni e
cliccare sul pulsante prestazioni / avanzate / memoria virtuale / cambia
/ qui selezionare nessun file di paging e cliccare su imposta / OK / OK
e riavviare

2. una volta riavviato destro mouse su risorse del PC / proprietà
/avanzate / impostazioni e cliccare sul pulsante prestazioni / avanzate
/ memoria virtuale / e selezionare Dimensioni gestite dal Sistema
cliccare Imposta / Ok / Ok e riavviare.

Se con questa procedura non compare più l'errore
DRIVER_IRQL_NOT_LESS_OR_EQUAL allora siamo stati fortunati, se invece
compare ancora e pure frequentemente, allora meglio focalizzare
l'attenzione sulla RAM.

fonte jsi

sabato 24 marzo 2007

[freebsd] - gestione utenti e gruppi

http://www.perlcode.org/tutorials/sysadmin/managing_users.pod

[freebsd] - mysql

qui c'è una guida all'installazione e alla configurazione di mysql su
freebsd
vale anche per altre distro

http://www.freebsddiary.org/mysql.php

[Freebsd] - abilitare il su

su - how to become a super user. avoid using root

If you're like most people new to Unix, you do everything as root. You
shouldn't. I know I don't follow my own advice, but I'm trying to
improve.

Create yourself another account. Use that instead of root. Unless you
really need root. You can always invoke su to become a super user.
That way, you don't have to log out and back in every time you need the
power.

wheel

Only users in the wheel group can run su. The group can be specified
when creating a user via adduser. To add a user manuall, just put the
name of the user at the end of the line in /etc/group. For example:

wheel:*:0:root,marc

This adds the user marc to the wheel group.


su

To become super user, you do this:

bash-2.02$ su
Password:
su-2.02#

At the password prompt, supply the root password.

Note that you might also want to use either the -l or the -m options.
Respectively, these options will simulate a full login or leave the
environment unmodified. see man su
<http://www.freebsd.org/cgi/man.cgi?query=su&apropos=0&sektion=0&manpath=FreeBSD+2.2.8-RELEASE&format=html>
for details.

mercoledì 21 marzo 2007

GPO - Group Policy - Installazione Software - OpenOffice e JRE

GPO - Group Policy - Installazione Software


OpenOffice e JRE

thanks to
http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation


Desktop Software Installation

These instructions describe the steps needed to perform a network
installation of the OpenOffice.org office suite and the
OpenOffice-Enterprise client software using Windows Group Policy.

These instructions are copyright Open Office Technology. They may be
linked to but not copied. Their permanent location is

http://OpenOfficeTechnology.com/OpenOffice-Enterprise/Desktop_Installation

<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation>

* Overview <http://openofficetechnology.com/node/24>
* Package Installation Order <http://openofficetechnology.com/node/30>
* Step 1 – Download Software Packages
<http://openofficetechnology.com/node/25>
* Step 2 – Create Network Installation Images
<http://openofficetechnology.com/node/26>
* Step 3 – Create Installation Group Policy Object
<http://openofficetechnology.com/node/27>
* Step 4 – Set Policy Scope and Link to Domain
<http://openofficetechnology.com/node/28>
* Upgrading OpenOffice-Enterprise
<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation/Upgrading_OpenOffice-Enterprise>
* Upgrading OpenOffice
<http://openofficetechnology.com/OpenOffice-Enterprise/Desktop_Installation/Upgrading_OpenOffice>
* Installation Troubleshooting <http://openofficetechnology.com/node/29>


Overview

The three software packages discussed in these instructions are:

1. The OpenOffice.org office suite. Installation of this package on
each client is required.
2. The OpenOffice-Enterprise client software. Provides Group Policy
management for the OpenOffice.org office suite. Installation of
this package on each managed client is required.
3. Sun's Java runtime environment (JRE). Certain functions in the
OpenOffice suite depend on the Java runtime, such as the database
application, mail merge and the document wizards in Writer. (For a
more complete list, see Java and OpenOffice.org
<http://wiki.services.openoffice.org/wiki/Java_and_OpenOffice.org#OpenOffice.org_2.0_Functionality_depending_on_Java>).
If these features are not required, the JRE does not need to be
installed. Full functionality requires the JRE or JDK version
1.4.0_02 or newer, or version 1.4.1_01 or newer. Limited
functionality is available with version 1.3.1 or higher. (Source:

http://www.openoffice.org/dev_docs/source/sys_reqs_20.html)

These instructions describe the installation procedure using the most
recent application versions as of the date these instructions were
written. The OpenOffice suite and Java JRE are not distributed by Open
Office Technology, and the information related to these packages may
change from time to time. If you find any discrepancies in these
instructions, please let us know <http://openofficetechnology.com/contact>.


Package Installation Order

The three packages must be installed in the following order:

1. Optionally, if required, the Java JRE.
2. The OpenOffice.org office suite.
3. The OpenOffice-Enterprise client software.

The installation of one or more of these packages can be combined into a
single Group Policy operation.

These instructions describe the process of installing all three packages
in one operation. If one or more are already installed, simply skip the
corresponding steps. To install one or more of the packages separately,
create separate Group Policy objects these packages.


Step 1 – Download Software Packages

The first step in the installation process is to download the software
packages.

A. Optionally, download the Java JRE *offline* installation package for
Windows. As of the date of these instructions:

* Most recent version of the JRE: Version 6.0
* Installation package file name: jre-6-windows-i586.exe
* Download location: http://java.sun.com/javase/downloads/

(Click to download "Java Runtime Environment (JRE) 6", click to
accept license agreement, then click on "Windows Offline
Installation, Multi-language")
* Other versions: http://java.sun.com/javase/downloads/previous.jsp

B. If OpenOffice is not already installed on the client machines,
download the OpenOffice installer for Windows without the JRE bundled.
As of the date of these instructions:

* Most recent version of the OpenOffice suite: Version 2.1
* Installation package file name: OOo_2.1.0_Win32Intel_install_en-US.exe
* Download location: http://download.openoffice.org/

* Other versions at: http://distribution.openoffice.org/mirrors/

<http://distribution.openoffice.org/mirrors/index.html#mirrors>

C. Download the OpenOffice-Enterprise client software installer. As of
the date of these instructions:

* Most recent version of OpenOffice-Enterprise client software:
Build 450
* Corresponding package file name: ooewin-450.msi
* Download location: http://OpenOfficeTechnology.com/download

<http://openofficetechnology.com/download>


Step 2 – Create Network Installation Images

The next step is to create network installation images for each of the
software packages. This places the installation images on a network file
server that is accessible to the client computers. To complete this
process, you must have write access to this location. The client
computer should have read-only access.

A. Extract the Java JRE msi file:

1. Run the JRE installation executable file, jre-6-windows-i586.exe.
The License Agreement screen will appear. Do not click either
"Decline" or "Accept".
2. The installer executable will have placed a file called
"jre1.6.0.msi" into the directory "C:\Documents and Settings\<your
username>\Application Data\Sun\Java\jre1.6.0". Copy the .msi file
to a network installation point, which is a location on the
network accessible to the client computers, such as
|
\\fileserver\net_install_images\jre-1_6_0\
|
Note 1: Earlier versions of JRE installation executable placed the
.msi file into a subdirectory such as "C:\Documents and
Settings\<your username>\Local Settings\Application
Data\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}", where the name of
the subdirectory depends on the JRE version. The .msi file
corresponding to the JRE version can be located by looking in all
subdirectories with names matching this pattern.
Note 2: Neither the Java installer executable nor the .msi file
support the "/a" administrative installation option.
3. Returning to the License Agreement screen, click "Decline". The
installer will delete the Application Data\Sun\Java directory and
its .msi file, then terminate.

B. Perform an administrative installation of the OpenOffice suite:

1. Run the OpenOffice installer,
OOo_2.1.0_Win32Intel_install_en-US.exe, with no parameters.
2. When prompted, enter a location to unpack the installation files,
such as a subdirectory called Ooo_installer_files in your current
working directory.
3. When the next stage of the installer runs ("Welcome to the
Installation Wizard for OpenOffice.org 2.1"), click "Cancel" and
abort the installation.
4. The OpenOffice installer should have unpacked several executable
and data files into the directory you selected. From the command
prompt, launch the setup file using the following command line:
|
setup /a
|
When prompted, enter a network installation point such as
|
\\fileserver\net_install_images\OpenOffice-2.1\
|
and then click "Install". The installer will create the directory
you specified, if it doesn't already exist, and then unpack the
file "openofficeorg21.msi" along with a handful of subdirectories
into this location.

C. Perform an administrative installation of the OpenOffice-Enterprise
client software:

1. From the command prompt, launch the installer file using the
following command line:
|
msiexec /a ooewin-450.msi
|
When prompted, enter a network installation point such as
|
\\fileserver\net_install_images\ooewin-450\
|
and then click "Next" twice. The installer will copy the .msi file
to this folder and unpack several files and one subdirectory.

Before continuing, ensure that the client computers have read-only
access to the network installation points that you used above.

Step 3 – Create Installation Group Policy Object

This step creates a Group Policy Object or "GPO" that will install the
software packages.

1. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then right-click on
"Group Policy Objects" and select "New". Enter a name such as
"OpenOffice-Enterprise Installation". Your new Group Policy Object
will appear in the tree under "Group Policy Objects". Right-click
on its name and select "Edit...". This will open the Group Policy
Object Editor.
2. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New --> Package...".
3. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
4. Navigate to the network location where you placed the Java JRE
install file "jre1.6.0.msi" and double-click on this file. If you
are not installing Java, skip this step and move down to the first
package you are installing.
5. For the deployment method, select "Assigned". The JRE install file
should appear in the view pane.
6. Right-click on "Software Installation" and select "New -->
Package..." again.
7. Navigate to the network location containing your OpenOffice suite
administrative install, and double-click on the .msi file
"openofficeorg21.msi".
8. Several installation transform files are available here
<http://openofficetechnology.com/OpenOffice_Installation_Transforms>.
If you do not want to use any transforms, select "Assigned" as the
deployment method and click "OK". The install file for OpenOffice
should appear in the view pane. Otherwise, to install OpenOffice
with one or more transforms, download the transform (.mst) files
and add them to the directory that contains the OpenOffice
installation file openofficeorg21.msi. Then for "Deployment
Method" select "Advanced" and click "OK". After a short pause, the
Properties dialog should appear. Under the "Modifications" tab,
add the transform file you wish to apply, then click "OK".
9. Right-click on "Software Installation" and select "New -->
Package..." again.
10. Navigate to the network location containing your
OpenOffice-Enterprise administrative install, and double-click on
the .msi file "ooewin-450.msi". For the deployment method, select
"Assigned". The OpenOffice-Enterprise install file should appear
in the view pane.

IMPORTANT: You must add the .msi files in the indicated order:
Java JRE, then OpenOffice.org suite, then OpenOffice-Enterprise.
The packages will appear in the view pane in alphabetical order,
but they will be installed in the order they were selected. The
indicated installation order is mandatory in order for all three
packages to be installed successfully.

11. To set additional options, double-click on each package name in
the view pane. For example, selecting "Uninstall this application
when it falls out of the scope of management" will cause the
applications to be automatically uninstalled if this group policy
object is deleted or unlinked. (Alternately, the software can be
uninstalled later by right-clicking on each package name and
selecting "All Tasks" -> "Remove..."). Any options selected must
be set for each package individually, so be certain to
double-click on each package name in succession and set the
desired options.
12. When done, double check your selections and close the Group Policy
Object Editor.


Step 4 – Set Policy Scope and Link to Domain

This final step selects the computers on which the software will be
installed. This involves designating a group or list of computers, along
with one or more domains or organizational units. The software will be
installed on a computer if it is both in the group that you designated
/and/ in one of the domains or organizational units you select.

The default is to "assign" the installation to all users which will
ultimately cause the software to be installed on all computers in the
selected domains, including servers and domain controllers. This is
probably not what you want.

A typical configuration will only install this software on desktop
workstations, not on domain controllers. Here are instructions to
accomplish this:

1. Back in the Group Policy Management console, click on the name of
your Group Policy Object (e.g., "OpenOffice-Enterprise
Installation" or whatever name you previously chose). In the pane
on the right, under "Security Filtering" in the "Scope" tab,
select "Authenticated Users" and click on "Remove".
2. Click "Add...", and in the dialog box that appears, under "Enter
the object name to select", type "domain computers" and click OK.
"Domain Computers" refers to all workstations in your domain; it
does not include domain controllers. It may however include
servers, so you should check the members of this group. In the
Group Policy Management view pane, click on the word "Domain
Computers", then click "Properties". In the Properties dialog,
select the "Members" tab. This brings up a list of the computers
in the "Domain Computers" group. If this group includes more
computers than desired, you can "Remove" this group and then
"Add..." computers individually, or you can create a custom group
using Active Directory Users and Computers. You can also select
computers using WMI filters, but this is beyond the scope of this
document.
3. When you are finished selecting computers, click on the name of
your Group Policy Object in the tree view again, and without
releasing the mouse button, drag the pointer to the name of the
domain or organization unit in which to install the software. The
pointer will change shape to a pointer with a "+". Release the
mouse button and click OK to link your Group Policy Object to this
domain. Repeat this process for any additional domains or
organizational units.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the software will be installed the next time the computer is
rebooted. The installation process will take several minutes.


Upgrading OpenOffice-Enterprise

The following instructions describe how to upgrade an existing Group
Policy installation to a new version of the OpenOffice-Enterprise client
software.

1. Download the new release of the OpenOffice-Enterprise client
software, as described in Step C of Download Software Packages
<http://openofficetechnology.com/node/25>.
2. Perform an administrative installation of the new release, as
described in Step C of Create Network Installation Images
<http://openofficetechnology.com/node/26>. CAUTION: Do not
overwrite the previous version; install the new release in a
different directory. Do not delete the previous version until you
are certain all desktops have been upgraded.
3. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then expand the tree
for "Group Policy Objects". Right-click on the Group Policy Object
used to install the previous version of OpenOffice, then select
"Edit...". This will open the Group Policy Object Editor.
4. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New --> Package...".
5. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
6. Navigate to the network location containing the administrative
installation of the new version of the OpenOffice-Enterprise
client software and and double-click on the .msi file
"ooewin-450.msi".
7. Select "Advanced" as the deployment method and click "OK". After a
short pause, the Properties dialog should appear.
8. Under the "Upgrade" tab, click "Add..." and under "Package to
upgrade", select "OpenOffice-Enterprise" and click "OK". The
properties dialog will display the text "Replace
OpenOffice-Enterprise".
9. The option "Uninstall this application when it falls out of the
scope of management" can be set under the "Deployment" tab. This
option will cause the application to be automatically uninstalled
if this group policy object is deleted or unlinked. Alternately,
the application can be uninstalled later by right-clicking on its
package name and selecting "All Tasks" -> "Remove..."
10. When all of the installation properties look correct, click "OK"
to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the new version of the OpenOffice-Enterprise client software
will be installed the next time the computer is rebooted. The
installation process will take only a few seconds.


Upgrading OpenOffice

The following instructions describe how to upgrade an existing Group
Policy installation to a new version of the OpenOffice.org office suite.

IMPORTANT: If you are upgrading to the latest v2.1 release of
OpenOffice, you must first upgrade to the latest release of the
OpenOffice-Enterprise client software, ooewin-450.msi. Prior releases of
the OpenOffice-Enterprise client software are not compatible with
OpenOffice v2.1.

1. Download the new release of OpenOffice, as described in Step B of
Download Software Packages <http://openofficetechnology.com/node/25>.
2. Perform an administrative installation of the new release, as
described in Step B of Create Network Installation Images
<http://openofficetechnology.com/node/26>. CAUTION: Do not
overwrite the previous version; install the new release in a
different directory. Do not delete the previous version until you
are certain all desktops have been upgraded.
3. Download the file Check_OOE.mst
<http://openofficetechnology.com/system/files?file=Check_OOE.mst>
and add it to the network installation directory.
4. Download any additional installation transform (.mst) files
<http://openofficetechnology.com/OpenOffice_Installation_Transforms>
you would like to use, and add them to the network installation
directory.
5. Launch the Group Policy Management console on your administrative
workstation. Expand the tree for your domain, then expand the tree
for "Group Policy Objects". Right-click on the Group Policy Object
used to install the previous version of OpenOffice, then select
"Edit...". This will open the Group Policy Object Editor.
6. In the Group Policy Object Editor, under "Computer Configuration",
expand "Software Settings", right-click on "Software Installation"
and select "New --> Package...".
7. Click on "My Network Places". (Note: This is a required step. You
must select the package to install from a network location rather
than a local location. If you do not first click on "My Network
Places", the selection of a package to install will not be accepted.)
8. Navigate to the network location containing the administrative
installation of the new version of OpenOffice and and double-click
on the .msi file "openofficeorg21.msi".
9. Select "Advanced" as the deployment method and click "OK". After a
short pause, the Properties dialog should appear.
10. Under the "Upgrade" tab, click "Add..." and under "Package to
upgrade", select "OpenOffice.org 2.0" and click "OK". The
properties dialog will display the text "Replace OpenOffice.org 2.0".
11. Under the "Modifications" tab, add Check_OOE.mst and the other
transforms you downloaded earlier (if any), then click "OK". The
selected transforms will appear in the properties dialog.
12. The option "Uninstall this application when it falls out of the
scope of management" can be set under the "Deployment" tab. This
option will cause the application to be automatically uninstalled
if this group policy object is deleted or unlinked. Alternately,
the application can be uninstalled later by right-clicking on its
package name and selecting "All Tasks" -> "Remove..."
13. When all of the installation properties look correct, click "OK"
to accept the properties, then close the Group Policy Object Editor.

The Group Policy Object will begin to propagate and will be applied on
each selected computer in the domain(s) within approx. 90 minutes
(depending on how Group Policy is configured). To apply the GPO
immediately on a particular computer, go to that computer and run
"gpupdate" from a command prompt. Once the Group Policy Object is
applied, the new version of OpenOffice will be installed the next time
the computer is rebooted. The installation process will take several
minutes.


Installation Troubleshooting

There a several methods to obtain information about the installation
process:

1. Installation failure and success messages are logged in each
computer's Application Event Log.
2. Group Policy and software installation operations can also be
logged. For more information, see the manual section /Logging
Group Policy and/or Software Installation/.

Eliminare chiavi di registro da file .reg

Eliminazione di chiavi e valori del Registro di sistema
Per eliminare una chiave del Registro di sistema con un file reg,
inserire un trattino (-) davanti al PercorsoRegistrodisistema nel file
reg. Per eliminare ad esempio la sottochiave Test dalla seguente chiave
del Registro di sistema:
HKEY_LOCAL_MACHINE\Software
inserire un trattino davanti alla seguente chiave nel file reg:
HKEY_LOCAL_MACHINE\Software\Test
L'esempio riportato di seguito corrisponde a un file reg che consente di
eseguire questa operazione.
[-HKEY_LOCAL_MACHINE\Software\Test]
Per eliminare un valore del Registro di sistema con un file reg,
inserire un trattino (-) dopo il segno di uguale (=) che segue il
NomeElementoDati nel file reg. Per eliminare ad esempio la sottochiave
TestValue dalla seguente chiave:
HKEY_LOCAL_MACHINE\Software\Test
inserire un trattino dopo "TestValue"= nel file reg. L'esempio riportato
di seguito corrisponde a un file reg che consente di eseguire questa
operazione.
HKEY_LOCAL_MACHINE\Software\Test
"TestValue"=-
Per creare il file reg, utilizzare Regedit.exe per esportare la chiave
del Registro di sistema che si desidera eliminare, quindi utilizzare il
Blocco note per modificare il file reg e inserire il trattino.

Dovecot - problema - il client continua a scaricare vecchi messaggi

Allora, forse ho individuato il problema...

[maillog]
Mar 19 08:50:59 zion dovecot: pop3-login: Login: user=<xxx@xxx.com>...
Mar 19 08:50:59 zion dovecot: pop3(xxx@xxx.com): mbox sync: Expunged
message reappeared in mailbox
/var/spool/mail/vhosts/xxx/xxx (U ID 7953 < 7976, seq=1, idx_msgs=0)
Mar 19 08:51:11 zion dovecot: pop3(xxx@xxx.com): mbox sync: UID inserted
in the middle of mailbox /var/spool/mail/vhosts/xxx.com/xxx (7976 >
7953, seq=1, idx_msgs=8)
[/maillog]

*************************************
http://wiki.dovecot.org/MboxProblems

If you insert messages, or if you "undelete" messages (eg. replace mbox
from a backup), you may see errors in Dovecot's logs:

mbox sync: UID inserted in the middle of mailbox /home/tss/mail/inbox
(817 > 787, seq=18, idx_msgs=32)

***************************************

probabilmente è stato modificato qlcs sui file mbox del dovecot che ora
impazzisce.

Secondo me la soluzione migliore è:

Far scaricare le caselle di posta da tutti i pc in cui sn configurate;
Cancellare i file mbox del dovecot, riavviare dovecot

Ciaoooooo

martedì 13 marzo 2007

Ricompilato e aggiornato apache modssl php

cd mod_ssl-2.8.28-1.3.37

./configure --with-apache=../../apache_1.3.37 --with-ssl=/usr/local/ssl
--enable-shared=ssl --with-mm=/usr/local

cd ../../apache_1.3.37

EAPI_MM="/usr/local" SSL_BASE="/usr/local/ssl" ./configure
--enable-module=so --enable-shared=ssl --enable-module=ssl
--enable-module=rewrite

make && make install

cd ../php/php-4.4.4

./configure --with-mysql=/usr/local/mysql --with-openssl=/usr/local/ssl
--with-apxs=/usr/local/apache/bin/apxs --enable-mbstring
--with-mm=/usr/local --with-zlib --with-gd

make && make install

aggiunto a httpd.conf

...
AddModule mod_rewrite.c
...

Ricompilazione php

è stato necessario ricompilare perchè mancava il supporto zlib e gd

./configure --with-mysql=/usr/local/mysql --with-openssl=/usr/local/ssl
--with-apxs=/usr/local/apache/bin/apxs --enable-mbstring
--with-mm=/usr/local --with-zlib --with-gd

poi nn si collegava al db, è stato necessario creare un link da
/tmp/mysql.sock a /var/lb/mysql/mysql.sock
e cambaire i permessi della dir /var/lib/mysql con un chmod ugo+x

MRSB - Sistema di prenotazione aule active directory windows server 2003 R2

Hi,
first of all, i'm sorry for my bad english!

I solved some problem occurred in ldap authentication with ADS Windows
2003 R2.

i've changed:

auth_ldap.inc in this manner:

function authValidateUser($user, $pass)
{
global $auth;
global $ldap_host;
global $ldap_base_dn;
global $ldap_user_attrib;
global $ldap_filter;
global $account_suffix; // <------- added LINE 26
...
...

// establish ldap connection
// the '@' suppresses errors
$ldap = @ldap_connect($ldap_host);
ldap_set_option($ldap, LDAP_OPT_PROTOCOL_VERSION, 3); // <-------- Added
line 77
ldap_set_option($ldap, LDAP_OPT_REFERRALS, 0); //disable plain text
passwords // <--------- Added line 78

// Check that connection was established
...
...


//if(@ldap_bind($ldap, $dn, $pass)) // <---- changed line 92 from ...
if(@ldap_bind($ldap, $user.$account_suffix, $pass)) // <--- ... to

...
...

i've configured
config.inc.php
like this:

# Where is the LDAP server
$ldap_host = "172.21.1.20";
$ldap_base_dn = "cn=users, dc=pippo, dc=local";
$account_suffix = "@pippo.local";
$ldap_user_attrib = "sAMAccountName";

In the follow line there was an error ...
#//$ldap_user_filter =
"memberOf=CN=ServicePrenotazioniSale,OU=ServiceGroup,dc=prvprato1,dc=local";

this is correct
$ldap_filter =
"memberOf=CN=ServicePrenotazioniSale,OU=ServiceGroup,dc=pippo,dc=local";


I hope someone can use this information to solve same problem.
Good bye.

P.S.
mrbs is a very good program!!!

Problemi con libmysqlclient.so e mysql binary installation

Ho scaricato ed estratto
MySQL-shared-4.1.18-0.i386.rpm
Poi ho copiato in /usr/local/mysql/lib
i file e i link che conteneva l'rpm
ho aggiunto /usr/local/mysql/lib in /etc/ld.so.conf
e ho lancato ldconfig


Fonte:

http://www.elbnet.com/supportlinks/mysql/manual_Placeholder.html


M.2.4 Problems Using the Perl |DBI|/|DBD| Interface
<http://www.elbnet.com/supportlinks/mysql/manual_toc.html#Perl_support_problems>

If Perl reports that it can't find the `../mysql/mysql.so' module, then
the problem is probably that Perl can't locate the shared library
`libmysqlclient.so'.

You can fix this by any of the following methods:

* Compile the |Msql-Mysql-modules| distribution with |perl
Makefile.PL -static -config| rather than |perl Makefile.PL|.
* Copy |libmysqlclient.so| to the directory where your other shared
libraries are located (probably `/usr/lib' or `/lib').
* On Linux you can add the pathname of the directory where
`libmysqlclient.so' is located to the `/etc/ld.so.conf' file.
* Add the pathname of the directory where `libmysqlclient.so' is
located to the |LD_RUN_PATH| environment variable.

If you get the following errors from |DBD-mysql|, you are probably using
|gcc| (or using an old binary compiled with |gcc|):

/usr/bin/perl: can't resolve symbol '__moddi3'
/usr/bin/perl: can't resolve symbol '__divdi3'

Add |-L/usr/lib/gcc-lib/... -lgcc| to the link command when the
`mysql.so' library gets built (check the output from |make| for
`mysql.so' when you compile the Perl client). The |-L| option should
specify the pathname of the directory where `libgcc.a' is located on
your system.

Another cause of this problem may be that Perl and MySQL aren't both
compiled with |gcc|. In this case, you can solve the mismatch by
compiling both with |gcc|.

If you get the following error from |Msql-Mysql-modules| when you run
the tests:

t/00base............install_driver(mysql) failed: Can't load '../blib/arch/auto/DBD/mysql/mysql.so' for module DBD::mysql: ../blib/arch/auto/DBD/mysql/mysql.so: undefined symbol: uncompress at /usr/lib/perl5/5.00503/i586-linux/DynaLoader.pm line 169.

it means that you need to include the compression library, -lz, to the
link line. This can be doing the following change in the file
`lib/DBD/mysql/Install.pm':

$sysliblist .= " -lm";

to

$sysliblist .= " -lm -lz";

After this, you MUST run 'make realclean' and then proceed with the
installation from the beginning.

If you want to use the Perl module on a system that doesn't support
dynamic linking (like SCO) you can generate a static version of Perl
that includes |DBI| and |DBD-mysql|. The way this works is that you
generate a version of Perl with the |DBI| code linked in and install it
on top of your current Perl. Then you use that to build a version of
Perl that additionally has the |DBD| code linked in, and install that.

On SCO, you must have the following environment variables set:

shell> LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib:/usr/progressive/lib
or
shell> LD_LIBRARY_PATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:/usr/progressive/lib:/usr/skunk/lib
shell> LIBPATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:/usr/progressive/lib:/usr/skunk/lib
shell> MANPATH=scohelp:/usr/man:/usr/local1/man:/usr/local/man:/usr/skunk/man:

First, create a Perl that includes a statically linked |DBI| by running
these commands in the directory where your |DBI| distribution is located:

shell> perl Makefile.PL -static -config
shell> make
shell> make install
shell> make perl

Then you must install the new Perl. The output of |make perl| will
indicate the exact |make| command you will need to execute to perform
the installation. On SCO, this is |make -f Makefile.aperl inst_perl
MAP_TARGET=perl|.

Next, use the just-created Perl to create another Perl that also
includes a statically-linked |DBD::mysql| by running these commands in
the directory where your |Msql-Mysql-modules| distribution is located:

shell> perl Makefile.PL -static -config
shell> make
shell> make install
shell> make perl

Finally, you should install this new Perl. Again, the output of |make
perl| indicates the command to use.

Vi / Vim e cron... la soluzione a tutti i miei problemi

Da sempre uso vim (e lo invoco con il comando vi).
Su slackware, dopo l'insatllazione, la prima operazione che faccio è:
rm /usr/bin/vi
ln -s /usr/bin/vim /usr/bin/vi
e subito dopo
cp /usr/share/vim/vim63/vimrc_example.vim /root/.vimrc

il problema sta proprio in questo...
in /usr/share/vim/vim63/vimrc_example.vim ci sono delle impostazioni
che creano problemi con il funzionamento di cron
infatti, il comando crontab -e (lancato da root) nn mi funzionava e
nonostante apportassi modifiche cron nn se ne accorgeva neanche.
Tutto ok, invece, se lanciavo lo stesso comando x altri utenti
crontab -e -u pippo
tutto OK!!

Per risolvere è bastato aggiungere in /root/.vimrc la seguente riga

set backupcopy=yes

subito dopo la riga

set nocompatible

Adesso tutto funziona perfettamente.

Problemi con lilo... Come risolverli con Knoppix

Avviare knoppix (meglio con knoppix lang=it)

editare /etc/fstab
aggiungere alla partizione da montare
dopo nouser,exec
,dev
-----

adesso dare mount /mnt/sda1
poi
chroot /mnt/sda1
mount -t none /proc
poi lilo -C /etc/lilo.conf -v -t
poi lilo -C /etc/lilo.conf -v


Saluti a tutti!!!

Squid - NTLM_AUTH - Permessi in base al gruppo

INTERESSANTE
Fonte:
http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/ntlm_auth.1.html

To setup ntlm_auth for use by squid 2.5 with
group limitation in addi-tion to the above example,
the following should be added to the
_squid.conf_ file.


auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp \
--require-membership-of='WORKGROUP\Domain Users'

auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic \
--require-membership-of='WORKGROUP\Domain Users'

Winbindd e Squid - Errore in avvio

Winbindd non parte e da il seguente errore:


invalid permissions on socket directory /var/lib/samba/winbindd_privileged


Soluzione:

chown -R root:squid /var/lib/samba/winbindd_privileged
chmod -R u+rwx /var/lib/samba/winbindd_privileged
chmod -R g-w /var/lib/samba/winbindd_privileged
chmod -R g+rx /var/lib/samba/winbindd_privileged
chmod -R o-rwx /var/lib/samba/winbindd_privileged

Sendmail - Forzare l'invio della posta

/usr/lib/sendmail -v -q -C/etc/mail/sendmail.cf

Configurazione di htdig + apache

Tutto nacque diversi anni fa... un buon progetto.. la raccolta del
sapere...

perchè, visto che siamo una classe affiatata e ci vogliamo un bene
dell'anima...
perchè non condividere il sapere fra noi e con il resto del mondo?

A tutti può far comodo...

Quindi, visto che nel frattempo nessuno si è mosso e te hai messo a
disposizione una
gran bella cosa (slack + adsl flat) (oltre al culo del quale però
disponiamo, chi +
chi – ormai da diversi anni) ho deciso di iniziare a pubblicare qualcosa.


Ho creato un file:

/etc/apache/documentazione.conf


ScriptAlias //cgi-bin// "//opt/www/cgi-bin//"
<Directory //opt/www/cgi-bin//>
AllowOverride None
Options +ExecCGI
FollowSymLinks
</Directory>

Alias //htdig// "//opt/www/htdocs/htdig//"
<Directory "/opt/www/htdocs/htdig">
order allow,deny
Allow from all
Options Indexes FollowSymLinks
</Directory>

<Directory "/web/http/documentazione">
Options Indexes FollowSymlinks MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>


Ho creato la directory /web/http/documentazione [dove verrà messa la
documentazione che scriviamo/troviamo/ecc...]


Ho modificato la configurazione di default di htdig come segue:

/opt/www/htdig/conf/htdig.conf


# # Example config file for ht://Dig.
# # This configuration file is used by all the programs that make up ht://Dig.
# Please refer to the attribute reference manual for more details on what
# can be put into this file. (http://www.htdig.org/confindex.html)
# Note that most attributes have very reasonable default values so you
# really only have to add attributes here if you want to change the defaults.
# # What follows are some of the common attributes you might want to change. #
# # Specify where the database files need to go. Make sure that there is
# plenty of free disk space available for the databases. They can get
# pretty big. #

database_dir: /opt/www/htdig/db

# # This specifies the URL where the robot (htdig) will start. You can specify
# multiple URLs here. Just separate them by some whitespace.
# The example here will cause the ht://Dig homepage and related pages to be
# indexed. # You could also index all the URLs in a file like so:
# start_url: `${common_dir}/start.url`
#

start_url:

http://www.maurizio.proietti.name/

#
# This attribute limits the scope of the indexing process. The default is to
# set it to the same as the start_url above. This way only pages that are on
# the sites specified in the start_url attribute will be indexed and it will
# reject any URLs that go outside of those sites.
# # Keep in mind that the value for this attribute is just a list of string
# patterns. As long as URLs contain at least one of the patterns it will be
# seen as part of the scope of the index. #

limit_urls_to: ${start_url}documentazione

# # If there are particular pages that you definitely do NOT want to index, you
# can use the exclude_urls attribute. The value is a list of string patterns.
# If a URL matches any of the patterns, it will NOT be indexed. This is
# useful to exclude things like virtual web trees or database accesses. By
# default, all CGI URLs will be excluded. (Note that the //cgi-bin// convention
# may not work on your web server. Check the path prefix used on your web
# server.) #

exclude_urls: //cgi-bin// .cgi

# # Since ht://Dig does not (and cannot) parse every document type, this
# attribute is a list of strings (extensions) that will be ignored during
# indexing. These are **only** checked at the end of a URL, whereas
# exclude_url patterns are matched anywhere.
#

bad_extensions: .wav .gz .z .sit .au .zip .tar .hqx .exe .com .gif \
.jpg .jpeg .aiff .class .map .ram .tgz .bin .rpm .mpg .mov .avi .css

# # The string htdig will send in every request to identify the robot. Change
# this to your email address. #

maintainer: m.proietti@aaa.it <mailto:m.proietti@maurizio.proietti.name>

# # The excerpts that are displayed in long results rely on stored information
# in the index databases. The compiled default only stores 512 characters of
# text from each document (this excludes any HTML markup...) If you plan on
# using the excerpts you probably want to make this larger. The only concern
# here is that more disk space is going to be needed to store the additional
# information. Since disk space is cheap (! :-)) you might want to set this
# to a value so that a large percentage of the documents that you are going
# to be indexing are stored completely in the database. At SDSU we found
# that by setting this value to about 50k the index would get 97% of all
# documents completely and only 3% was cut off at 50k. You probably want to
# experiment with this value.
# Note that if you want to set this value low, you probably want to set the
# excerpt_show_top attribute to false so that the top excerpt_length characters
# of the document are always shown. #

max_head_length: 10000

# # To limit network connections, ht://Dig will only pull up to a certain limit
# of bytes. This prevents the indexing from dying because the server keeps
# sending information. However, several FAQs happen because people have files
# bigger than the default limit of 100KB. This sets the default a bit higher.
# (see <http://www.htdig.org/FAQ.html> for more) #

max_doc_size: 200000

# # Most people expect some sort of excerpt in results. By default, if the
# search words aren't found in context in the stored excerpt, htsearch shows
# the text defined in the no_excerpt_text attribute:
# (None of the search words were found in the top of this document.)
# This attribute instead will show the top of the excerpt.
#

no_excerpt_show_top: true

# # Depending on your needs, you might want to enable some of the fuzzy search
# algorithms. There are several to choose from and you can use them in any
# combination you feel comfortable with. Each algorithm will get a weight
# assigned to it so that in combinations of algorithms, certain algorithms get
# preference over others. Note that the weights only affect the ranking of
# the results, not the actual searching. # The available algorithms are:
# accents
# exact
# endings
# metaphone
# prefix
# soundex
# substring
# synonyms
# By default only the "exact" algorithm is used with weight 1.
# Note that if you are going to use the endings, metaphone, soundex, accents,
# or synonyms algorithms, you will need to run htfuzzy to generate
# the databases they use. #

search_algorithm: exact:1 synonyms:0.5 endings:0.1

# # The following are the templates used in the builtin search results
# The default is to use compiled versions of these files, which produces
# slightly faster results. However, uncommenting these lines makes it
# very easy to change the format of search results.
# See <http://www.htdig.org/hts_templates.html> for more details. #
# template_map: Long long ${common_dir}/long.html \
# Short short ${common_dir}/short.html
# template_name: long
# # The following are used to change the text for the page index.
# The defaults are just boring text numbers. These images spice
# up the result pages quite a bit. (Feel free to do whatever, though)
#

next_page_text:
<img src="/htdig/buttonr.gif" border="0" align="middle" width="30" height="30" alt="next">
no_next_page_text: prev_page_text:
<img src="/htdig/buttonl.gif" border="0" align="middle" width="30" height="30" alt="prev">
no_prev_page_text: page_number_text:
'<img src="/htdig/button1.gif" border="0" align="middle" width="30" height="30" alt="1">' \
'<img src="/htdig/button2.gif" border="0" align="middle" width="30" height="30" alt="2">' \
'<img src="/htdig/button3.gif" border="0" align="middle" width="30" height="30" alt="3">' \
'<img src="/htdig/button4.gif" border="0" align="middle" width="30" height="30" alt="4">' \
'<img src="/htdig/button5.gif" border="0" align="middle" width="30" height="30" alt="5">' \
'<img src="/htdig/button6.gif" border="0" align="middle" width="30" height="30" alt="6">' \
'<img src="/htdig/button7.gif" border="0" align="middle" width="30" height="30" alt="7">' \
'<img src="/htdig/button8.gif" border="0" align="middle" width="30" height="30" alt="8">' \
'<img src="/htdig/button9.gif" border="0" align="middle" width="30" height="30" alt="9">' \
'<img src="/htdig/button10.gif" border="0" align="middle" width="30" height="30" alt="10">'

# # To make the current page stand out, we will put a border around the
# image for that page. #

no_page_number_text:
'<img src="/htdig/button1.gif" border="2" align="middle" width="30" height="30" alt="1">' \
'<img src="/htdig/button2.gif" border="2" align="middle" width="30" height="30" alt="2">' \
'<img src="/htdig/button3.gif" border="2" align="middle" width="30" height="30" alt="3">' \
'<img src="/htdig/button4.gif" border="2" align="middle" width="30" height="30" alt="4">' \
'<img src="/htdig/button5.gif" border="2" align="middle" width="30" height="30" alt="5">' \
'<img src="/htdig/button6.gif" border="2" align="middle" width="30" height="30" alt="6">' \
'<img src="/htdig/button7.gif" border="2" align="middle" width="30" height="30" alt="7">' \
'<img src="/htdig/button8.gif" border="2" align="middle" width="30" height="30" alt="8">' \
'<img src="/htdig/button9.gif" border="2" align="middle" width="30" height="30" alt="9">' \
'<img src="/htdig/button10.gif" border="2" align="middle" width="30" height="30" alt="10">'
# local variables:
# mode: text
# eval: (if (eq window-system 'x) (progn (setq
font-lock-keywords (list '("^#.*" . font-lock-keyword-face)
'("^[a-zA-Z][^ :]+" . font-lock-function-name-face)
'("[+$]*:" . font-lock-comment-face) )) (font-lock-mode)))

# end:


Ed ho creato un file documentazione.html


<html lang="it">
<head>
<title>www.maurizio.proietti.name <http://www.maurizio.proietti.name> - Home Page</title>
</head>
<BODY background="./image/slack_bg.jpg" text="black" link="black" vlink="Black">
<font size="+4">
<strong><em><div align="center">www.maurizio.proietti.name <http://www.maurizio.proietti.name></div></em></strong>
</font>
<br><br><br><br>
<div align="left">
<strong><em><font size="+2">
<a href="http://www.maurizio.proietti.name/htdig/search.html" <http://www.maurizio.proietti.name/htdig/search.html>>Cerca nella Documentazione</a>
</font></em></strong>
</div>
<br><br>
<div align="left">
<strong><em><font size="+2">
<a href="http://www.maurizio.proietti.name/documentazione/" <http://www.maurizio.proietti.name/documentazione/>>Sfoglia la Documentazione</a>
</font></em></strong>
</div>
</body>
</html>


In pratica il funzionamento è il seguente:

Chi si collega a www.maurizio.proietti.name <http://www.maurizio.proietti.name/> vede
fra i link della home page un link a
documentazione.html che gli fa scegliere se sfogliare la documentazione
(cioè consultare la lista dei file contenuti nella directory) oppure
effettuare una ricerca con htdig.

Htdig non fa altro che indicizzare i file presenti nella sola directory
documentazione e permette ricerche mirate.

A questo punto mancherebbe soltanto la possibilità di uploadare
direttamente
la documentazione tramite un ftp con un utente e password conosciuta
solo da noi.

USB Mass Storage device con udev e Kernel 2.6.x

udev How to
[origine: http://www.slacky.it/tutorial/udev/HOWTO-udev.html]


Con questo Howto ho la presunzione di voler essere d'aiuto a chi desidera automatizzare il sistema di riconoscimento e di mounting di device USB quali pen drive, Hard Disk, Card Reader etc.


Premessa

Ultimamente mi sono ritrovato a possedere sempre piu' dispositivi USB e ad avere la necessita' di automatizzare la gestione degli stessi.
Piu' esattamente possego un Pen Drive, un HD esterno, una fotocamera digitale, un card reader e un lettore MP3. Tutti questi dispositivi funzionano benissimo sotto Linux essendo gestiti perfettamente come USB Mass Storage devices.
La cosa piu' snervante e' che bisogna sempre andare a vedere dove il sistema crea i block device per poter montare correttamente il dispositivo.
Ad esempio la prima partizione del mio HD viene riconosciuta come /dev/sda1, se pero' lo monto insieme al Pen Drive allora sara' riconosciuto come /dev/sdb1 e cosi' via.
Questo mi impedisce di poter creare delle entry fisse nel mio fstab.
Dopo un po' di ricerche ecco che finalmente trovo la soluzione con udev.



Requisiti

  1. Un PC (eh eh) con Linux (preferibilmente Slckware).

  2. Kernel della serie 2.6.x (io uso la 2.6.6) scaricabile da www.kernel.org con supporto sysfs

  3. Hotplug scaricabile dalla current di Slackware

  4. udev scaricabile da www.kernel.org/pub/linux/utils/kernel/hotplug/



Preparazione

Compiliamo la ns. Kernel come al solito ricordandoci di settare in General setup :

Support for hot-pluggable devices

Assicuriamoci che sysfs sia montato. Per fare cio' aggiungiamo una linea al nostro fstab del tipo :
none /sys sysfs defaults
diamo un bel:
mount -a
et voila'.



Installazione

Una volta scaricati i sorgenti di udev scompattiamo il pacchetto con :
tar -xzf udev-XXX.tar.gz (dove XXX e' la versione di udev che avete scaricato).
Andiamo nella directory appena creata con:
cd udev-XXX
e diamo un bel:
make

se non avvengono catastrofi nella compilazione possiamo tranquillamente installare il tutto con:
make install
A questo punto dobbiamo copiare lo script di avvio di udev nella nostra /etc/rc.d. Lo script opportuno si trova nella directory extra dei sorgenti e si chiama start_udev lo copiamo con :
cp extra/start_udev /etc/rc.d
Bisogna ora fare in modo che lo script sia eseguito all'avvio, modifichiamo il file rc.local aggiungendo la linea /etc/rc.d/start_udev.



Configurazione

Passiamo dunque alla configurazione di udev. Nella directory /etc/udev troviamo il file udev.conf apriamolo con il ns. editor favorito e cerchiamo la linea:

# udev_rules - The name and location of the udev rules file
udev_rules="/etc/udev/rules.d/"

Modifichiamola con :

udev_rules="/etc/udev/udev.rules

Questo dira' ad udev dove trovare il file di definizione delle regole (ARRGH non sono riuscito a tradurlo meglio !)

Ora dobbiamo scrivere le regole per l'identificazione delle ns. devices USB. Per fare questo dobbiamo conoscere qualcosa dei nostri dispositivi, piu' precisamente il “vendor” e il “model” che altro non sono che il “venditore” e il “modello”. Per avere queste informazioni possiamo avvalerci dell' utility udevinfo procedendo come segue:
attacchiamo il dispositivo che vogliamo identificare e digitiamo :
dmesg
qu dovremmo vedere alla fine un messaggio del tipo :

scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: WDC WD60 Model: 0AB-60CBA0 Rev: 03.0
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sda: 117231409 512-byte hdwr sectors (60022 MB)
sda: assuming drive cache: write through
sda: sda1 sda2
Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi1, channel 0, id 0, lun 0, type 0
USB Mass Storage device found at 2

(questo e' l'output di dmesg dopo che ho attaccato il mio HD esterno).
Sappiamo quindi che il dispositivo e' attacato su “/dev/sda epossiamo con udevinfo interrogare il path adeguato:
udevinfo -a -p /sys/block/sda
l'output sara' pressapoco questo:

udevinfo starts with the device the node belongs to and then walks up the
device chain, to print for every device found, all possibly useful attributes
in the udev key format.
Only attributes within one device section may be used together in one rule,
to match the device for which the node will be created.


looking at class device '/sys/block/sda':
SYSFS{dev}="8:0"
SYSFS{range}="16"
SYSFS{size}="117231409"
SYSFS{stat}=" 68 7 75 273 0 0 0 0 0 273 273"


follow the class device's "device"
looking at the device chain at '/sys/devices/pci0000:00/0000:00:0b.0/usb2/2-1/2-1:1.0/host1/1:0:0:0':
BUS="scsi"
ID="1:0:0:0"
SYSFS{detach_state}="0"
SYSFS{device_blocked}="0"
SYSFS{max_sectors}="240"
SYSFS{model}="0AB-60CBA0 "
SYSFS{queue_depth}="1"
SYSFS{rev}="03.0"
SYSFS{scsi_level}="3"
SYSFS{state}="running"
SYSFS{type}="0"
SYSFS{vendor}="WDC WD60"



Guardiamo nella sezione che contiene il BUS scsi .
Qui abbiamo le informazioni che ci interessano per scrivere il nostro udev.rules, riapriamo il ns editor e aggiungiamo questa linea a udev.rules:
BUS="scsi", SYSFS{vendor}="WDC WD60",SYSFS{model}="0AB-60CBA0", NAME="exthd%n"
Facciamo attenzione ad eventuali spazi nei nomi !!
Abbiamo cosi' detto ad udev che quando questa device viene attaccata deve creare un node che si chiama “exthd%n” dove %n e' il numero di partizione che verra' rilevata.
La prossima volta che attaccheremo il dispositivo compariranno (per miracolo ?) nella directory /udev due block devices che si chiamano exthd1 e exthd2.
Possiamo ora usare queste block devices per montare il nostro disco al posto di /dev/sda1 e /dev/sda2
A tal proposito scriviamo nel nostro fstab le seguenti linee :
/udev/exthd1 /mnt/extern/FAT32 vfat noauto,users,gid=100,umask=3 0 0
/udev/exthd2 /mnt/extern/Linux auto noauto,users

(Nel mio caso la prima partizione dell'HD e' Fat32 e la seonda e' ext3)
Arrivati fin qui non ci resta che montare il nostro dispositivo con:
mount /udev/exthd1
OHHHH funziona ! Ma se siamo veramente pigri e non vogliamo neanche dare il mount ?
Ecco che udev puo' aiutarci anche nell'automount.



AUTOMOUNT

Durante l'installazione di udev e' stata creata una directory /etc/dev.d/. E' li' che andremo a “smanettare” per poter far funzionare il nostro automount.
Udev per ogni device “creata” si va a cercare in /etc/dev.d/ una directory che abbia lo stesso nome della device. Nel nostro esempio dopo aver attaccato l'HD esterno si a a cercare una directory /etc/dev.d/exthd1 e una volta trovata esegue tutto cio' che termina con estensione “.dev”
Non ci resta quindi che crearci una directory con :
mkdir /etc/dev.d/exthd1
e all'interno di questa creare uno script pressappoco cosi' :

#!/bin/bash
if [ "$ACTION" == "add" ] ; then
logger -t dev.d "Mounting external HD"
/bin/mount /mnt/extern/FAT32
fi
if [ "$ACTION" == "remove" ] ; then
logger -t dev.d "Unmounting external HD"
/bin/umount /mnt/extern/FAT32
fi

Udev usa le stesse regole di Hotplug per quel che riguarda ACTION ( fate riferimento al man di Hotplug)
Questo script verra' eseguito, ogni volta che la device verra' attaccata o staccata dal sistema. L'esecuzione avviene come utente root per cui facciamo in modo che nel fstab i permessi di accesso siano settati secondo le nostre esigenze.

Buon divertimento !!!

Credits

Questo Howto e' stato scritto scopiazzando varie cose che ho trovato sulla rete e che mi sono state utili a capire il funzionamento di udev.
Udev e' fornito di una piccola documentazione che si trova nella directory dei sorgenti, non molto in verita', ma si puo' benissimo integrare con quel meraviglioso strumento che e' Internet.
Attenzione udev non e' solo questo, in futuro rimpiazzera' del tutto (forse) il devfs tradizionale.
Ringrazio tutti gli iscritti a Slacky.it che mi hanno aiutato dopo anni di Distro porfessionali a ributtarmi nell'avventura Slackware.

A mio figlio Jan

Sal Paradiso Giugno 2004

Installazione da sorgenti - problema con le librerie

Problema:durante l'installazione di un programma  dai sorgenti
(con il classico ./configure && make && make install)
l'installazione nn va a buon fine perchè le librerie e i file *.la
(per es. /usr/lib/libgmodule-2.0.la)
vengono cercati in /usr/lib invece che in /usr/local/lib

A me è successo dopo aver installato dai sorgenti
gtk2, gtkmm, ecc

In questo caso ci sono 3 modi che possono risolvere il
problema:

1) export LDFLAGS=-Wl,-R/usr/local/lib && ./configure

2) Creare link simbolici:
cd /usr/local/lib
for i in `ls *.la`
do
ln -s $i /usr/lib/$i
done

3) Controllare e modificare il parametro 'dependency_libs' nei file *.la
(che sono editabili con un qualsiasi editor di testi)
in modo che comprenda anche la path /usr/local/lib

Installare software da CVS - Errore - Checking for forbidden M4 macros...

dopo aver scaricato il sw occorre lanciare ./autogen.sh

può capitare che il comando restituisca il seguente errore:

Checking for forbidden M4 macros...
***Error***: some autoconf macros required to build gtkhtml2
were not found in your aclocal path, or some forbidden
macros were found. Perhaps you need to adjust your
ACLOCAL_FLAGS?

in tal caso si può risolvere con il comando:

ACLOCAL_FLAGS="-I /usr/local/share/aclocal"
./autogen.sh

in seguito

make
[root]
make install

Outlook Web Access (OWA): Dividere Front-end (su internet) da Back-end (in LAN): Aumentare la sicurezza di OWA

Hardware & Software utilizzati:

Server con installato Windows 2000 server e Microsoft Exchange 5.5 e
Outlook Web Access che gestisce le caselle di posta di tutti gli utenti
della rete.
Server Pentium II 300 MHz con installato Slackware.

Disinstallo apache mysql php openssl e scarico i seguenti sorgenti:

[mysql-standard-4.1.14-pc-linux-gnu-i686-glibc23.tar.gz]
openssl-0.9.7h.tar.gz
openssh
php-4.4.0.tar.gz
httpd-2.0.54.tar.gz

X installare openssl:
./config shared
make
make test
make install

X installare openssh:
./configure
make
make install


X installare httpd2+php+mysql:
httpd2:
./configure --enable-so --enable-cgi --enable-info --enable-rewrite --enable-speling --enable-usertrack --enable-deflate  --enable-ssl --enable-mime-magic --enable-ext-filter --enable-proxy --enable-proxy-connect --enable-proxy-ftp --enable-proxy-http --enable-modules=all
make
make install

cd ../php-NN
./configure --with-apxs2=/usr/local/apache2/bin/apxs --with-mysql=/usr/local/mysql
make
make install


A questo punto creo un certificato self-signed x iis
come descritto nel seguente link:
http://dejavu.mu.nu/archives/080563.php

che riporto di seguito:


######################################################################################################
May 10, 2005
Self-Signed IIS SSL Certificates using OpenSSL

Self-Signed IIS SSL Certificates using OpenSSL

This tutorial assumes that you have a Linux box with OpenSSL installed,and that you want to create a self-signed certificate for IIS5.0

1. Set up your CA (you only have to do this once)
ON THE LINUX BOX...
* Create a private key

openssl genrsa -des3 -out CA.key 1024

(You'll need to supply a passphrase. DON'T FORGET THIS!!)

* Set this to read-only for root for security

chmod 400 CA.key

* Create the CA certificate

openssl req -new -key CA.key -x509 -days 1095 -out CA.crt

(Provide appropriate responses to the prompts...for Common Name, you might want to use something like "OurCompany CA")

* Set the certificate to read-only for root for security

chmod 400 CA.crt

2. Obtain a CSR
ON THE IIS BOX...
* Open the Internet Manager
* Select the site for which you want to create a key
* Right-click and choose Properties
* Select the "Directory Security" tab
* Click the "Server Certificate" button
* Follow the prompts to create a CSR
* Save your CSR, then transfer it to the Linux box for further processing. (For the following steps, we'll refer to your CSR as "new.csr")

3. Sign the CSR
ON THE LINUX BOX...
* Sign the CSR (all of this on one line)

openssl x509 -req -days 365 -in new.csr -CA CA.crt -CAkey CA.key -CAcreateserial -out new.crt

* Transfer the new.crt file back to the IIS box

4. Install self-signed certificate
ON THE IIS BOX...
* Open the Internet Manager
* Select the site to install the key
* Right-click and choose properties
* Select the "Directory Security" tab
* Click the "Server Certificate" button
* Specify that you want to complete the pending request
* Select the .crt file that you just transferred

That's it!

Now...here's the updated info, with special thanks to David MacKenzie:David's comments: I found your instructions for creating a self-signed cert for IIS using OpenSSL invaluable--thanks! (I found them by google.) There's one subtlety I'd like to suggest you add to them. If the IIS server is Outlook Web Access for an Exchange server, then installing the SSL cert breaks Public Folders administration from the Exchange System Manager MMC console. ESM complains that the cert isn't connected to a recognized authority, and if you fix that, it complains that the system name is wrong. After more googling, I found an answer that worked for me, shown below as additional steps for your check list. I'm using Windows 2000 SP3 and Exchange 2000 SP3.

1. If the IIS server is running Outlook Web Access for Exchange, make ourselves recognized as a CA
ON THE IIS BOX...
* Open Internet Explorer
* Tools>Internet Options
* Content tab
* Certificates
* Import
* Next
* Browse
* Files of type: X.509 Certificate (*.cer, *.crt)
* Select CA.crt
* Open
* Next
* Next
* Finish
2. If the IIS server is running Outlook Web Access for Exchange, fix Public Folders management for the Exchange Server Manager
ON THE IIS BOX...
* Open Internet Services Manager
* Right-click on exchange>Default Web Site>Exadmin
* Properties
* Directory Security tab
* Secure communications Edit
* Uncheck Require secure channel (SSL)
* OK
* OK
Posted by MoMo at May 10, 2005 11:32 AM

##################################################################################################

A questo punto iis disporrà di un certificato e quindi potrà comunicare in https

Iniziamo a configurare apache2 per funzionare come proxy
(fruttando il mod_proxy)


Prima di tutto occorre creare un certificato per il server apache come segue:
[ripresa dal sito:
http://www.vanemery.com/Linux/Apache/apache-SSL.html
]


###################################################################################################



Step 1: Setup your own CA (Certificate Authority)

In order to run a secure (SSL/TLS encrypted) web server, you have to have a private key and a certificate for the server. For a commercial web site, you will probably want to purchase a certificate signed by a well-known root CA. For Intranet or special-purpose uses like this, you can be your own CA. This is done with the OpenSSL tools.

Here, we will make a private CA key and a private CA X.509 certificate. We will also make a directory for the certs and keys:

[root]# mkdir /root/CA
[root]# chmod 0770 /root/CA
[root]# cd /root/CA

[root]# openssl genrsa -des3 -out my-ca.key 2048
Generating RSA private key, 2048 bit long modulus
.....................................................+++
...................................................+++
e is 65537 (0x10001)
Enter PEM pass phrase:
Verifying password - Enter PEM pass phrase:

[root]# openssl req -new -x509 -days 3650 -key my-ca.key -out my-ca.crt
Using configuration from /usr/share/ssl/openssl.cnf
Enter PEM pass phrase:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [GB]:US
State or Province Name (full name) [Berkshire]:Kentucky
Locality Name (eg, city) [Newbury]:Fayette County
Organization Name (eg, company) [My Company Ltd]:VanEmery.Com
Organizational Unit Name (eg, section) []:Certificate Authority
Common Name (eg, your name or your server's hostname) []:VanEmery.Com CA
Email Address []:hostmaster@vanemery.com

[root]# openssl x509 -in my-ca.crt -text -noout

Notes:  The first OpenSSL command makes the key. The second command makes the X.509 certificate with a 10-year lifetime. The third command lets you view the completed certificate. Make sure that you keep the password in a safe place, you will need this every time you sign another certificate! You will probably also want to make backups of the cert and key and lock them in a safe place.



Step 2: Make a key and a certificate for the web server:

Now, we have to make an X.509 certificate and corresponding private key for the web server. Rather than creating a certificate directly, we will create a key and a certificate request, then "sign" the certificate request with the CA key we made in Step 1. You can make keys for multiple web servers this way. One thing to note is that SSL/TLS private keys for web servers need to be either 512 or 1024 bits. Any other key size may be incompatible with certain browsers.

[root]# openssl genrsa -des3 -out mars-server.key 1024
Generating RSA private key, 1024 bit long modulus
....++++++
.++++++
e is 65537 (0x10001)
Enter PEM pass phrase:
Verifying password - Enter PEM pass phrase:

You could also create a private key without file encryption:

[root]# openssl genrsa -out mars-server.key 1024



[root]# openssl req -new -key mars-server.key -out mars-server.csr
Using configuration from /usr/share/ssl/openssl.cnf
Enter PEM pass phrase:
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter '.', the field will be left blank.
-----
Country Name (2 letter code) [GB]:TW
State or Province Name (full name) [Berkshire]:Taipei County
Locality Name (eg, city) [Newbury]:Nankang
Organization Name (eg, company) [My Company Ltd]:VanEmery.Com
Organizational Unit Name (eg, section) []:Web Services
Common Name (eg, your name or your server's hostname) []:mars.vanemery.com <=== This must be the real FQDN of your server!!!
Email Address []:hostmaster@vanemery.com

Please enter the following 'extra' attributes
to be sent with your certificate request
A challenge password []:
An optional company name []:

# openssl x509 -req -in mars-server.csr -out mars-server.crt -sha1 -CA my-ca.crt -CAkey my-ca.key -CAcreateserial -days 3650
Signature ok
subject=/C=TW/ST=Taipei County/L=Nankang/O=VanEmery.Com/OU=Web Services/CN=mars.vanemery.com/Email=hostmaster@vanemery.com
Getting CA Private Key
Enter PEM pass phrase:

[root]# openssl x509 -in mars-server.crt -text -noout

Make sure that your server name is the same as the FQDN that your clients will use when connecting to your site. Also, let's get in the habit of protecting our keys with appropriate permissions:

[root]# chmod 0400 *.key

Now, we need to move the new keys and certs into the proper directories in the /etc/httpd hierarchy:

[root]# cp mars-server.crt /etc/httpd/conf/ssl.crt
[root]# cp mars-server.key /etc/httpd/conf/ssl.key
[root]# cp my-ca.crt /etc/httpd/conf/ssl.crt



######################################################################################################

La documentazione l'ho trovata nel seguente link:
http://www.sikurezza.org/ml/03_04/msg00041.html

che riporto di seguito per comodità


#####################################################################################################

How to make Apache working with OWA (OutLook web access), using mod_proxy.


Table of Content:

1. The purpose of the document
2. What we need
3. Configuration
4. TroubleShooting.


1. PURPOSE OF THE DOCUMENT


Sometimes someone ask us to make possible to access his e-mail account from
Internet. In best cases we can use a simple and powerful web-mail, but in
worst cases we MUST use OWA, AKA Outlook Web Access.

The problem is twice:

1) Using Exchange server 5.5 or 2000 in normal edition we can't separate OWA
from the Exchange Machine.
2) Using OWA, we MUST use IIS that we know suxXXs in security.

So, to avoid these problems we can use Apache mod_proxy to:

 + Separate services to a FrontEnd <-> BackEnd scenario
 + Putting IIS in a DMZ and make that most attacks were made to the
front-end Apache (that is better).



The purpose of this document is how to install and, of course, make work
Apache mod_proxy to make possible to access OWA trought IIS.

The scenario we'll be:

Client ----> Apache (mod_proxy) <------> IIS-Exchange



2. WHAT WE NEED

Naturally we need:

  + A Working Exchange 2000/5.5 installation
  + A Working IIS + SSL maximum patchlevel with OWA correctly installed on
the same Exchange machine
  + A working ApacheII with SSL and mod_proxy support on another Machine


3. Configuration

Ok, let's go.

The configuration to make all these work is quite simple, but include a
work-around. OWA infact return FQDN urls to the client; so we must make that
the client always think to connect to the apache, and the Apache always
think to connect to the IIS server for the same domain name! Better
explanation will be parsing configuration files :-)

For security reasons we'll configure all using SSL connections, so there
will be a Secure Connection between Client and Apache, and between Apache
and IIS, so no data go on the net unencrypted.
This is important thing because as Microsoft says in Q29661 Article, only
Basic Authentication is possible between front-end back-end, also if
front-end is IIS and not Apache. By the way... using Integrated Windows
Authentication with ourconfiguration will make IE not work :-)

We can configure our wonderful apache server machine. I suggest to use the
httpd' latest version.
Naturally we assume that the reader has any experiences with Virtual Hosts,
normal and SSL Based, for further information please read Apache
documentation.

For firts we assume that the scenario is you have a public or private
domain, (Ex. owa.myexistentdomain.com) so in your DNS you must translate
this domain to the Apache IP Address (could be public or private) .



After that you MUST put into the /etc/hosts file of the apache machine this
string:

owa.myexistentdomain.com 192.168.0.1 # substitute this ip with the IIS-OWA
internal IP address.

we make this action to make possible the apache to understand and correctly
proxy the connection because OWA sends him the FQDN as the URL to contact!!!


So in your ssl.conf:



<VirtualHost privateip:443> #substitute this IP with the address resolved by
the dns for owa.myexistentdomain.com!!!

    SSLEngine on
    SSLProxyEngine on
    SSLProtocol +all
    SSLCipherSuite HIGH:MEDIUM

    SSLCertificateFile /apache/conf/ssl.crt/server.crt
    SSLCertificateKeyFile /apache/conf/ssl.key/server.key

   <Files ~ "\.(cgi|shtml|phtml|php3?)$">
    SSLOptions +StdEnvVars
   </Files>


    ServerAdmin root@xxxxxxxxxxxxxxxxxxxxxxxx
    ServerName owa.myexistentdomain.com:443

    <Location "/exchange">

    ProxyPass https://owa.myexistentdomain.com/exchange
    ProxyPassReverse https://owa.myexistentdomain.com/exchange
    </Location>

    <Location "/exchweb">
    ProxyPass https://owa.myexistentdomain.com/exchweb
    ProxyPassReverse https://owa.myexistentdomain.com/exchweb
    </Location>

    <Location "/public">
    ProxyPass  https://owa.myexistentdomain.com/public
    ProxyPassReverse https://owa.myexistentdomain.com/public
    </Location>
#
    ErrorLog logs/owa_ssl_error
    CustomLog logs/owa_ssl_acces common
    CustomLog logs/ssl_owa_request_log \
          "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"

    # mod_security Configuration

    SecFilterEngine On
#    SecAuditEngine On
#    SecAuditLog logs/audit_log
#    SecFilterScanPOST On
    SecFilterDefaultAction deny,log,status:409
      # Filters
      SecFilter "\.\./"
      SecFilter "<( |\n)*script"
      SecFilter "<(.|\n)+>"
      SecFilter "root.exe*"
      SecFilter "cmd.exe*"
      SecFilter "default.ida*"
      SecFilter "delete( |\n)+from"
      SecFilter "insert( |\n)+into"
      SecFilter "select( |\n)+from"


</VirtualHost>


Now, we can make a simple html or php page to put in htdocs/ that redirect
every single connection from the original site to the https:// one, a simple
php example here:

<?
header("location: https://owa.myexistentdomain.com/";);
?>



Now, after that we MUST correctly configure IIS to make he can response to a
connection made from the client from a different Domain Name.

So, take IIS Admin interface and put into the Virtual Domain in witch OWA
lives and into the:

Properties -> Web Site -> IP Address -> Advanced

Add the identity to the web server:

IP Address:       Put here the local ip address of the Exchange-IIS machine
TCP Port:         80 of course
Host Header Name: Here you must put owa.myexistentdomain.com

click OK and save :-)

Naturally you must the identity also of the SSL identity in witch the port
is 443 and the ip is the same of the previus configuration (norma identity).

Click OK and save :-)

Now, into the menu':

Properties -> Web Site -> IP Address:

put the IP address of the IIS-Exchange machine.


now, a VERY important thing are:

+ tell IIS to refuse any NON-SSL Connection (search into "Directory
Security" and Edit certificate properties)
+ Disable Integrated Windows Authentication and Enable Basic one (search
into "Directory Security").


Now we suggest to:

+ use IISLockdown utility to hardenize IIS configuration (is free avaiable
on microsoft site)
+ Use Apache mod_protection or mod_security to avoid attack (search
freshmeat for them)


Now all is working!!! Point our browser to
http://owa.myexistentdomain.com/exchange/ or
https://owa.myexistentdomain.com/exchange/ and go on!!!!


4. TroubleShooting.


For first thing I suggest to try different browsers instead of IE that is
buggy.
Doing this configuration I find out that forcing SSLv3 with HIGH encryption,
Netscape works but IE will NOT WORK saying the stupid error "Navigation
Cancelled" :-D (thank you Mr. Bill... you make me happy).


After that try this:

+ Try to connect directly to IIS to ensure that is not an IIS or OWA problem
+ Pinging from a client owa.myexistentdomain.com I reach the apache IP
Address.
+ Pinging from The apache Server owa.myexistentdomain.com I reach the
Exchange-IIS IP Address.
+ Both Apache and IIS Certificates are valid and built on the
owa.myexistentdomain.com Common Name
+ Try to disable NTLM Auth, sometimes IE is more stupid that he would
appear.
+ Recontrol Apache and IIS Configuration

+ Try to sniff the traffic to manage what it is going on!!!!



Best Regards,


Federico ego_pfe@xxxxxxxxx

Credits: I must say thank to buzzzo, without him my lamerness would take
windward ;-)

[Slack] - Libnet per dsniff-2.3

Problema:

La versione di Libnet per dsniff 2.3 che sono riuscito a installare (e che permette il funzionamento di dsniff) è:
Libnet-1.0.2a

Dopo aver dato ./configure
make

ottengo il seguente errore:

In file included from src/libnet_resolve.c:36:
include/libnet.h:87:8: missing terminating " character
include/libnet.h:89:50: missing terminating " character
make: *** [src/libnet_resolve.o] Error 1

Questo errore è dovuto dal fatto che c'è un errore nel file include/libnet.h

Soluzione:

Editare il file include/libnet.h
e sostituire le righe:

#error "byte order has not been specified, you'll
need to #define either LIBNET_LIL_ENDIAN or LIBNET_BIG_ENDIAN.  See the
documentation regarding the libnet-config script."

con

#error "byte order has not been specified, you'll need to #define either LIBNET_LIL_ENDIAN or LIBNET_BIG_ENDIAN.  See the documentation regarding the libnet-config script."

in pratica si deve mettere tutta la stringa su una stessa riga.

Adesso salvare, uscire e ricominciare con ./configure && make && make install

[Slack] - Installazione dsniff

Problema:

/record.c: In function `record_save':
  ./record.c:130: `R_NOOVERWRITE' undeclared (first use in this function)
  ./record.c:130: (Each undeclared identifier is reported only once
  ./record.c:130: for each function it appears in.)
  ./record.c:130: warning: passing arg 2 of pointer to function from
  incompatible pointer type
  ./record.c:130: too few arguments to function
  ./record.c: In function `record_dump':
  ./record.c:143: structure has no member named `seq'
  ./record.c:143: `R_NEXT' undeclared (first use in this function)
  ./record.c: In function `record_init':
  ./record.c:167: warning: assignment makes pointer from integer without a cast
  ./record.c: In function `record_close':
  ./record.c:206: too few arguments to function
  make: *** [record.o] Error 1

Soluzione:

This little fix will allow dsniff to install on any slackware box...

Change directory to /usr/include

Create a symbolic link with:
ln -s db3/db_185.h db_185.h

Then do a ./configure, make, make install.

Ricompilato e aggiornato apache modssl php

cd mod_ssl-2.8.28-1.3.37

./configure --with-apache=../../apache_1.3.37 --with-ssl=/usr/local/ssl --enable-shared=ssl --with-mm=/usr/local

cd ../../apache_1.3.37

EAPI_MM="/usr/local" SSL_BASE="/usr/local/ssl" ./configure --enable-module=so --enable-shared=ssl --enable-module=ssl --enable-module=rewrite

make && make install

cd ../php/php-4.4.4

./configure --with-mysql=/usr/local/mysql --with-openssl=/usr/local/ssl --with-apxs=/usr/local/apache/bin/apxs --enable-mbstring --with-mm=/usr/local --with-zlib --with-gd

make && make install

aggiunto a httpd.conf

...
AddModule mod_rewrite.c
...