Re: 'code too large' error with 2D array

From: Anthony Borla (ajborla_at_bigpond.com)
Date: 10/31/03 

Date: Fri, 31 Oct 2003 11:10:33 GMT

Christophe,

"Christophe Vanfleteren" <c.v4nfl3t3r3n@pandora.be> wrote in message
news:jjpob.116531$EX3.5191722@phobos.telenet-ops.be...
>
> Anthony Borla wrote:
>
> > Why would you want to include the array data in the source
> > code, anyway - security reasons such as avoiding tampering
> > of the data by outsiders ? If so, a simple option is to place the
> > text file in the '.jar' file you are using to distribute your program.
> > There were a couple of posts on this [accessing resources in
> > a '.jar' file] recently.
>
> I hope you do not really believe that putting files in a jar provides
> you with more security, unless you believe in security by
> (really minimal) obscurity.
>

No, no, not at all. In hindsight, I should have omitted the word 'security'
and used the phrase 'more tamper proof than a standalone file'. Post and
learn :) !

>
> Anyone can look inside a jar file (as it is just a zip file) and extract
> what they want.
>

My intention was to suggest a very simple means of minimising the
possibility of data tampering, something quite easy to do with a standalone
data file [e.g. file could be deleted, corrupted, or edited (and
modification dates altered)], while more difficult [to mask evidence of
tampering] in a '.jar' file.

Cheers,

Anthony Borla

Relevant Pages

  • More on SCADA comm security
    ... Further to my last (hopefully this posting is visible amongst all ... RF security has not been an issue ... My client believes that the threat of RTU tampering is still low, ... The worst threat scenario is that the attacker steals an RTU. ...
    (comp.arch.embedded)
  • Re: code too large error with 2D array
    ... > Anthony Borla wrote: ... There were a couple of posts on this ... > with more security, unless you believe in security by ... > Anyone can look inside a jar file and extract what ...
    (comp.lang.java.help)