Login

Please log in to view your cart or post on the forum



Modular Systems Blog

Where all the bells and whistles are

[MS] Onyx

Posted by: Fractured

Tagged in: Untagged 

Fractured

 

Various recent events have stirred up yet another storm of misinformation and rumor about certain third party viewers; this has once again brought to light the fact that most people know little about most of the harmful viewers in circulation; the viewers that violate licensing agreements to stay closed source, the ones equipped with content theft tools and weapons designed to intentionally crash other viewers and sims, or otherwise ruin Second Life for others.

These viewers generally remain private, closely guarded and shared either with close friends or for a significant fee, the reason being that exploits are quickly identified and neutralized when released in a public manner.
The result of this is that nobody can be sure of the capabilities of these viewers, information posted on blogs and forums is woefully inaccurate at the best of times, and even more often misinformation spread by those who want the public to remain in the dark. We spent a long time discussing this, and we've come to the conclusion that sharing the information that we've gathered and independently confirmed about these viewers is the right decision, as it will give people the answers they need to make informed decisions on how to protect their content.

This is why we have chosen to make public the Onyx project here at Modular Systems. 

Onyx is a project in which a group of our core developers explicitly spend time locating and fixing the vulnerabilities that can be used to crash Second Life viewers or simulators, that are used to violate the permissions systems, or to infringe upon the rights and degrade the experience of Second Life users. This is done both by testing for potential new vulnerabilities, maintaining watch over the most popular forums and websites for sharing these viewers, and by acquiring copies of said viewers to test and identify any exploits they may be using.
Confirmed exploits are patched in Emerald if it is possible for us to do so, and immediately communicated to Linden Lab so that they can make the necessary changes to render them ineffectual.

Since the project began it has remained private, because it was not important for anyone to know it existed as long as the exploits were fixed. We are changing this now because the Onyx project is undergoing significant changes, both as a result of Linden Lab's Policy on Third Party Viewers and the changes this policy will cause developers of these harmful viewers to make as they struggle to hide their identity.

We are creating a public site for Onyx; on this site we plan to list every viewer we are aware of, which of them are known to have malicious features, and what those features are. Think of it as a viewer reference that actually includes viewers that don't want to be found.
We are announcing this because you can help us. Our resources are finite, and there are a lot more people developing these malicious programs than there are trying to stop them. 

Together we can limit the spread and functionality of these viewers.

What we need you to do is send us information on anything that:
* could be used to crash a viewer (most significantly on-demand)
* could be used to crash a sim on-demand
* could be used to violate the permissions system

Also more importantly, any malicious viewer, especially any that we do not currently have any information listed on or any for which you feel our information is incomplete or inaccurate.

Viewers sent to us will be analyzed and their nature listed on the viewer list. Don't worry about any sort of "access control" or "security" a malicious author may have put in place; its not an issue for us, although any details would be welcome if available.

In any of the above cases we encourage you to also report them as a SEC JIRA entry at http://jira.secondlife.com/ ; this both guarantees that Linden Lab knows about it, and ensures that if a bounty is issued by Linden Lab, it will be received by you, not us.

Any materials can be sent via email to onyx@modularsystems.sl for immediate review.

We expect there may be some controversy over this; however, we feel that by working with all of you, instead of alone, we can do far more to combat malicious viewers, whether they be for content theft, to attack other residents, or both.
You can find more information at http://onyx.modularsystems.sl/ .

POLL: Default audio engine for Linux

Posted by: Discrete

Tagged in: Untagged 

Discrete
pollcode.com free polls
Default audio engine in Linux: FMOD or OpenAL?
FMOD OpenAL   

Click Read More on this blog post for a lot more information.

After finding a solution for my own audio issues in Ubuntu 9.10, I'm leaning heavily toward OpenAL. Build 1632 of Emerald happened to have a bug that prevents OpenAL from being utilized, so I have rebuilt it and made a fixed version, 1633, available -- otherwise it would be rather hard to try it out for yourself and make a judgement on the poll.

In the current version, OpenAL can be enabled by editing the secondlife wrapper script used to launch the viewer and uncommenting the line that disables FMOD as shown here:

## - Avoids using any FMOD audio driver.
export LL_BAD_FMOD_DRIVER=x

 


[Emerald] 1632 Release

Posted by: lordgreggreg

Tagged in: Untagged 

lordgreggreg

Emerald Release 1632 is finished!

Download it here
Read the Documentation

  • Fixes and Changes from the 1628 RC.
    • cao chat command no longer causes a crash (Zwagoth)
    • Login manager saves setting per grid + other bug fixed (LGG)
    • (???) in radar no longer apear

You can also check out the  Change log


[Emerald] 1628 Release Candidate

Posted by: lordgreggreg

Tagged in: Untagged 

lordgreggreg

Download it here
Read the Documentation

  • Fixes and Changes.
    • Saved logins manager! Will both auto save accounts (if "save login info" is checked) as well as give you the meerkat manager to edit them, use them on different grids, etc (LGG)
    • Texture Loading has been fixed.  Higher quality loading, and much faster loading than 1585 (Zwagoth)
    • Particle changes have been turned off by default (that allow follow source to work properly) due to some broken content.  They can be re-enabled via the debug setting "EmeraldUseNewFollowSourceLogic" (Zwagoth)
    • Emerald Arc changes can be reverted back to the broken method via the debug setting "EmeraldUseProperArc" (Zwagoth)
    • Irc auto-logins have been turned off to help confused users, they can be re-enabled by the irc prefs panel (Zwagoth)
    • Crash from pressing script count button on radar window is fixed (LGG)
    • Preprocessor and script preview bug fixed (Fractured)
    • Mouse wheel + ctrl or shift adjustments are not reset till you press escape (LGG)
    • Changes so SideBySidefix is no longer required.
    • Script counter does not freeze up
    • Skins from kirsten's added
  • There is a KNOWN crash in the "cao on" command if the client ao window was opened and then closed. This will be fixed before proper release.

You can also check out the  Change log

For any help and support, please go to the forums here or contact our support volunteers.


[Emerald] 1585 Release

Posted by: jessica_lyon

Tagged in: Untagged 

jessica_lyon

Emerald viewer build 1585 released!

This build focuses on many stability and performance improvements, as well as some awesome new features!
Download it here

Read the Change log
Read the Documentation
The Emerald Team.

P.S.  There will be no optimized version this time.  The one download provided is already optimized fully and works for all computers. P.S. If you are having the "Application failed to start" error. Please read the page HERE




[Emerald] Wiki

Posted by: jessica_lyon

Tagged in: Untagged 

jessica_lyon

As I promised.. DOCUMENTATION!

Announcing our new official Wiki site. This is a work in progress and will continue as such. I wanted to announce it now as we are on the eve of the next release!

Please have a look through it, most features are well documented now, as well as a trouble shooting guide and more to come....


[Emerald] Dev and Other Blogs

Posted by: Fractured

Tagged in: Untagged 

Fractured

Every once in a while, I have had the impulse to blog about things that don't really merit going on everyones login screen. I'm not sure if others have, but apparently enough were interested in my solution. There is now a subdomain dedicated to blogs of various individuals working here in the Emerald project or on other things in Modular Systems. This is http://blogs.modularsystems.sl/ .

Shown there, and reposted here as a why not:

Fractured - http://blogs.modularsystems.sl/fractured/
Chalice - http://blogs.modularsystems.sl/thatpurpleone/
LordGregGreg - http://blogs.modularsystems.sl/lgg/
Discrete - http://blogs.modularsystems.sl/discrete/
Neurocam - http://blogs.modularsystems.sl/neurocam/
Phox - http://blogs.modularsystems.sl/phox/
Jessica Lyon - http://blogs.modularsystems.sl/jessica_lyon/
Zwagoth - http://blogs.modularsystems.sl/zwagoth/







[Emerald] Icon Behavior Poll

Posted by: lordgreggreg

Tagged in: Untagged 

lordgreggreg

Please vote how you would like your default icon to behave.

 

How would you like the default icon to behave.
Pick a constant icon for all releases.
Change the icon for each release.
  

 


[Emerald] MacOs 10.4 support

Posted by: Hyang

Tagged in: Untagged 

Hyang

Question to all Mac users, how about moving from 10.4 on 10.5 and 10.6?

Apple stopped support for 10.4 and Mac users still on Tiger systems should be aware that there are no further security or system patches planned for these systems.


[Emerald] Meetings with Linden Lab

Posted by: Fractured

Tagged in: Untagged 

Fractured

 

Over the course of the last year or so, more and more people have chosen to use the Emerald Viewer; so many in fact, that it is now the most used third party viewer in Second Life. As a result, it is undeniable that even the most incidental of changes in Emerald, when multiplied by the sheer amount of users, can cause drastic effects on the grid. We thus felt it was necessary to work more closely with Linden Lab to prevent any serious issues from occurring.


As some of you may already know, for the past several weeks we have been meeting with representatives from Linden Lab for the purpose of discussing issues that impact the Second Life service and the Emerald Viewer. By initiating and maintaining direct and frequent contact with Linden Lab, we have access to the information necessary to ensure that our improvements and features do not disrupt the service. This allows us to make certain that the changes we implement, when scaled up to the tens of thousands of people using Emerald, will not cause anything to explode. ;P


<< Start < Prev 1 2 3 4 Next > End >>