[Maya-Python] É LESBICA ASSASSINA E PEDOFILA: #MARINABERLUSCONI! COME SUO PADRE MAFIOSO, NAZISTA, PEDOFILO E MANDANTE DI OMICIDI E STRAGI: #SILVIOBERLUSCONI! NE SCRIVE IL BANCHIERE #ANDREASNIGG DI SAF
É LESBICA ASSASSINA E PEDOFILA: #MARINABERLUSCONI! COME SUO PADRE MAFIOSO, NAZISTA, PEDOFILO E MANDANTE DI OMICIDI E STRAGI: #SILVIOBERLUSCONI! NE SCRIVE IL BANCHIERE #ANDREASNIGG DI SAFRA SARASIN ZURICH, PENTITO D'AVER LAVATO LORO SOLDI CRIMINALI.. PER ANNI ED ORA OTTIMAMENTE SPUTTANANTE GLI STESSI! /// PEDOFILIA INCULA BAMBINI E BAMBINE, MAFIA, CAMORRA, ndrangheta TERRORISMO NAZISTA, STRAGI FASCISTE, MASSONERIA SATANISTA OMICIDA E BERLUSCONISMO SON STESSA MERDA. SCUSATE PER MIO ITALANO IMPRECISO, MA SONO SVIZZERO. SONO ANDREAS NIGG DI BANCA J SAFRA SARASIN ZURICH, PREMIATO NEL 2018, 2019 E 2020 COME BANCHIERE SVIZZERO DELL'ANNO A BASILEA. ATTENZIONE: SON DA ARRESTARE SUBITO LA PEDOFILA NAZISTA ASSASSINA #MARINABERLUSCONI MARINA BERLUSCONI, IL PEDOFILO STRAGISTA #SILVIOBERLUSCONI E L'AVVOCATO MASSONE, SATANISTA, NAZISTA, SATA卐NAZISTA, PEDERASTA, SUPER OMICIDA #DANIELEMINOTTI DANIELE MINOTTI DI CRIMINALISSIMO STUDIO LEGALE LISI. INIZIAMO DA QUEST'ULTIMO, PLEASE. É DAVVERO DA FERMARE GIUDIZIARIAMENTE PER SEMPRE, L'AVVOCATO SATANISTA, NAZISTA, SATA卐NAZISTA, PEDERASTA, OMICIDA #DANIELEMINOTTI DI RAPALLO E GENOVA: RAPISCE, INCULA, UCCIDE TANTI BAMBINI, SIA PER VENDERNE GLI ORGANI ( COME DA QUESTA ABERRANTISSIMA FOTO https://www.newnotizie.it/wp-content/uploads/2016/07/Egypt-Organ-Harvesting-415x208.jpg), CHE PER RITI MASSONICO SATANISTI CHE FA IN MILLE SETTE! https://groups.google.com/g/comp.lang.python/c/8LTlfy6wPpQ -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to python_inside_maya+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/d210f666-df0f-4168-b1a2-b8e089deef65n%40googlegroups.com.
Re: [Maya-Python] V Crypt System
yes, something like that might work, but if I am working locally from home sending files to someone else that is also in his own personal computer I can't really force that persone to set the usertSetup.py or the other alternative you mentioned. aarrggg...callbacks are nice, but yeah...doesn't seem to hard to by pass them. I'll have to trust that people will respect the nda agreement... About what I am trying to protect is the rig basically in 2 aspects: 1-prevent redistribution outside a production 2-prevent reverse ingeniering, which I did find out recently that a lot of nda's have a section stating that you agree not to do that...but againhow can you enforce that? it is impossible. So far the safest system is VCrypt, but as we talked before, many clients might refuse to use it even if provide them a license. Anyway, thanks for all the suggestions. El miércoles, 15 de septiembre de 2021 a las 7:47:08 UTC+2, Marcus Ottosson escribió: > it work is you execute that at the beginning of every maya session (for > instance putting it in the userSetup.py), but then you just have to find > this part of the code and remove it… > > About MSceneMessage.addCheckCallback, there are a few ways of installing > it. > >- userSetup.py >- plug-in >- Script node in a New Scene Template > > I’d argue each of these are equally insecure, in that anyone can (1) edit > the userSetup.py, or associated environment variable that points to it, (2) > unload the plug-in, forcefully or launch Maya without plug-ins and (3) find > that hidden spot where you edit the new scene template. > > userSetup.py can be made more secure by residing on PYTHONPATH rather than > in the user’s home directory. That way, you provide your own Maya > executable (e.g. a .bat file on Windows) whereby a userSetup of your choice > is added to PYTHONPATH prior to launch. > > :: maya.batset PYTHONPATH=\\server\pipeline\userSetup.pystart "c:\program > files\autodesk\maya2020\bin\maya.exe" > > That way, the user would be unable to launch Maya without also executing > this userSetup.py. Especially if it is also what loads up relevant pipeline > tooling such that if they were to try and launch it without this executable > (which is read-only, on a network), they would be unable to even use Maya > for their work. > > And again, I think you have to define what you protecting against. > Malicious hacker-animators, or the 99% case? Because no system can ever > protect against every attack; not in Maya, not anywhere. If what it takes > to defeat your system is to bypass a hidden userSetup.py then I’d argue you > have already protected against the vast majority of cases. > > On Wed, 15 Sept 2021 at 04:02, Justin Israel wrote: > >> >> >> On Wed, Sep 15, 2021 at 11:36 AM Rudi Hammad wrote: >> >>> So I cam up with a evil idea that seems to work. >>> . I create a script node that travels with the scene that will check >>> your mac address out from a list of valid addresses (that would be the ones >>> corresponding to the people working remotly on their personal computers). >>> if the address doesn't match it wont open (it opens a new file for >>> instance) >>> . So then, lets say that your address is valid. Now you would think that >>> you can just delete the scriptNode and that's it, right? weI >>> added a callback that triggers when you delete the scriptNode, that deletes >>> everything . >>> >>> Of course we can just change that to something less evil, but maybe this >>> might work? save a scriptnode will what ever callback are needed, and >>> prevent this script node from bein delete? >>> I don't know...I am starting to lose motivation... >>> >> >> What if I just open the scene file with the option to disable script >> nodes? If it's somewhat trivial to defeat the security then you have to >> decide if you are doing this with the goal of absolute security, or just >> being a deterrent and using security-via-obscurity. If there is any way to >> get the scene file opened, either by disabling script nodes, or by another >> binary to ascii conversion that can then edit the script nodes, it kind of >> makes this pointless if the goal is security. >> >> >> >>> >>> >>> >>> El lunes, 13 de septiembre de 2021 a las 22:21:47 UTC+2, >>> justin...@gmail.com escribió: >>> On Tue, Sep 14, 2021 at 7:52 AM Rudi Hammad wrote: > About V crypt, I got in thouch with them and they sent me the system > to test it in demo mode. It work pretty well, but as Justin anticipated > and > as the video showed, all clients are requiered to have the app. > So maya is should be launched from V Crypt, and then you can open the > encrypted files. Which is not ideal because you are enforcing everyone to > purchast their system. > > So as an alternatively I tried to do something with addCheckCallback > that Marcus mention: > > mSceneMsgOpenCheck =
Re: [Maya-Python] V Crypt System
oh noI had no idea you can open files disabeling script nodes. Bummer...good thing I am not working in security. El miércoles, 15 de septiembre de 2021 a las 5:02:23 UTC+2, justin...@gmail.com escribió: > On Wed, Sep 15, 2021 at 11:36 AM Rudi Hammad wrote: > >> So I cam up with a evil idea that seems to work. >> . I create a script node that travels with the scene that will check your >> mac address out from a list of valid addresses (that would be the ones >> corresponding to the people working remotly on their personal computers). >> if the address doesn't match it wont open (it opens a new file for >> instance) >> . So then, lets say that your address is valid. Now you would think that >> you can just delete the scriptNode and that's it, right? weI >> added a callback that triggers when you delete the scriptNode, that deletes >> everything . >> >> Of course we can just change that to something less evil, but maybe this >> might work? save a scriptnode will what ever callback are needed, and >> prevent this script node from bein delete? >> I don't know...I am starting to lose motivation... >> > > What if I just open the scene file with the option to disable script > nodes? If it's somewhat trivial to defeat the security then you have to > decide if you are doing this with the goal of absolute security, or just > being a deterrent and using security-via-obscurity. If there is any way to > get the scene file opened, either by disabling script nodes, or by another > binary to ascii conversion that can then edit the script nodes, it kind of > makes this pointless if the goal is security. > > > >> >> >> >> El lunes, 13 de septiembre de 2021 a las 22:21:47 UTC+2, >> justin...@gmail.com escribió: >> >>> On Tue, Sep 14, 2021 at 7:52 AM Rudi Hammad wrote: >>> About V crypt, I got in thouch with them and they sent me the system to test it in demo mode. It work pretty well, but as Justin anticipated and as the video showed, all clients are requiered to have the app. So maya is should be launched from V Crypt, and then you can open the encrypted files. Which is not ideal because you are enforcing everyone to purchast their system. So as an alternatively I tried to do something with addCheckCallback that Marcus mention: mSceneMsgOpenCheck = OpenMaya.MSceneMessage() def licenseCheckOnOpen(*args): # a function that reads your mac address and if it doesn't match the hardcoded one, it won't open. OpenMaya.MSceneMessage.addCheckCallback(mSceneMsgOpenCheck.kBeforeOpenCheck, licenseCheckOnOpen) but that was a total failit work is you execute that at the beginning of every maya session (for instance putting it in the userSetup.py), but then you just have to find this part of the code and remove it... ps: let me know if this last part is offtopic and I'll just shut up about it. >>> >>> Oh I didn't even connect your MEL and callback questions to this topic. >>> I see now that you were experimenting with related custom approaches. >>> >>> Yea I agree with you that it would be cumbersome to require everyone to >>> purchase some encryption app license. But maybe the approach is that a temp >>> license is given to the client on behalf of the owner of the media and the >>> one imposing the workflow? Having full ownership of the Maya process, as V >>> Crypt wants to do, seems like the only way to get close enough to securing >>> the media. If you ever let the user have direct unregulated access to the >>> source then they can disable whatever checks (callbacks or whatever). >>> "Close enough" is maybe just making it hard enough to avoid mistakes and >>> easily sharing things? >>> >>> El lunes, 13 de septiembre de 2021 a las 19:22:37 UTC+2, Rudi Hammad escribió: > It was still kind in the context of encrypting a maya scene that > derived from the main V Crypt topic, but we'll do. > El lunes, 13 de septiembre de 2021 a las 19:07:28 UTC+2, > justin...@gmail.com escribió: > >> Please make sure to start a new thread if you want to engage in new >> topics. It seems two completely new questions have been asked since the >> original thread was started about V Crypt, and are entirely unrelated. >> Thanks! >> >> On Tue, 14 Sep 2021, 4:25 am Rudi Hammad, wrote: >> >>> That's it! thanks Juan >>> >>> El lunes, 13 de septiembre de 2021 a las 15:33:57 UTC+2, Juan Moraga >>> escribió: >>> Try using "def onOpenCallBack(*args):" instead. Callbacks may pass on arguments to you method, which you can use or not. But you need to allow the function to receive these arguments, otherwise it will raise an exception. On Mon, 13 Sep 2021, 15:09 Rudi Hammad, wrote: > Hello,
