Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request - support for 'REQUIRE SSL' option on mysql_grants state #5778

Closed
jedd opened this issue Jun 27, 2013 · 3 comments
Closed

Request - support for 'REQUIRE SSL' option on mysql_grants state #5778

jedd opened this issue Jun 27, 2013 · 3 comments
Labels
Feature new functionality including changes to functionality and code refactors, etc. Platform Relates to OS, containers, platform-based utilities like FS, system based apps stale State-Module
Milestone

Comments

@jedd
Copy link

jedd commented Jun 27, 2013

As of salt 0.15.3 there does not appear to be a way to grant rights to a user and constrain / allow that connection to use SSL.

As per http://dev.mysql.com/doc/refman/5.0/en/grant.html there are myriad other REQUIRE features, which seem less used, but some abstraction here would doubtless be preferable.

@basepi
Copy link
Contributor

basepi commented Jun 27, 2013

Thanks for the request! I've added it to the next release milestone.

@basepi basepi modified the milestones: Helium, Hydrogen Release Feb 4, 2014
@basepi basepi modified the milestones: Approved, Helium Apr 21, 2014
@sandbender
Copy link
Contributor

I'm gonna work on this shortly, just an FYI for anyone else looking at the issue in the interest of avoiding duplicate effort ;)

sandbender added a commit to sandbender/salt that referenced this issue Apr 23, 2014
@jfindlay jfindlay added the Platform Relates to OS, containers, platform-based utilities like FS, system based apps label May 26, 2015
@stale
Copy link

stale bot commented Nov 10, 2017

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

@stale stale bot added the stale label Nov 10, 2017
@stale stale bot closed this as completed Nov 17, 2017
protochron added a commit to protochron/DeDRM_tools that referenced this issue Nov 28, 2020
It looks like Big Sur removed `libcrypto.dylib` as a file on the
filesystem, so loading it using `ctypes.find_library` fails which breaks
Kindle decryption. Now to load a dylib you need to attempt to load it
directly and the operating system will load the dylib from the OS' cache
or fail.

This fixes the problem by explicitly setting the path to libcrypto to
`/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the
file, loading the dylib and raising an exception if it fails at that
point.

See saltstack/salt#5778 for more detailed info.

Closes apprenticeharper#1369.
protochron added a commit to protochron/DeDRM_tools that referenced this issue Nov 28, 2020
It looks like Big Sur removed `libcrypto.dylib` as a file on the
filesystem, so loading it using `ctypes.find_library` fails which breaks
Kindle decryption. Now to load a dylib you need to attempt to load it
directly and the operating system will load the dylib from the OS' cache
or fail.

This fixes the problem by explicitly setting the path to libcrypto to
`/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the
file, loading the dylib and raising an exception if it fails at that
point.

See saltstack/salt#5778 for more detailed info.

Closes apprenticeharper#1369.
protochron added a commit to protochron/DeDRM_tools that referenced this issue Nov 28, 2020
It looks like Big Sur removed `libcrypto.dylib` as a file on the
filesystem, so loading it using `ctypes.find_library` fails which breaks
Kindle decryption. Now to load a dylib you need to attempt to load it
directly and the operating system will load the dylib from the OS' cache
or fail.

This fixes the problem by explicitly setting the path to libcrypto to
`/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the
file, loading the dylib and raising an exception if it fails at that
point.

See saltstack/salt#5778 for more detailed info.

Closes apprenticeharper#1369.
protochron added a commit to protochron/DeDRM_tools that referenced this issue Nov 28, 2020
It looks like Big Sur removed `libcrypto.dylib` as a file on the
filesystem, so loading it using `ctypes.find_library` fails which breaks
Kindle decryption. Now to load a dylib you need to attempt to load it
directly and the operating system will load the dylib from the OS' cache
or fail.

This fixes the problem by explicitly setting the path to libcrypto to
`/usr/lib/libcrypto.dylib` if `ctypes.find_library` does not find the
file, loading the dylib and raising an exception if it fails at that
point.

See saltstack/salt#5778 for more detailed info.

Closes apprenticeharper#1369.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature new functionality including changes to functionality and code refactors, etc. Platform Relates to OS, containers, platform-based utilities like FS, system based apps stale State-Module
Projects
None yet
Development

No branches or pull requests

4 participants