On Fri, Oct 4, 2024 at 5:38 AM Vincent Sherwood <vince...@itsolutions.ie.invalid> wrote:
> Hi Michael, > > Firstly, thank you to the team for a great product. > > I loaded this staging/1.6.0 build up on one of our servers to test it out. > > For building the server, the instructions assume more knowledge than I and > probably many others have. Perhaps it is an oversight in preparing the > Staging branch? > > The README says load prerequisites then run ./configure > > However, there is no ./configure ! > > I did a web search and found these instructions - Can you please confirm > if they are correct for Guacamole, or if they need changing. > > libtoolize --force > aclocal > autoheader > automake --force-missing --add-missing > autoconf > ./configure > > You shouldn't have to do all of those steps - it should be: autoreconf -fi ./configure The "autoreconf -fi" call should build the configure script for you. > Perhaps the correct set of steps can be added to the Staging README file. > Or, the appropriate steps can be taken to produce the ./configure file and > the resultant files added to the Staging branch. > > Note: This has never been an issue with server release downloads as they > have always had a ./configure already present in the directory > > Yeah, this is specific to building out of the Git repo, as the configure script does not exist, there. > As regards testing. > > Thus far, I have been testing using the 1.5.5 extensions - auth-totp, > auth-ldap, auth-json and auth-jdbc-mysql > > All looks good so far. I have tested both RDP to Windows 2016 servers and > VNC to linux servers. Our setup uses AD and TOTP (Google Authenticator) for > sign-on to Guacamole. Guacamole connections have a mix of pre-configured > authentication and prompting for credentials. I will continue to use this > version and will report back if I encounter any issues. > > One note - On an RDP connection that had only the DOMAIN pre-configured > and NLA security set, and prompted for the userid/password - when I swapped > in the Guacamole 1.6 WAR file, this connection would not work. It would > attempt to connect and then would just hang on a blank screen. It never > prompted for the userid/password. There were no errors in the guacd log > entries in the /var/log/messages file. Doing a hard refresh in the browser > (Ctrl-F5) and re-logging into Guacamole resolved this issue. I recall > reading user messages from someone who was seeing similar RDP anomolies > recently after upgrading to 1.5.5 - if you still have access to the thread > perhaps suggest the user tries a browser hard refresh. > > Yeah, when changes are made to the HTML, JavaScript, and style sheets, the browser caches tend to need to be cleared. As long as it is working after you clear the cache you should be okay. -NIck >
