View Issue Details

IDProjectCategoryView StatusLast Update
00033063 - Current Dev ListBugpublic2019-04-26 19:32
ReporterK7ZCZAssigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version6.5.0.207 
Target VersionFixed in Version 
Summary0003306: Logbook database code pokes at user registry, uses hard-coded driver names
DescriptionThe logbook database configuration management code (see CLogbookDatabase::ConnectString() ) accesses the registry directly when it should use the ODBC API for enumerating and configuring data sources.

Further, it uses hard-coded driver strings to identify drivers. It should, instead, use the ODBC API to find the driver and the right version.

Side-channeling the API isn't a tennable or stable. The code must be re-written to use supported APIs and best-practices for identifying and configuring available drivers.
TagsNo tags attached.
ModuleLogbook
Sub-ModuleInstall
TestingNot Started

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-04-26 19:32 K7ZCZ New Issue