Anyone know how i can deobfuscate the code below i paid for a plane ?(Roblox LuaU ServerScript), obfuscation is "This file was generated using Luraph Obfuscator v13.6.4" thanks.
-- This file was generated using Luraph Obfuscator v13.6.4
https://pastebin.com/raw/UeNxJQPy
Related
I don't have VB or anything installed, as I have absolutely no clue how to properly code (I can read and understand super basic code) - but I have no clue about any functions/ methods etc.
I've got a Lua file that I want to decode/ be able to actually read this file. From what I've read here on stack overflow, I've gathered maybe it's not encrypted, rather in lua crypt or something? Any input would be much appreciated! Thanks!
Here's the code:
FXAP JÈŸ‘Ä#I«ILmOÿ‰ýÚn_ô0J8ôã*2-¿ã´*¶p‹ý
Ëí}ý_A>¢AaÁ`®E÷„êÝ6g¿¿£¹®îãöà€•ãûÛ'—À]M™)bñà?W·S ›(Vâ†É(þ“ñמQ&|#Å´c•HX²¡<d¿CÖÖ[d×A“¨ò“>'fÈîÍ ¿¥±v´ô2Ys2Ñ‚:b/¥˜à¹Ü¬Å H~ß 9SºM‘FCú®}Ñ:Šè|¹7|]òC§CcKX|¾,#
Ž¤6ÚÖ\ºÂZ†ãï¥~t,‘?±…÷ï/è’±Q_™œê'ôYÖenŠ`äCÑ#“IÅ_Kà€þÒ´ek:QýÚ‚ò&ÿO±!ÁÓGâhÏĽD²ÓdŸñÎ^6D3òÚ„üD?ûÕá$‚eÒäúÞ5î72ä±dv¬]hHƒ
Y¤4 ÑÊ#!³-(icæ…*¢ƒ¿þÛLþÉ®±ß¶)îFe!S$ÜS|ƒ¹C¶hl—Ã-í®Ì:+ôÆSD¦¨ÌÅfÌhÕnÉ:_cÔ·Âä"ÏpßÅ7vÅi¸€ß†Mf~÷IBgÕ½
#ÊEüÈÉÙ5¥´·6g†^.æ`Z/Ð[ÏcÁÊ8ô4y[›—A¨›ÿ0j’ºrèyÖ$ÇÿD7"7}è:g
|Ðò¢n¬m8-`{I²Èû«°6˜ê”×o<ñ9*FÔåeDˆ€Åûà]ªý·gÈÿ¥íªCÏâÜá0Ðf¯uÒ·’Æ1<L¹±M¤˜~ïÒ)ÑfQÃq\aň½3K ÐàÀ}ŒXÂœg°’¢d|¹ÛŠ"®£öƒ?È B¼4®½ÎmŸ—r¾)Ù’dçÒ
>L©NN*†q&NòbOñ«ªŸÅ÷S[;×úB ÉS!˼×Yö“í«ÚXÎ]óÜ”®V Véeú"ˆZåZÃE/5GïÊýUÉd–‚ /¼Rd—ƒÅ%Ñà_ÚuŽõ¨·çö}ˆ /y“Ùèø…°åñ ˜Žî$¬¸NfHþqó•¨=€¦}d¨.îÓ±"ÂnãR =8Fx<›ötuèu‘í*Ÿxa Õ½
ç2ÃÓ8¯ —û–7,Š´2ý’5êÒfRè×íX¼’ühA"µsEÕƒ†×¯!Œ˜rp²Gòä×`þ/ àÃ(%B˜UÀð´÷²©ÏëÇ
wY•ƒå™/×)ú·]qÇx›P
~d{#
¶ ¬À€r~…Ûíü£Vn}QÙäJÜ[³dJÁš8±ÌèÏb×ÿÆñ'*ƒŠ*K`›éw=Þ¢’®ÁK¿šÍ"¯×¹
HdÈQãí–y}3ÂOäÞÃRÇ'uG& VY1
ôÚ<lk ®·Êïݲ´ÄEô+}ƒÞó„`Txs¨Ý©ãáOkÂCÇ.’á„oÚæ0‚ê¶iø̉æ9Ä9ºík]y¿ñI‚Õ=\{ñü•ñÎáÚ4Ù$íi—˜ÎEB‘Šªmha-9÷œû
Tried basic research, online encryption detection websites (None worked)
I have lots of BTS2010 unit tests that check an XML file can be mapped to flat file.
I have developed my first of such tests on BTS2013r2 but on executing TestableMapBase.TestMap(_inputFilename, _inputType, outputFilename, _outputType), I get the error "Generate schema instance failure"
I've used reflector to debug the MS assemblies and got as far as the following line within CFrameworkSchemaTreeExtensions.cs of Microsoft.BizTalk.TOM.Adapter :
infoArray = instanceGenerator.GenerateInstance(filename, xmlInstance);
on executing, the infoArray is populated with the following error
ErrorInfo: hexadecimal value 0x00, is an invalid character. Line 2, position 1."
Prior to executing I have taken the content of xmlInstance, pasted into Notepad++ and used the Hex plugin to search for null characters (hex 0x00), there are none.
I have tried many different XML inputs to the maps on two different BizTalk development laptops and get the same result.
Has anyone been able to successfully run tests of XML to flat file in BTS2013r2?
Today I have created the most basic of solutions (1 BizTalk project + 1 unit test project) in order to test if this really is a Microsoft bug. It does seem that way because I got the same error when running this very simple test on a third BizTalk development laptop. I have added the source code to the following github repo: https://github.com/RobBowman/FFMapFailBTS2013r2
Make sure it is not an encoding issue. Finding a 0x00 at that position sounds like the input file is in UTF-16 format, while the processor is expecting UTF-8 or another single-byte encoding.
Microsoft have published a hotfix for this - see: https://social.msdn.microsoft.com/Forums/en-US/cacecbfd-8b71-409c-bd59-2eed26950f25/test-map-to-flat-file-in-bts-2013r2-does-this-ever-work?forum=biztalkgeneral
I am quite new to postgresql full text search and I am setting up the configuration as where can I download the ispell *.dict and *.affix filefollowing (exactly as in docs):
CREATE TEXT SEARCH DICTIONARY english_ispell (
TEMPLATE = ispell,
DictFile = english,
AffFile = english,
StopWords = english
);
So, this I think expects files english.dict and english.affix on for example:
/usr/share/postgresql/9.2/tsearch_data
But these files are not there. I just have ispell_sample.dict and ispell_sample.affix - which when included above work fine - no problem.
So... I followed this post and downloaded the required dictionary from the open office people and renamed the .dic to .dict and .aff to .affix. Then I have checked (using file -bi dict.affix and file -bi english.dict and they are UTF8 encoded).
When I run the above text search dictionary, I get the error:
ERROR: wrong affix file format for flag
CONTEXT: line 2778 of configuration file "/usr/share/postgresql/9.2/tsearch_data/english.affix": "COMPOUNDMIN 1
"
I was wondering if anyone had clues on how to solve this problem or if anyone had encountered this before..
Thanks./.
UPDATE:1: I guess the question can be rephrased as follows:
where can I download the ispell *.dict and *.affix file for postgres
Here's a good reference: https://www.cs.hmc.edu/~geoff/ispell-dictionaries.html This is a good resource for those dictionaries of any language.
Ada is still new to me, so I am trying to find my way around the GPS IDE. I asked another question earlier, but I think this problem has precedence over that one, and may be at the root of my trouble.
When I compile, I am getting a long list of *warning: source file ... not found"
In my .gpr file, I have listed all of the spec and body source files and use the following naming scheme:
package Naming is
for Casing use "mixedcase";
for Dot_Replacement use ".";
for Spec_Suffix ("ada") use "_s.ada";
for Body_Suffix ("ada") use "_b.ada";
end Naming;
What is odd it the error messages all look either like this:
warning: source file "xxx_b.adb" not found
or this
warning: source file "xxx.adb" not found
Note that neither of these (xxxb.adb or xxx.adb) conform to the file specs, which should end with .ada.
Can someone explain what is going on here?
I'm 99% sure that the problem is one of the ones I mentioned in answer to your other question: GNAT does not normally support more than one compilation unit in a file. I got exactly the behaviour you describe with GPS and these files:
james_s.ada:
with Jane;
package James is
end James;
jim_s.ada:
package Jim is
end Jim;
package Jane is
end Jane;
The error message on compiling james_s.ada says it can't find Jane_s.ada, but when I ask GPS to go to the declaration of Jane it takes me to the "correct" line in jim_s.ada.
You could use gnatchop to split jim_s.ada, but it doesn't understand project files or naming conventions; you probably want to keep the existing names for the code that works, so you'd rename gnatchop's output as required.
However! to my great surprise, it turns out that GNAT does support having more than one compilation unit in a file, provided package Naming in the project file tells it about each unit in the file:
package Naming is
for Casing use "mixedcase";
for Dot_Replacement use ".";
for Spec_Suffix ("ada") use "_s.ada";
for Body_Suffix ("ada") use "_b.ada";
for Spec ("Jim") use "jim_s.ada" at 1;
for Spec ("Jane") use "jim_s.ada" at 2;
end Naming;
It's up to you whether to do this or to bite the bullet and use gnatchop, either on the multi-unit files or on the whole source tree.
First off, this isn't an Ada problem, its a Gnat problem. Other Ada compilers have no problem with the file names you are using.
However, Gnat is rather unique in that it expects there to be only one program unit (package body, package spec, stand-alone routine, etc) per source file. This is because it is also rather unique in that it expects to be able to find the source code for any program unit just by knowing that unit's Ada intentifier. Most other Ada compilers maintain some kind of library file that maps file names to program units, and you have to register all your files into it. (Whereas your typcial C compiler just leaves the problem of finding files for all your code up to the user entirely).
Generally the easiest thing to do with Gnat, the way that will cause you the least trouble, is to just use its default file naming convention (and of course don't put multiple program units in a single file.
If you already have some existing Ada code (perhaps developed for another compiler), the easiest way to import it into Gnat is typically to run the gnatchop tool on it all. So that's what I'd suggest you try.
From GPRbuild User's Guide:
Strings are used for values of attributes or as indexes for these attributes. They are in general case sensitive, except when noted otherwise [...]
Based on this, I believe you have to use "Ada" instead of "ada" as index for Spec_Suffix and Body_Suffix. I currently do not have access to the tools for testing this, so I suggest to just try it out.
I am translating a Ada83 to Ada95 file. The problem happens when I try to compile a file which calls a separate. The error is "Illegal character " and refers to directive to preprocessor:
with BAS_PUT;
#if ADA_COMPILER="GNAT" then
WITH ADA.GNAT_PUT;
#else
WITH ADA_PUT;
#end if;
separate(A_CALL_PUT)
procedure ....
This problem does not happen when the same preprocessor directive is in a file adb that it is not a separate function.
Someone can help me???
Ada has no preprocessor, so # is indeed an illegal character.
Some compilers (eg: Gnat) do come with one, but if so it is one of their own devising. If you like you can set up your build system to run your Ada source files through external preprocessor (eg: the C pre-processor). I've never done that, but I'm told its eminently doable.
If your compiler does happen to come with a preprocessor, it is non-standard. Use it if you like, but by definition it will be useless for creating portable source files (which appears to be what you are trying to do with it).
Most folks would consider it better form to just create different source files for your different environments, and have the build environment (make rules?) switch between them.