Do not use Process.GetCurrentProcess() to get calling executable
----------------------------------------------------------------
Key: DNET-293
URL: http://tracker.firebirdsql.org/browse/DNET-293
Project: .NET Data provider
Issue Type: Improvement
Affects Versions: 2.5.1
Environment: Windows XP SP3, Kaspersky Internet Security 2009
Reporter: Valeriy
Assignee: Jiri Cincura
Priority: Blocker
In FbConnectionInternal.cs at line 548 DO NOT use
"Process.GetCurrentProcess().MainModule.FileName" to determine calling
executable. Instead of this please use "Assembly.GetEntryAssembly().Location"
because call to Process.GetCurrentProcess() demands application to increase
they privileges to "Debug privileges" (that we don't need at all).
By calling "Assembly.GetEntryAssembly().Location" we will get the same process
string as call to "Process.GetCurrentProcess().MainModule.FileName" but
without requesting debug privileges.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
