Skip to content

Conversation

grooverdan
Copy link

Avoids compile error in gcc-5.4.0 (default in ubuntu-16.04)

sql_acl.cc: In member function 'bool Rsa_authentication_keys::read_key_file(RSA**, bool, char**)':
sql_acl.cc:11688:62: error: ignoring return value of 'size_t fread(void_, size_t, size_t, FILE_)', declared with attribute warn_unused_result -Werror=unused-result fread(*key_text_buffer, filesize, 1, key_file);

Avoids compile error:

sql_acl.cc: In member function 'bool Rsa_authentication_keys::read_key_file(RSA**, bool, char**)':
sql_acl.cc:11688:62: error: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', declared with attribute warn_unused_result [-Werror=unused-result]
          (void) fread(*key_text_buffer, filesize, 1, key_file);
@grooverdan grooverdan changed the title Check filesize read in rsa authentication plugin Check filesize read in rsa authentication plugin (5.6) Aug 3, 2016
@grooverdan
Copy link
Author

I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.

@mysql-oca-bot
Copy link

Hi, thank you for your contribution. Please confirm this code is submitted under the terms of the OCA (Oracle's Contribution Agreement) you have previously signed by cutting and pasting the following text as a comment:
"I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it."
Thanks

@mysql-oca-bot
Copy link

Hi, thank you for your contribution. Your code has been assigned to an internal queue. Please follow
bug http://bugs.mysql.com/bug.php?id=82428 for updates.
Thanks

@grooverdan grooverdan changed the title Check filesize read in rsa authentication plugin (5.6) bug 82428: Check filesize read in rsa authentication plugin (5.6) Aug 3, 2016
dbussink added a commit to planetscale/mysql-server that referenced this pull request Dec 7, 2023
…rsion (mysql#89)

* Ensure to use unique version names for building

We don't want to reuse version numbers nor do we want to have to
manually track these. So let's use the automatic versioning we already
have here for versioning the packages.

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>

* Ensure to use non-colliding package names

We don't want these package names to collide with the packages we've
created from our public fork where we accidentally install those.

---------

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants