The release below is from prior to Guacamole's acceptance into the Apache Incubator. It is not an Apache Software Foundation release, and is licensed under the MIT license. The latest release of Apache Guacamole is 1.5.5.
The 0.9.3 release of Guacamole features greatly improved keyboard support, the ability to configure guacd with a configuration file, as well as support for authentication via HTTP Basic. Support for all standard control code shortcuts (C0 control codes) within SSH and telnet has also been added. Previous versions of Guacamole only supported Ctrl+A through Ctrl+Z, making other combinations like Ctrl+^ impossible.
guacd can now be configured with an INI-style configuration file called guacd.conf. This file is optional, but makes configuring guacd easier when you need custom startup options like SSL encryption or a non-standard port. Past versions of Guacamole required that such options be specified on the command-line.
If you use an external service like Apache to provide authentication prior to granting access to the Guacamole login page, you can now pass the username/password from that service through to Guacamole, authenticating with those credentials as if entered on Guacamole’s login page manually.
This requires that the external service use HTTP Basic authentication, but as long as the HTTP “Authorization” header makes its way to Guacamole, it will attempt to authenticate using that first, prior to resorting to the login page.
After much debugging, the base of Guacamole’s keyboard support has been rewritten to properly handle non-US keyboards. See the links below for a full description of these improvements, but in general, what was broken before is broken no longer. If you were having issues typing with past Guacamole releases, please give 0.9.3 a try and see if things are now resolved.
Past releases of Guacamole supported Ctrl+A through Ctrl+Z for SSH and telnet, but there are several other standard key combinations which produce control codes from the C0 block. Guacamole 0.9.3 adds support for the remaining codes.
This is particularly important if you use Guacamole to connect to a device that uses these codes to implement “break”, as some Cisco devices do.
Recent versions of Chrome have removed a deprecated sound API that lingered within Guacamole, thus breaking sound. Release 0.9.3 migrates to the newer version of this API, thus restoring sound. If Guacamole is used on a browser that only supports the older API, it will still work.
If you embed Guacamole within your own web application, and wish to restrict which Guacamole instructions are sent or received over each connection, support for such filtering is now provided within guacamole-common. You can modify, drop, allow, or deny any instruction read/written over an active Guacamole connection.