In response to my earlier note on this list about my Mercurial hook to
check for well-formed XML at commit time, CG kindly pointed me to the
hooks written by Bos for a more extensive set of LL policy checks
(including well-formed XML).
Needless to say, the version Bos wrote is more elegant
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/442/
---
Review request for Viewer.
Summary
---
Disallowed parsing HTTP URLs
Violation: Third Party Viewer Usage
You are connecting to the grid with a viewer that is not in the third
party viewer directory.
However...
A viewer does not need to be on the Third Party Viewer Directory in
order for development or usage of it to be compliant with the Third
Party Viewer
Last I checked there is no requirement to use an approved tvp. even on the tvp
listing page. Looking at the policy and the directory pages, no where does it
say that the viewer must be listed in the tvp...
http://secondlife.com/corporate/tpv.php
exactly which is why this message is so disturbing. accounts have been
terminated from second life for using a viewer not listed in the
directory.
This email is notification that Linden Lab has terminated
your access to the Second Life virtual world due to severe
or repeated violations of the
i have heard two people report that they cannot *initiate* an IM. They can
receive them, but not *start* a session.
On Mon, Aug 15, 2011 at 7:13 PM, Yoz Grahame y...@lindenlab.com wrote:
Not speaking for the team here (especially because I'm not in viewer
development), just myself as a Lion
Careful, it could be a phishing attempt. Do NOT click on any of the
links inside this email (unless you're certain it comes from Linden
Lab, but then again emails can be spoofed).
On 16/08/2011, mala...@tamzap.com mala...@tamzap.com wrote:
exactly which is why this message is so disturbing.
I thought it was a phishing attempt as well. But the account has been
removed from second life. POOF. so unless some phisher has the ability
to terminate accounts this is as real as it gets.
On Tue, 16 Aug 2011 20:21:48 +0200, Marine Kelley wrote:
Careful, it could be a phishing attempt. Do
It might be that the explanation message is mistaken, and it's supposed to
reference the TPVP instead of the TPVD (or even a different policy
altogether, if, say, someone clicked the wrong message). Are you sure that,
whatever viewer(s) was being used, it conformed to the TPVP, and there
wasn't
I am sure. It was a fresh pull from viewer-development as requested by
a fellow dev. 3 days later the email came and the accounts were
terminated.
The point of the matter is, No where does it say that a client MUST BE
LISTED IN THE TPVD in order to comply with that policy. Yet they are
This is interesting as our support team has had reports of this from some of
our own users. We figured it was phishing and suggested said users contact
LL. I don't know the results however...
Jessica Lyon
-Original Message-
From: opensource-dev-boun...@lists.secondlife.com
I knew it couldnt be just a single event. There is something going on
at Linden Lab and honest developers are losing their accounts over it.
On Tue, 16 Aug 2011 14:46:29 -0400, Erin Mallory wrote:
I have been hit with this as well on one of my alts. interestingly, I
have only ever logged that
im just like wtf? the account i got hit by (which i sent the name of to oz) is
still showing active... in search... but its one i rarely use. mostly for
hiding and/or testing stuff. Im hearing the same from other people too now
though in other groups im in...
Date: Tue, 16 Aug 2011
I looked at a few of the accounts from people who contacted security@ to ask
if this was a phishing message. In the cases I've seen, this corresponds to
accounts warned, suspended or banned for using features that violate the
TPV, such as copybotting, payment impersonation, or spamming features.
What were some of the viewers you tested on that account? Typically, the
trigger would have been within the last month.
On Tue, Aug 16, 2011 at 12:07 PM, Erin Mallory angel_of_crim...@hotmail.com
wrote:
im just like wtf? the account i got hit by (which i sent the name of to
oz) is still
the only viewers on this computer are singularity and
viewer-developments source code.
On Tue, 16 Aug 2011 12:12:13 -0700, Brian McGroarty wrote:
What were some of the viewers you tested on that account? Typically,
the trigger would have been within the last month.
On Tue, Aug 16, 2011 at
---
This is an automatically generated e-mail. To reply, visit:
http://codereview.secondlife.com/r/442/#review979
---
indra/newview/skins/default/xui/en/notifications.xml
On Aug. 16, 2011, 1:19 p.m., Boroondas Gupte wrote:
indra/newview/skins/default/xui/en/notifications.xml, lines 5901-5906
http://codereview.secondlife.com/r/442/diff/1/?file=6943#file6943line5901
Shouldn't the same change be made in the translations?
Ah, right. Thanks, will fix.
Heya Oz
Thanks for making Bos' hg hooks public!
I've looked at the unit test you've written for hg policy and have two
questions about it:
1. Is it by purpose that the return code isn't checked after the hg
policy invocation on line 23
believe that your
account was improperly affected, the process you should follow is here:
http://bit.ly/hBIjz
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.secondlife.com/pipermail/opensource-dev/attachments/20110816/012cd0f6/attachment-0001.htm
://bit.ly/hBIjz
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.secondlife.com/pipermail/opensource-dev/attachments/20110816/012cd0f6/attachment-0001.htm
--
Message: 3
Date: Tue, 16 Aug 2011 15:19:33 -0400
From: Erin
http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/oz_viewer-poreview/rev/238624/index.html
STORM-632 http://jira.secondlife.com/browse/STORM-632
URL-like resident display name is shown as clickable HTTP URL in
various places
STORM-782
On 2011-08-16 17:25, Boroondas Gupte wrote:
Heya Oz
Thanks for making Bos' hg hooks public!
I've looked at the unit test you've written for hg policy and have two
questions about it:
1. Is it by purpose that the return code isn't checked after the hg
policy invocation on line 23
23 matches
Mail list logo
