Urs Meli

Today I was struggling with LDAP.

The Domino Server has directory assistance over 2 address books activated.

Problem: Got LDAP error 50 - authentication error and only the users from the second adressbook were visible.

Always got the same problem, even with administrator credentials.

After checking the default domain config document, both addressbook's ACL's, directory assistance and searching the internet I found an interesting ini setting:
On the server console: set config ldapdebug=7
turns ldap debugging on.
Connecting with the LDAP administrator user I saw a strange message like "User CN=XYZ has no read access to names.nsf" on the console.
But the user was in the ACL (Manager) and could open the names.nsf in the notes client.

Comparing the 2 adressbooks I discovered that in names.nsf the "maximum internet name and password" was set to "No Access".
After changeing it to reader, everything worked!

I always thought that this "Maximum Internet name and password" setting was for http access only.





 

Since yesterday my laptop is totally secure :-)

Even I'm not able to login anymore.....

What happend: I caught the zlob trojan, which is a bad thing. First I thought I could remove it using tools like knoppicillin or some other external virus scanners and bootdisks. But suddenly I realized, my harddisk has been encrypted 3 months ago....gosh...

Next thing I tried, booting windows in safe-mode, removing the virus with some tools and several av-engines. When I tried to switch back to normal windows the sequence started: starting up windows..... shutting windows down..... Halt.....panic!

After a hard reboot the encryption program blocked my whole machine. My harddisk is still encrypted and unaccessible therefor now I have a very secure system...

Our helpdesk has to pull the harddisk out, access it from a different System and get the data of my drive....

What about a backup? Sure. Its 3 months old......

As a developer your sourcecode is in a svn repository or not? nope, svn repository crashed 6 months ago. just before lotusphere we got our hardware back. svn restoreing was planned for this week...... crap.....