«

What obfuscators handle 1.5? Any comparisons of obfuscators out there?

Thanks
John

DashO Java obfuscator http://www.preemptive.com/products/dasho works
well for my apps.

Sam

A Java Obfuscator should offer maximum protection against reverse
engineering, as this is the main reason to buy an obfuscator.
The obfuscator should rename Packages, Classes, Methods and Fields
using aggressive obfuscator techniques
The obfuscator should stop decompilers from producing usable results
The obfuscator should use Advanced Control Flow Obfuscation
String Encryption features should be included with the obfuscator
Software watermarking is a feature offered by some obfuscator tools to
help track piracy

An obfuscator can improve code efficiency. Look for the obfuscator to
provide Class and method level optimization to improve JIT performance.
The obfuscator should also have Unused Class/Method/Field and constant
pool entry removal. An obfuscator can also provide dynamically-loaded
class (forname) detection

Professional obfuscator models can support efficient Java code
development and deployment. The obfuscator should versions up to 1.5.
An obfuscator should provide Incremental Obfuscation
An obfuscator should provide Automated Stack Trace Translation
An obfuscator should provide Packaging into directories or jars
An obfuscator should support packaging any type of Java - applications,
libraries, applets, servlets, EJBs, etc.
An obfuscator should support fJ2ME CLDC based profiles
An obfuscator should recognize CLDC pre-verified library classes
Obfuscator output should retain 100% pure Java and passes verifiers
Obfuscator control should include command-line interface suitable for
integrating into build environments.
The obfuscator should include a comprehensive User's Guide
The obfuscator should support for Generic Types and Methods
The obfuscator should provide granular configuration.

A Java Obfuscator should offer maximum protection against reverse
engineering, as this is the main reason to buy an obfuscator.
The obfuscator should rename Packages, Classes, Methods and Fields
using aggressive obfuscator techniques
The obfuscator should stop decompilers from producing usable results
The obfuscator should use Advanced Control Flow Obfuscation
String Encryption features should be included with the obfuscator
Software watermarking is a feature offered by some obfuscator tools to
help track piracy

An obfuscator can improve code efficiency. Look for the obfuscator to
provide Class and method level optimization to improve JIT performance.
The obfuscator should also have Unused Class/Method/Field and constant
pool entry removal. An obfuscator can also provide dynamically-loaded
class (forname) detection

Professional obfuscator models can support efficient Java code
development and deployment. The obfuscator should versions up to 1.5.
An obfuscator should provide Incremental Obfuscation
An obfuscator should provide Automated Stack Trace Translation
An obfuscator should provide Packaging into directories or jars
An obfuscator should support packaging any type of Java - applications,
libraries, applets, servlets, EJBs, etc.
An obfuscator should support fJ2ME CLDC based profiles
An obfuscator should recognize CLDC pre-verified library classes
Obfuscator output should retain 100% pure Java and passes verifiers
Obfuscator control should include command-line interface suitable for
integrating into build environments.
The obfuscator should include a comprehensive User's Guide
The obfuscator should support for Generic Types and Methods
The obfuscator should provide granular configuration.
The DashO java obfuscator http://www.preemptive.com is a reasonable
choice as they focus on obfuscators

<> wrote in message
news: ps.com...
>A Java Obfuscator should offer maximum protection against reverse
> engineering, as this is the main reason to buy an obfuscator.
> The obfuscator should rename Packages, Classes, Methods and Fields
> using aggressive obfuscator techniques
> The obfuscator should stop decompilers from producing usable results
> The obfuscator should use Advanced Control Flow Obfuscation
> String Encryption features should be included with the obfuscator
> Software watermarking is a feature offered by some obfuscator tools to
> help track piracy
>
> An obfuscator can improve code efficiency. Look for the obfuscator to
> provide Class and method level optimization to improve JIT performance.
> The obfuscator should also have Unused Class/Method/Field and constant
> pool entry removal. An obfuscator can also provide dynamically-loaded
> class (forname) detection
>
> Professional obfuscator models can support efficient Java code
> development and deployment. The obfuscator should versions up to 1.5.
> An obfuscator should provide Incremental Obfuscation
> An obfuscator should provide Automated Stack Trace Translation
> An obfuscator should provide Packaging into directories or jars
> An obfuscator should support packaging any type of Java - applications,
> libraries, applets, servlets, EJBs, etc.
> An obfuscator should support fJ2ME CLDC based profiles
> An obfuscator should recognize CLDC pre-verified library classes
> Obfuscator output should retain 100% pure Java and passes verifiers
> Obfuscator control should include command-line interface suitable for
> integrating into build environments.
> The obfuscator should include a comprehensive User's Guide
> The obfuscator should support for Generic Types and Methods
> The obfuscator should provide granular configuration.
> The DashO java obfuscator http://www.preemptive.com is a reasonable
> choice as they focus on obfuscators
>

Spam?

--
LTP

"Luc The Perverse" <> writes:
>>The obfuscator should provide granular configuration.
>>The DashO java obfuscator http://www.p(...)tive.com is a reasonable
>>choice as they focus on obfuscators
>Spam?

There is no need to completely quote advertisements
(unless you would get paid by the advertisers to do so).

I would not have seen this message at all, if you would not
have quoted it, because my message filter had suppressed it.

`"Luc The Perverse" <> wrote on
Sat, 24 Dec 2005 22:38:00 -0700 in comp.lang.java.programmer:

>Spam?

If you look at the headers on the original post, you'll see this:

Injection-Info: g47g2000cwa.googlegroups.com;
posting-host=69.40.252.183;
posting-account=Tt-DIg0AAACUPbBpGjHTEvj2F_15rk5U


And in the headers of the two followups that came along in minutes,
you'll see:

Injection-Info: z14g2000cwz.googlegroups.com;
posting-host=69.40.252.183;
posting-account=frIB1A0AAACdf_8g6USvS1A7aN5GX0sA

from "", and

Injection-Info: f14g2000cwb.googlegroups.com;
posting-host=69.40.252.183;
posting-account=7-pGhA0AAAAR2W065rHUrGOblwO8QYZN


from "". The interesting thing is that they
all contain this:

posting-host=69.40.252.183

which suggests that they all three originated from the same machine.
So it looks like the two followups were sockpuppets on the hand of
"".

Personally, I don't think it would have been out of line if the guy
just posted an announcement for his product. It is on-topic, after
all.


--
"If you are seriously interested in fighting for a better world,
begin by identifying the nature of the problem. The battle is
primarily intellectual (philosophical), not political. Politics
is the last consequence, the practical implementation, of the
fundamental (metaphysical-epistimological-ethical) ideas that
dominate a given nation's culture. You cannot fight or change
the consequences without fighting and changing the cause; nor
can you attempt any practical implementation without knowing
what you want to implement."

--Ayn Rand,
*Philosophy, Who Needs It*

"Luc The Perverse" <> wrote
in message news:43ae304a$0$7789
<snip>
>> An obfuscator can improve code efficiency. Look for the
>> obfuscator to>> choice as they focus on obfuscators
>>
>
> Spam?

I just read that in South Korea the folks like spam (the one in
the tin.)
When we were poor (long time ago) we used to get a meat product
that
resembled spam, but was much less tastey.

>
> --
> LTP
>
>
>

"Joan" <> wrote in message
news:_. ..
>
> "Luc The Perverse" <> wrote in message
> news:43ae304a$0$7789
> <snip>
>>> An obfuscator can improve code efficiency. Look for the obfuscator to>>
>>> choice as they focus on obfuscators
>>>
>>
>> Spam?
>
> I just read that in South Korea the folks like spam (the one in the tin.)
> When we were poor (long time ago) we used to get a meat product that
> resembled spam, but was much less tastey.


I think society's public sentiment against spam led to the invention of a
new word, an acronym for unwanted advertising. The original acronym has
been all but lost but the word itself persists!

--
LTP

On Tue, 27 Dec 2005 12:18:55 -0700, "Luc The Perverse"
<> wrote, quoted or indirectly
quoted someone who said :

>I think society's public sentiment against spam led to the invention of a
>new word, an acronym for unwanted advertising. The original acronym has
>been all but lost but the word itself persists!

SPAM was originally canned ham. It is popular in Samoa. Monty Python
did a sketch about it where everything on the menu contains spam. That
lead to its metaphorical use as something ubiquitous you can't get
away from.
--
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.