[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

this sounds like a plan but i think the main goal should be to develop a c version of the wallet and supply this to the exchanges.
the nxt hack at bter was only a matter of time cause all is based on java....

- this is FUD. But what else can you expect from a newbie ...

if this is FUD how can you explain why there are on regular base and not on demand critical security updates for JAVA advised?
http://www.oracle.com/technetwork/topics/security/alerts-086861.html

or compare the cve submission dates to patch availability:
http://www.oracle.com/technetwork/topics/security/public-vuln-to-advisory-mapping-093627.html

now please tell me why i state a huge nxt hack was only a matter of time.

Really if Java was that bad, it's hard to understand why it is so widely used in the enterprise world.

It's FUD because security is not about a vulnerability in Java. A vulnerability STILL needs some malicious code to run before it can be exploited- this is a problem because the average user do run such code every now and then, or another vulnerability in e.g. a browser is used to execute said code. In short don't run untrusted code and you'll be fine, properly firewall the system, and you'll be fine.

you currently mix up javascript and java but thats not the point here. the enterprise world loves java because its powerfull and can be secured by the application design. the most critical point in any design is to only allow defined and trusted network peers access to the java vm. in 99% of all enterprise apps this is done by secured networks. a core element of a wallet application design is to communicate with "anonymous" peers. firewalling a java wallet vm in a exchange environment may only be possible by analysing the traffic payload with snort or similar tools. then you let only pass "known good" packets. this is a really hard (if even possible) job to do which would not have to be done if the wallet code is ported to c. thats the point in my inital reply.

No I do not confuse anything. What I am saying that if you want to exploit a vulnerability in Java the user must either run untrusted code, or it must be a 2 stage exploit where AS AN EXAMPLE a bug in the browser that allow the adversary to execute any code of his choice. That could be a 0-day in the OS or a 0-day in Java.

The simple fact that you really try to tell the world that C is inherently more secure than Java, show quite well you do not understand 101 of hardening applications and securing networked systems.

i see that you don't get it if you talk about a browser and a user running comprimsed code but thats fine for me. convince the world that java is safe and cry if nxt based wallets get attacked.
all i want to have is the best possible security for anything i invest in.
for now the best possible security is java but for long term the coin needs a c based wallet.