I can't seem to reproduce your "save as" problem with running Chrome Version 80.0.3987.87 (Official Build) (64-bit) on Windows 10. FormIt "MenuSave Sketch asLocally" opens a dialogue box allowing me to give the sketch a new name, sets that new name as the active sketch and downloads the file to the download directory Chrome points to (ie the default C:\users\myuser.name\downloads).
I am a recitation instructor for MIT's 6.033 course this semester, which basically involves discussing "notable" computer science papers with approximately 50 students every week. This week we discussed buffer overflows. To refresh my memory, I dug up my previous work with a buffer exploit challenge, simplifying it and revisiting it for modern Linux. Here is a brief introduction to how to exploit a buffer overflow on a Linux system. This works on both 32-bit and 64-bit systems, although 64-bit systems may need an offset to be manually updated.
The latest version of FormIt Converter For Revit can be downloaded for PCs running Windows 10/11/Vista/7/8, 64-bit. The program belongs to Photo & Graphics Tools. This program was originally produced by Autodesk. The current setup file available for download occupies 642.4 MB on disk. The following versions: 16.1 and 1.9 are the most frequently downloaded ones by the program users.
Downloading of this software may constitute an export of cryptographic software from the United States of America that is subject to the United States Export Administration Regulations (EAR), 15 CFR 730-774. Additional laws or regulations may apply. It is the responsibility of the person or entity contemplating export to comply with all applicable export laws and regulations, including obtaining any required license from the U.S. government.
The emulator package for Ubuntu is fairly old at this point, but it should still work. The major challenge when using it on newer versions of Linux is that most distributions are now primarily 64-bit, as the emulator and its supporting utilities are 32-bit. I set up a VM using Ubuntu 21.10 and determined that the following should work in a clean environment:
64-bit PuTTY before version 0.71 incorrectly tries to load 32-bit version of MIT Kerberos DLL. This obviously fails and PuTTY falls back to Microsoft SSPI (which is probably not set up on your system, so it fails too). This was fixed in PuTTY 0.71.
So either upgrade to PuTTY 0.71. Or if you you are stuck with an older PuTTY version, you have to manually specify a path to 64-bit DLL in "User-supplied GSSAPI library path" box at "Connection > SSH > Auth > GSSAPI"
Problem seems to be solved after looking at the bitness of all of the software. I was running 64-bit PuTTY, but it was trying to look for the 32-bit Kerberos file. I directed it to the 64-bit Kerberos file, and I was able to connect to the server. Thank you to Martin and grawity!
aa06259810