This is a bugfix release. The following has changed since 0.1:

• Display wgTitle instead of wgPage to avoid url encoded titles
• Fix issue where wgJSBreadCrumbsMaxCrumbs + 1 number of bread crumbs were shown instead wgJSBreadCrumbsMaxCrumbs
• Strip empty title and url when it exists
• Change the output of the leading description to look like “Leading description:” instead of “Leading description ” + wgJSBreadCrumbsSeparator, to make it more clear that it isn’t part of the history.
• Change the character used to split and join in cookies to ‘|’ since it is illegal in urls and page titles, and therefore is guaranteed to work, unlike using the user overridable separator

JSBreadCrumbs is a simple extension that adds a jQuery based Javascript file and a CSS file to your wiki’s output that will add a trail of navigation breadcrumbs below the navigation tabs. The idea is for a simpler history than your back button that only tracks navigation inside of the wiki. Unlike the browser’s back button, it will only track GET requests, not POSTs, will only show history for your wikis, and will remove duplicate entries from the list.

This is a bugfix release related to the previous 1.2b release. The following has changed:

• Fixed issue with single domains, and non-auto-authentication domains being non-operational due to security fix in 1.2b
• Fixed another issue with mail me a password not working properly

To download this version, please use the extension distributor (http://www.mediawiki.org/wiki/Special:ExtensionDistributor/LdapAuthentication), select “Development version (trunk)”, and click “Continue”.

This release contains a security bugfix for users of register_globals. Most configuration options in the extension did not have default values; this release sets defaults for all configuration globals. Users are recommended to update to this version, or disable register_globals. If you do not have register_globals enabled, you are not affected.

The following has changed since 1.2a:

• Fixed issue with group synchronization and nested groups
• Added support for exclusion groups in addition to required groups
  • Configured via $wgLDAPExcludedGroups; syntax the same as $wgLDAPRequiredGroups
• Fixed check for returns with no entries
• Added memberOf support

XDMCP is insecure when used directly, as it is unencrypted, and will send your credentials and all keystrokes and mouse actions  over the network in clear text. By default XDMCP is disabled on most recent distros. Thankfully there isn’t any reason to use it!

Instead of using XDMCP, you can use X11 forwarding to run your graphical environments across SSH. Doing so also allows you to log in via smart cards, if your version of SSH has PKCS11 support.

If for some reason you have Windows running as part of a cluster, like as a node in a Selenium Grid, it is nice to be able to monitor it. A frequently used monitoring suite for clusters is Ganglia. Ganglia, unfortunately, doesn’t have a native Windows binary. Thankfully, it can be compiled and installed in Cygwin. The instructions for doing so are included in the Ganglia tarball (in README.WIN). Instructions that aren’t included are how to run gmond as a Windows service.

After installing Ganglia, you can add gmond as a Windows service by doing the following:

At some point recently the SSH shipped with Cygwin added PKCS11 support. This support allows you to add a smart card library to use your smart card’s certificates as ssh keys. This article will describe how to use ActivClient or Coolkey to access your card, how to export the card’s public certificates (as rsa public keys), and how to use ssh/ssh-agent options to properly use the smart card.

Prerequisites

I’ve tested with the below software and versions. Other versions may work, but haven’t been tested.

• ActivClient 6.2+ or Coolkey
• Cygwin 1.7+
  • OpenSSH_5.5p1+
  • OpenSSL 0.9.8n+