Bug 43282 - base/univention-licence/lib/license_ldap.c issues
base/univention-licence/lib/license_ldap.c issues
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: License
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on: 35157
Blocks:
  Show dependency treegraph
 
Reported: 2017-01-04 11:56 CET by Philipp Hahn
Modified: 2019-01-03 07:23 CET (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Hahn univentionstaff 2017-01-04 11:56:55 CET
343 »···»···»···if (strncmp(attrFilter,attributeName,strlen(attrFilter)) == 0)
370 »···»···»···»···if (strncmp(attrFilter,attributeName,strlen(attrFilter)) == 0)
 prefix?

149 »···filter = malloc(sizeof(char) * filter_len + 1);
176 »···filter = malloc(sizeof(char) * filter_len + 1);
208 »···filter = malloc(sizeof(char) * (filterLen+1));                                                              
 ENOMEM?

166 lObj* univention_license_ldap_get_licenseObject(const char* licenseDN)
  useless malloc for static filterstr

12 int univention_ldap_set_machine_connection( univention_ldap_parameters_t *lp )
  Needs merge of r75478

9 univention_ldap_parameters_t* lp = NULL;
 static?

code-style
Comment 1 Stefan Gohmann univentionstaff 2019-01-03 07:23:20 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.