Bug #19516 stored procedur encoding/obfuscating

Submitted: 3 May 2006 13:06 Modified: 4 Oct 2008 20:28
Reporter: cristian vanti Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S4 (Feature request)
Version:5.1 OS:Any (all)
Assigned to: CPU Architecture:Any

[3 May 2006 13:06] cristian vanti
Description:
It's very useful to encode a procedure avoiding that clients can modify it or reverse engineer it. 
Oracle permits it. SQLServal too. Oracle is better because you can provide an obfuscated script to install the procedure/function inside a client db. With SQLServer you can't.

How to repeat:
on oracle:
wrap iname=get_date_string.sql
[12 May 2006 17:26] Valeriy Kravchuk
Thank you for a reasonable feature request. Yes, something similar to Oracle's wrap may be useful to some "closed-source" software developers.
[27 Nov 2006 13:36] mohammed ali
when are we going to get this in mySQL?
[4 Oct 2008 20:28] Konstantin Osipov
Duplicate of Bug#4210 Stored Procedure Encryption.
[2 Feb 2010 15:44] Max Arbos
So this one links to 4210 and that one links to this one....but is there any progress on this?

Would be a useful feature to have in my upcoming project.

Thanks.
[28 Mar 2013 11:05] Charles Bradshaw
While code encryption is mostly undesirable, there circumstances making the feature very useful.

Here is a good example of the use of WITH ENCRYPTION when defining a stored function.

SELECT AES_DECRYPT(passwd,'secretkey') AS cleartext FROM table ....

It is possible to place 'secretkey' in a stored function, but pointless if the code is visible!

Like this:
CREATE FUNCTION secret()
WITH ENCRYPTION
RETURNS CHAR(9)
BEGIN
 RETURN 'secretkey';
END

Even if the database is compromised passwd and the AES key are protected.
[26 Nov 2013 8:54] Awlad Hossain
Though this is an old issue in the list, found no solution in the reply. So I am enquiring again if there's any solution for the stored procedure encryption currently!

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.053 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.