It seems there is an issue where compiled scripts are stored, not as individual
assets, but as part of SOG/SOP.
That should never have happened, but it has.
For the moment, TrustBinaries=false is your solution, but watch for changes!
- Melanie
On Sat, 16 Oct 2021 00:19:09
Hello,
I have checked and found that our simulators were set with TrustBinaries =
true
I have reverted that setting in a simulator that displayed an exception
about method not found when loading and now it has loaded WITHOUT any
exception.
As we suffer similar problems in other locations, I
I have checked the code, extensively. I did find an exploit where a carefully
crafted yobj file could be instrumented to create a DOS attack or a nuisance
attack and I'm looking into how to fix that issue.
However, I also did check the YEngine code, and compiled scripts are most
certainly
Did TrustBinaries = false fixed the issue?
As you did observe, TrustBinaries is not only a major security problem,
it also forces the use of binary code wrongly stored on the asset at grid.
so the only fix with TrustBinaries = true, is manual inworld recompile.
0008026: "Runtime Error in
Hi Melanie, Happy to see you :)
On Thu, Oct 14, 2021 at 11:00 AM Melanie wrote:
> If your grid is a walled garden without HG, you can set TrustBinaries on
> even when using XEngine. TrustBinaries accelerates TP and region crossings
> in walled gardens, the option was created for Avination.
>
>
If your grid is a walled garden without HG, you can set TrustBinaries on even
when using XEngine. TrustBinaries accelerates TP and region crossings in walled
gardens, the option was created for Avination.
Now, with YEngine, all grids could have it on if no XEngine is used.
- Melanie
Hello,
I don't mind setting TrustBinaries = false as our grid is a "walled garden"
so there will not be cases of untrusted binaries entering our system.
I still don't understand how could new compiled code generate this error.
I'm starting to think that there is something in the old LSL code
TrustBinaries is safe in regions using only YEngine. That is because the
compiled YEngine scripts are not actually binaries, they are not DLLs. They are
just a preparsed AST to save the compiler some work, but that AST is used to
generate the binary code on the receiving side.
With XEngine,
Make sure you have TrustBinaries = false in opensim.ini
That should never be true except on a few use cases.
Ubit
On 13-Oct-21 15:56, Asaff Belfer wrote:
But this is just it.
The simulators were not upgraded. They were re-installed in a different
folder so it's a completely new installation.
As I replied before, the simulators were installed in a different folder so
it's actually a new installation. There is nothing in that folder that
belongs to the old version.
That's what makes it so strange.
On Wed, Oct 13, 2021 at 6:25 PM Fred Beckhusen wrote:
> The script was compiled into
But this is just it.
The simulators were not upgraded. They were re-installed in a different
folder so it's a completely new installation.
Could it be that there is a C# or a compiled code stored inside the assets
server?
Asaff
Hi,
Yes on a major upgrade you should delete folder
.../bin/ScriptEngines so all scripts are compiled and initialized again.
Ubit
On 13-Oct-21 11:23, Asaff Belfer wrote:
Hello everyone,
We've recently upgraded our grid to version 0.9.1.1. We found out that some
scripts generate
12 matches
Mail list logo
