PuTTY ssh authentication agent

Spread the love

Unfortunately, this protocol was not fully implemented on OpenEdge ABL. On the one hand, before transferring or receiving files, they had to be converted to various encodings. We tried to implement ABL file conversion, but it worked out very slowly. And the transfer of data from ABL also turned out to be slow. And this speed did not suit us. On the other hand, forcing ABL to simply display a single character, such as a space or ESC, caused a lot of inconvenience. As a result, we have a small set of C-programs, which were called from ABL putty quick connect.

This bundle has worked on both the 32-bit Linux platform and the 64-bit Linux and Sparc Solaris brothers. Since the programs did not use any special functions and consisted of 30-40 lines of code, it was not a problem to collect them under other environments. In one of the tests, the system was run on AIX. And even did not have to rewrite.

The simplest command — launching an application on a workstation — was generally made with a sh script:

#! / bin / sh

echo “\ 033% w $ 1 \ 033 \ c”

Thus, only three functions are explicitly covered. But what about the rest?

And everything is done like this:

Get the contents of the folder – you need to run the command DIR DISK: \ PATH \ *> FILE.TMP, then pick up the file, and then run the command to delete the file.

Send the file to print to the matrix printer – put the file on the workstation, start copying to the desired device (PRN, LPT1, …), delete the file.

Send a file to a laser printer – put on the workstation a file with text and a file with fonts for the printer. Run the command to copy the font to the printer port, after the command to copy the text file to the printer port. Next, delete the files.

Read and write to the Registry, get lists of printers, network interfaces, the name of the workstation – there is a great program REG.EXE. With it, you can both extract the necessary data from the Registry, and put it back.