We present a practical protection mechanism against SQL injection attacks. Such attacks target databases that are accessible through a web front-end, and take advantage of flaws in the input validation logic of Web components such as CGI scripts. We apply the concept of instruction-set randomization to SQL, creating instances of the language that are unpredictable to the attacker. Queries injected by the attacker will be caught and terminated by the database parser. We show how to use this technique with the MySQL database using an intermediary proxy that translates the random SQL to its standard language. Our mechanism imposes negligible performance overhead to query processing and can be easily retrofitted to existing systems.
Read the rest of this entry »

• 0 Comments

How is it different from building an application using visual studio for dot net or any visual java development tool?
The basic difference is the amount of programming that needs to be done is significantly reduced. Reasonably complex applications ERP, CRM, HMS, HCMS, etc can be built without writing programs in any programming language. However, fundamental database and SQL (select statements)
Read the rest of this entry »

• 0 Comments

A Word About Secure Database Access
Unfortunately, this database access code exhibits insecurities of its own. For example, you should never use the sa account (or an equivalent) to access databases from Web applications. Instead, use weak accounts that lack permission to drop tables, insert, update, and delete records, and the like. In addition, you should use stored procedures or parameterized commands in lieu of dynamic SQL commands for added protection against malicious input parameters. Finally, consider encrypting database connection strings to minimize the risk of information disclosure if your source code falls into the wrong hands. And note that truly paranoid ASP.NET programmers encrypt connection strings and store them in ACLed registry keys. When it comes to Web security, a little paranoia can be a good thing.
Read the rest of this entry »

• 0 Comments

Graphical objects, also known as entities, are the visible objects (lines, circles, raster images, and so forth) that make up a drawing. Each graphical object has methods that allow an application to perform most of the AutoCAD editing commands, such as Copy, Erase, Move, Mirror, and so forth. These objects also have methods for setting and retrieving extended data (xdata), highlighting and updating, and retrieving the bounding box of the object. Graphical objects have typical properties such as Layer, Linetype, Color, and Handle. They also have specific properties, depending on their object type, such as, Center, Radius, and Area.
—ActiveX Automation User’s Guide, AutoCAD help file
Read the rest of this entry »

• 0 Comments

Object data allows you to create a simple database in a map and store text and numeric data in your maps directly attached to any object. It is far more powerful than block attributes because object data works with any object, not just blocks. Use object data tables to save any kind of information, run queries based on information in the tables and to create thematic maps. Object data can associate an object with documents from other applications. However, Autodesk Map works with object data created only in Autodesk Map and does not recognize object data from other applications, including AutoCAD®.
Read the rest of this entry »

• 0 Comments

This article shows you how a Java™ 2 Platform, Enterprise Edition (J2EE) application was enhanced with an Ajax-style architecture by using the IBM® WebSphere® Application Server Feature Pack for Web 2.0. Learn how to combine Ajax-style architectures with an existing application without having to rewrite the entire Web application. You’ll also discover some ideas on how to apply the Web 2.0 Feature Pack to your own J2EE applications for IBM WebSphere Application Server. The “Plants by WebSphere” application is among a number of samples that are provided with the IBM WebSphere Application Server Feature Pack for Web 2.0.
Read the rest of this entry »

• 0 Comments

Microsoft provides a very simple layer between the web interface (asp.net 2.0) and the database. The object they use to perform this is the SqlDataSource. It works very well in many cases. It’s fast, easy to use and great for demonstration of technology and to show how fast you can program database type applications. It falls apart (IMHO) when the application starts getting larger and requiring more customization. It’s also very hard to maintain because at the end of the day, it puts most of what it does in the aspx page itself.
Read the rest of this entry »

• 0 Comments

The phenomenon known as Web 2.0 is more than just the web today. Reaching far beyond the browser, this name for live, interactive, user-manipulable data has come to define RIAs (Rich Internet Applications) and RDAs (Rich Desktop Applications). These represent a new generation of Internet-compatible applications that can be implemented across multiple platforms on personal computers, as well as mobile devices (PDAs, smartphones, etc.).
Read the rest of this entry »

• 0 Comments