.rbs files
-
I do some consultancy work for a company that uses SU in all their branches.
A couple of years ago they had an employee (who is no longer with them) who created some plugins for them.
They now want to modify the plugins, but the employee is no longer with them. Although I am no script writer they have asked me to look at the scripts to see if I can modify them - they have no one in the company that knows about plugins, and they tell me that the plugins have company sensitive content so they are reluctant to pass them on to anyone else.The first hurdle I have is that they are in .rbs format and appear to be encrypted, and from some research I see that there is a SU 'Scrambler' which encrypts plugins.
Does anyone know if it is possible to decrypt these files to be able to read them?
-
The .rbs format is compiled into a encrypted format.
It is not possible to decrypt it - I don't think even Google could do it
There must be [or must have been] some equivalent .rb file[s] that were used to make the .rbs format file[s].
These files can be edited and reused directly, or recompiled as new .rbs files.
If there are not existing .rb files then they are screwed
Presumably they were the organization's property ?
A .rb file is easily read [it's actually no more than a suitably set out plain-text file] and then edited if you know a little coding and the changes are simple - e.g. like changing text in a dialog, otherwise someone with more skill is needed to change algorithms, methods etc.
Note that a few .rb files are 'packed' to encrypt them from casual pilfering and therefore also impossible to read... BUT unlike a .rbs file someone with sufficient knowledge can 'unpack' the contents back to a readable text format and make changes...
If they have any .rb format files at all they perhaps need to make discreet contact with a scripter - like myself - who will give confidential advice about how they might be adjusted etc
-
@unknownuser said:
If there are not existing .rb files
They don't have any
@unknownuser said:
then they are screwed
From what you say - it looks like it.
I have sent you a PM.
-
This is a interesting situation. While it seems clear that the company owns the software, can they make a claim for the source code? My guess is yes, but they have to find the fellow (assuming he kept a copy). He probably scrambled the program because of the "sensitive data".
Depending on the extent of the modification required, if very minor, then perhaps a programmer at the level of assembly language might be able to make small changes with debug. I have done it with .com, and .exe files, but don't know about code at the current "state of the art".
Advertisement