Re: certificates naming conventions

to troubleshoot.

o Requested a login via SecureID and Salomon's netblazer, supporting
28.8 PPP (TCP/IP for windowing connectivity) for the vendor. Let
them transfer in any tools they need to troubleshoot.
Short-term access.

o If it is truly necessary to transfer a large amount of code, such as
Informix working to convert a large Sybase app, then take the time
to write a shell script that (using say 'sed') scrambles the names
of environment variables, and be sure to hand-ruin any proprietary
algorithms.

Why is transfer of Salomon proprietary source to a vendor's site the last
step to try? Because Salomon loses control over the code. In the Informix
/Sybase case, the vendor Informix requested (and received) another copy
of the code "because I lost the previous copy".

Two emails between the pair are enclosed.

[snip]

*********************************
:Size: 846077, Dated: Jul 3 17:52
:Sender: sara@sbixxx [sara xxxxxxxxxx XXX-NJ]
:Recipient: xxxxxxx@xxxxxxxxxxxxx [Dennis xxxxxxx]
:Subject: Re: (Fwd) Re: (Fwd) rw...
**** UUencoding, Filename='rw4.tar.Z'

Hi Dennis,

The last patch didn't help, here's some other code that will also
trigger the bug.

This code doesn't compile for other reasons but we need to get the
Rougeview issue resolved.

Could you ask xxxx to look this over?

Thanks,

sara

:begin 600 rw4.tar.Z
*********************************

# of
lines filename
----- --------
54 4x.env
139 LocalRules
344 LoginDlg.cc
65 LoginDlg.h
221 MacroRules
87 Makefile
619 OASYSMain.cc
175 OASYSMain.h
79 SubApp.cc
51 SubApp.h
54 gui_main.cc
33 gui_main.h
42 lib_inc
647 sbOfLogin.cc
113 sbOfLogin.h
0 sun4_4
22 version.txt



.

Relevant Pages
Quantcast