I'm prototyping using Apache Guacamole for brokering RDP connections.
The tech stack works really well, however, I'm hitting a usability issue in regaurds to running a Mac and trying to send hot keys like Control+C/Command+C and them not working.
Per Guac's docs, this seems to be inline with what they expect, as they don't do any "curtesy" remapping that other RDP managers on Mac (Microsoft Remote Desktop, RDS HTML5 Client, etc) do.
My question is has anyone found a customization or workaround to allow Mac->Win keymapping through Guacemole HTMl5 interface?
I'm not sure its a none starter, but it is extremly difficult to use windows with nearly no keyboard shortcuts :).
Thanks!
On my mac I use BetterTouchTool to get around this issue. It's not great though because your guacamole will still register the original keypresses from time to time. I have been looking for a workaround as well and have thus far not been able to find one :/.
I was wondering if there's a way to use Mosh on windows without Cygwin?
I need to be able to put it on my USB drive and copy it over to a windows computer and be able to Mosh into one of my servers. Otherwise, is there a way to use Cygwin and have it portable? I did get mosh working under windows via Cygwin, but that meant I had to add an environment path to the windows computer, which, on the windows computer that I'm working on doesn't allow you to change that, since I don't have admin privileges.
MobaXTerm is portable and supports Mosh.
It works quite well. I spent all day using it on a very dodgy connection and it worked like a charm.
Just get the most recent version and from the Session menu select Mosh. It did does not support IPv6 (at least in Version 9.2 (2016-09-18)):
Bugfix: Mosh sessions are forced to IPv4 only (IPv6 is not yet supported by Mosh client/server)
But it might work now, since Version 10.4 (untested):
We also improved MobaXterm behavior and fixed issues with multi-monitors, IPv6 connections, mouse scrolling and keyboard shortcuts.
Interestingly enough, I wanted MOSH for Windows too, and I find Cygwin to be very messy. Instead, I just downloaded a minimal Text-only Debian distribution, booted it up in VirtualBox, and installed MOSH. Surprisingly, it's much less time consuming and requires less tweaking than going the Cygwin route, and makes less modifications to the host machine.
In fact, there is a portable VirtualBox, so you can put your MOSH VM and Portable VirtualBox on a memory stick.
I haven't even tried to optimize things, but it runs just fine on the 256MB of ram I gave it. It would probably run just fine on 64MB or less.
I do hope MOSH will be built into PuTTY/KiTTY in the future.
I have noticed that a new version of MobaXterm has been released (version 7.1) and includes an intergrated Mosh session.
So, you dot not need anymore need plugin for that.
They said that it is "experimental", but I have tested it, and it is working quite well.
As of now, Mosh has added support for Google Chrome (or any of Chromium Browsers) as an official extension. So you can keep a portable google chrome & use mosh from there.
For Windows, there isn't a single solution install to support MOSH. Rather, you have to sort of "stitch together" a few options to make it work.
MOSH itself does not need ssh or any other initial program necessarily. It is possible to start a session on your server, then using the published connection information, go to your client (in this case your windows box) and use that information to connect the session. This is sort of messy and is the main reason people use SSH to basically establish a connection to the server, remotely start a MOSH server, get the session information back to your client machine, then launch the MOSH experience.
The two pieces you need on the client side (if you make the connection manually) are the server port number and symmetric encryption key. A typical example of one given by a MOSH server would be:
MOSH CONNECT 60001 U0MWPbwn3BdcdMyNLnSFCA
Where 60001 is my port number and "U0...CA" is my encryption key. Don't ever give this out BTW as ANYONE can connect to your running MOSH server with this information (that is, they would look just like an IP change just like you do when you get disconnected and reconnected)
So, back to installation. MobaXterm (currently at v10.5) is a free for personal use app that you can find at https://mobaxterm.mobatek.net/. Installation is relatively straight forward. One word of caution however, their SSH implementation is rudimentary. Basically they support password authentication for ssh. If you use public keys, you cannot have one with a password on it and expect it to work (the code to ask you for your password appears to be missing). This might not be a show stopper for everyone but this is where my company stopped following this thread.
Within MobiXTerm, you want to hit the "Sessions" button at the top left to bring up a new session window. Press the Mosh button on the top right to get the start of your session (NOTE: This is IPv4 only. Zippo luck on getting IPv6 with this to work). Enter your remote host and the username of the ssh account you will be using. If you have an unsigned ssh key, then you can use the Advanced Mosh setting to link that private key with this session (at this point, as a security guy, I'm sort of passing out). At this point, as long as mosh is correctly running on your server (with the 60000-61000 UDP ports open in the server firewall), things should "just work".
Ok, so its not too painful to get working this way. But other than terminal functionality, its not very much fun either. Although MobiXterm is an X-server, I haven't yet gotten X to function over the mobi connection (at least not automatically).
I am trying to use the HP Fortify Static Code Analyzer to analyze security concerns in a large C application and I have run into various bugs in the software itself that I cannot seem to find any answers to anywhere on the Internet. I am using version 3.4 of the software and running it on a Linux x64 system.
The main bug that I am encountering that makes it very difficult to use this product at all is that in various different places in their Audit Workbench GUI the program will just close for no reason. An example is whenever a pop-up window shows asking you a question and your answer to the question is just to close the pop-up window by either clicking on the close button or the cancel button, the whole program ends instead of returning you back to where you were when you originally got the pop-up. Another example is when I try to open the Rules Editor, either for a new Rule Pack or an existing Rule Pack, the program opens up a progress window with a moving progress bar that sits there and moves for a while but when it is finished, instead of opening up the Rules Editor, the whole program just ends suddenly.
Has anyone out there seen behavior like this? If so, please let me know what I can do about it. Thank you.
I would highly recommend upgrading to the latest (4.10 at the time of this post) version. One thing you can do to help diagnose issues is to look at the log files. These are located in (by default) [user.home]/fortify/AWB-3.40/log.
Also, since you are using Linux 64bit, you will want to ensure that AWB isn't trying to access the 32bit JRE at any time. This can be accomplished by removing [fortify install root]/jre and renaming [fortify install root]/jre64 to [fortify install root]/jre. Some of the tools default to /jre and so you can run into issues on Linux 64bit.
I need to have multiple versions of IE browser in my windows 7 for cross browser testing.
I checked for Standalone application, but nothing worked properly.
I know there is a F12 developer tool in windows which will switch the user agent, is it possible to call the iexplore.exe browser from command line along with the required browser version?
I have already got the trial version of spoon, but I am looking for a free solution.
I am not looking for any paid version of alternatives
I dont need procedures that involve creation of virtual machine as they will not work for me.
Kindly let me know if the above information is not clear or insufficient.
It's not possible to change the browser version from the command line.
The closest you can do and it's not at all recommend as it impacts every IE instance is to use the Browser Emulation feature control key (documentation) to change the default mode.
When I am making changes on my localhost, it is not working. I am on windows 7 but when I copy the file in which the changes were made, and try to execute them in Windows XP, its working. I as I asked someone who has a lot of knowledge on this and they said it is a configuration issue.
Someone else told me it was because of output caching, so I disabled everything and tried, even then there was no response. Can anyone tell me how do I go about it?
This was because of caching issue.
Navigate to Control Panel\All Control Panel Items\Administrative Tools\IIS Configuration Manager, select Output caching, then add new rule with follow parameters:
Insert types of files, you are changing(.aspx,.php) in File name extension field and simply unselect all types of caching. Then restart server and it should work now
I could hardly understand your word, so I think your very first task is to make sure you understand IIS and how to start troubleshooting.
Without a clearer description on the problem, nobody can provide you useful information on how to resolve it.
If you like, open a support case with Microsoft support team and talk to the support engineer about your issue.
http://support.microsoft.com