WRT "Money would be the first issue of course
since no one who does such work normally does it
gratis, but among those who are real fans of the
software I am sure some way could be found to
fund such an effort, via crowd site or more private means."
If such an effort were to be mounted in any
realistic way, I for one would be willing to contribute.
Dave Cole
At 11/4/2022 03:12 PM, Farley, Peter wrote:
I agree with Jay that it still may be possible
to recover the source IF the files still exist.
I know it probably is possible to set up PW
protected or encrypted files to "self-destruct"
or somehow lock permanently (I assume any agency
or company who are serious about secrecy all
have access to some capability like that), but
is such a seriously advanced capability really
available to "ordinary" folk like the SPF developer?
Even assuming the answer to that question is
"yes", it would be worth asking if a certified
"white hat" hacker or company had the capability
to unlock such files anyway. Obviously it
depends entirely on what the "locking" mechanism
really was and how permanent the "self-destruct"
status is, but I tend to think that someone with
the necessary credentials could possibly resolve
this unfortunate situation. Money would be the
first issue of course since no one who does such
work normally does it gratis, but among those
who are real fans of the software I am sure some
way could be found to fund such an effort, via
crowd site or more private means.
Any such effort would require his widow's
cooperation and official written approval of
course, but it sounds to me like that would not be an issue.
Another question to ask is if any version of the
source was escrowed with a law firm or other
"rights protecting" organization in order to
make a sale to a large company? Many software
developers and companies have had to do that to
protect the rights of large user
organizations. Such a situation might provide
(with cooperation from the beneficiary(ies) of
the escrow) access to some version of the
original code, though getting it released in the
open might take lawyers and/or court actions.
Just a couple of thoughts for consideration.
Peter
-----Original Message-----
From: IBM Mainframe Discussion List
<[email protected]> On Behalf Of Michael Knigge
Sent: Tuesday, November 1, 2022 5:59 PM
To: [email protected]
Subject: AW: SPF/SE is available for free
Jay,
I've got the following information.....
<quote>
Hello Michael. I contacted his wife and she
told me that Timâs SPF s/w is âgone
foreverâ. Apparently he PW protected it and
when she tried to break the PW, it self
destructed. In any case, according to her,
there is no hope for any data recovery. Very disappointing.
</quote>
Sorry....
Michael
Mit freundlichen GrüÃen
Michael Knigge
Software Engineer
<Snipped>
-----Ursprüngliche Nachricht-----
Von: IBM Mainframe Discussion List
<[email protected]> Im Auftrag von Jay Maynard
Gesendet: Dienstag, 1. November 2022 20:23
An: [email protected]
Betreff: Re: SPF/SE is available for free
Hm. According to the README on the Github
site, the source code was stored
encrypted...are the encrypted files still in
existence? Perhaps they can be obtained and
decrypted. It's a long shot, to be sure, but definitely worth a try.
On Tue, Nov 1, 2022 at 9:22 AM Michael Knigge <[email protected]> wrote:
> FYI:
>
> I guess some of you guys use SPF/SE (SPF SourceEdit) from Command
> Technology. The editor was developed by Tim Tetivia, who unfortunately
> died in 2022 as a result of a corona infection. With some research and
> help from other SPF users (namely Peter aka Verizon), it was possible
> to contact Tim's wife Bonnie. She gave us permission to distribute the
> editor for free (sadly the source code is âlostâ forever).
<Snipped>
--
This message and any attachments are intended
only for the use of the addressee and may
contain information that is privileged and
confidential. If the reader of the message is
not the intended recipient or an authorized
representative of the intended recipient, you
are hereby notified that any dissemination of
this communication is strictly prohibited. If
you have received this communication in error,
please notify us immediately by e-mail and
delete the message and any attachments from your system.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
