Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Other Programming > Other Programming Languages
Other Programming Languages If you have a coding issue to discuss about another language that really isn't provided for in any other forum here (not ASP.NET C#, C++, VB, PHP, JavaScript, Python, Java, Perl, Applescript, XML or any of the other forum topics we have), post it here. Enough discussion on a language we don't have covered could prompt a new forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Other Programming Languages section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old July 5th, 2007, 04:01 PM
Authorized User
Join Date: Nov 2005
Posts: 15
Thanks: 0
Thanked 0 Times in 0 Posts
Default A security issue of my new computer language


I am designing a new computer language that is very similar to java. Like in java, you can declare some of the members in a class as private and, like java, the source code is always compiled to java bytecode.

But, for reasons I don’t want to get into here, when a member is explicitly declared as private in the source code in my language, the compiler will have to implicitly implement it as a package-access level member in bytecode! What I want to know is: would this bad for security? - would this make the members declared as private in the source code but implemented as package-access in bytecode more likely to be directly accessed in bytecode by malicious code made by computer hackers? (especially over the net).

I am no expert on computer security but my current thinking (which may be wrong) on this issue is that if the computer hacker has the power to directly access a bytecode package-access level class member then that hacker probably would have the power to directly access the same bytecode class member even if it was implemented a private member in bytecode (by, for example, simply changing the access specifier in the bytecode class file) and therefore it would make little difference to security! Please could someone put me right if I am wrong.

Reply With Quote

Similar Threads
Thread Thread Starter Forum Replies Last Post
Code Access Security & Role Based Security robzyc C# 6 April 11th, 2008 02:31 AM
Security Issue Brendan Bartley Access 1 April 26th, 2007 09:37 AM
java security certificate issue getsreenuk Apache Tomcat 0 March 3rd, 2007 05:49 AM
Security Issue rajuru Beginning PHP 3 December 23rd, 2004 09:35 AM
Security Issue vlado2000 Classic ASP Professional 0 March 5th, 2004 02:26 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.