[sldev] Patch to Address Debit Permission Spoofing
Chance Unknown
chance at kalacia.com
Sat Jun 2 06:03:53 PDT 2007
You missed the earlier discussion. Why do you need to inspect a prim
that you own? To find out who the joker was that sent you the prim
thats robbing you? You shouldn't accept inventory items from a
grey-goo cloud in the first place -- let alone rez them.
Thats part of the game legacy that all NOOBS get at one point. Then
after that we all laugh that someone else got hit with it too.
On 6/2/07, Kele Kravelin <grazel.cosmo at gmail.com> wrote:
> Hmmm has anyone told the victim here about hte newish 'inspect' pie menu
> option. As I recall it shows the owner and creator of all prims and
> inventory of an object, that should give the name of the creator of the
> malicious script and help track it down. Of course that means one of the
> victims would have to believe Dave and work with him to track the true thief
> down. Also they can look at their transaction history since their lost L$
> will be going to someone (and if Dave is innocent it won't be Dave's name).
> While there are remedies (which many will just ignore and just go after the
> fast 'solution') it does highlight a need for changes in the debit
> permission system.
>
>
> On 5/30/07, Tateru Nino <tateru.nino at gmail.com> wrote:
> >
> >
> > Able Whitman wrote:
> > > Of course, as others have pointed out, malicious scripts are rare. But
> > > the need to grant an object the debit permission is also rare, or at
> > > least it is uncommon. And once granted it is difficult to both revoke
> > > the permission and to seek remedy for fraudulent debits.
> > Not so rare, perhaps:
> > http://www.gridgrind.com/?p=93
> >
> > --
> > Tateru Nino
> > http://dwellonit.blogspot.com/
> >
> > _______________________________________________
> > Click here to unsubscribe or manage your list subscription:
> >
> /index.html
> >
>
>
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html
>
>
More information about the SLDev
mailing list