Sponsored Content
Full Discussion: Obfuscated C
Top Forums Programming Obfuscated C Post 18503 by LivinFree on Friday 29th of March 2002 01:05:27 AM
Old 03-29-2002
Hey, I like that!
I've moved it to $HOME/bin since it is a lot better than "man ascii"...
Here's one of my favorites:
Code:
 main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);}

It was written by David Korn, and won Best One-Liner in 1987.
Another one I think is awesome is thadgavin.c, a winner in 2000 (source too long to post here).

Also, a stongly suggested entry to look at in jarijyrki.c in 2000. I've actually used that program before for work purposes!

Lookin' good PxT!
 

3 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Removing obfuscated javascript from js files

ello, I am trying to remove obfuscated code in multiple files on a server, the malicious code is surronded by /*km0ae9gr6m*//*qhk6sa6g1c*/ I had success removing from some files using this command sed -i ':strt;s|/\*km0ae9gr6m\*/*/\*qhk6sa6g1c\*/||g;/\/\*km0ae9gr6m\*\//{N;b strt}'... (5 Replies)
Discussion started by: cuantica
5 Replies

2. Web Development

Random - Any help decoding obfuscated code?

I have this following file and I would quite like to get it decoded - any help / advice is appreciated. I would like to know how to decrypt it, however if someone is able to do it for me I would be equally grateful. <?php //Obfuscation provided by FOPO - Free Online PHP Obfuscator v1.2:... (6 Replies)
Discussion started by: mcclunyboy
6 Replies

3. Programming

Obfuscated "Hello World!" in Python 2.7.x...

Obfuscated Hello World! in Python 2.7.x This is seriously impressive:- Obfuscating "Hello world!" - Ben Kurtovic (2 Replies)
Discussion started by: wisecracker
2 Replies
flaw(7) 						 Miscellaneous Information Manual						   flaw(7)

NAME
flaw - a Lua OO management framework for awesome WM widgets DESCRIPTION
flaw stands for Fully Loaded AWesome. It is a LUA object oriented library providing a thin abstraction layer above awesome widgets. It is aimed at being simple and resources efficient. To achieve these goals, flaw provides the following concepts. gadgets To add functionality to awesome widgets, flaw defines gadget objects, which are a wrapper around a widget. All gadgets have proper- ties, events, a refresh mechanism and a data provider (see below). Gadgets can wrap all awesome widget type, namely text boxes, image boxes, graphs or progress bars. flaw provides many gadgets for common system information (like CPU or memory activity). provider flaw tries to minimise system access and data refresh. Since all information do not have the same expiration rate, all gadgets refresh independently. And since some gadgets can share information, all data is provided by providers which can be shared among gadgets. Providers maintain status data from the system and refreshes only when necessary (ie. when the gadget with the shortest refresh rate demands it). events Events are a way for the user to modify the gadget behaviour or properties when some conditions are met. An event is composed of a trigger, which computes the condition, and an action. Event triggers are tested by the providers only when data changes. Both the condition and the action are provided by the user. USAGE
flaw depends on the lua-filesystem package which can be found http://luaforge.net/projects/luafilesystem. Once installed, the following statement must be inserted in awesome configuration before any flaw gadget or mechanism is used. require('flaw') Using flaw consists in creating gadgets, passing them parameters to customize their display and events to add some behaviour to them, and then adding them in a wibox like any other awesome widget. flaw and awful gadgets can live together. The complete flaw documentation is available in Luadoc format. Enter the following command to generate it. LUA_PATH="path_toflaw/doclet/html/?;;" luadoc -d html --nofiles *.lua DIAGNOSTICS
flaw tries to recover upon bad invocations. When something wrong occurs, it outputs warning or error messages to stderr (for example, if awesome was started with xsession, output will be found in ~/.xsession-errors ). BUGS
Certainly a lot. AUTHOR
David Soulayrol <david.soulayrol at gmail dot net> SEE ALSO
awesome(1), awesome-client(1), awesomerc(5) FEBRUARY 2009 flaw(7)
All times are GMT -4. The time now is 10:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy