Mod binary to use existing .dylib from Applications folder? OpenSSH

Discussion in 'Mac / Hackintosh' started by realpancake, Nov 24, 2016.

  1. realpancake

    realpancake Member

    Joined:
    Nov 24, 2016
    Messages:
    44
    Likes Received:
    9
    Location:
    Upper Slaughter
    I have read a lot this evening whilst trying to get GRM Tools 3.3 to work on 10.11.6 on my MBPro. I understand that you can use OpenSSH plug-ins without changes to the usr/lib/ by following the guides HERE.

    I have the 10.10.2 dylib in the GRM folder BUT... I also have two modded libstXX++.6 & libstXX++.6.0.9.dylibs from something HOOK k'ed in a folder in my Applications.

    I wanted to try and redirect the GRM plugs to this by doing something like:

    install_name_tool -change /usr/lib/libstdc++.6.dylib /System/Applications/ilok/libstXX++.6.dylib GRM\ Freeze

    I'm not certain that this would work so I thought I should seek some advice before I give up & replace the .dylib in usr/lib/

    Am I waaaay off base? Thanks,

    J
     
  2.  
  3. realpancake

    realpancake Member

    Joined:
    Nov 24, 2016
    Messages:
    44
    Likes Received:
    9
    Location:
    Upper Slaughter
    OK,

    So I have just moved over to a new machine on 10.11.6 and I'm re trying this using platensoul's method -

    I have hex edited and renamed the .dylib, made an alias and replaced it's codesign in terminal and placed it into /usr/lib

    When i try to change the plugs dependance I get this error..


    install_name_tool -change /usr/lib/libstdc++.6.dylib /usr/lib/openssh++.6.dylib /Library/Audio/Plug-Ins/Components/GRM\ Freeze.component/Contents/MacOS/GRM\ Freeze

    error: /Library/Developer/CommandLineTools/usr/bin/install_name_tool: can't open input file: /Library/Audio/Plug-Ins/Components/GRM Freeze.component/Contents/MacOS/GRM Freeze for writing (Permission denied)
    error: /Library/Developer/CommandLineTools/usr/bin/install_name_tool: can't lseek to offset: 4096 in file: /Library/Audio/Plug-Ins/Components/GRM Freeze.component/Contents/MacOS/GRM Freeze for writing (Bad file descriptor)
    error: /Library/Developer/CommandLineTools/usr/bin/install_name_tool: can't write new headers in file: /Library/Audio/Plug-Ins/Components/GRM Freeze.component/Contents/MacOS/GRM Freeze (Bad file descriptor)
    error: /Library/Developer/CommandLineTools/usr/bin/install_name_tool: can't lseek to offset: 5050368 in file: /Library/Audio/Plug-Ins/Components/GRM Freeze.component/Contents/MacOS/GRM Freeze for writing (Bad file descriptor)
    error: /Library/Developer/CommandLineTools/usr/bin/install_name_tool: can't write new headers in file: /Library/Audio/Plug-Ins/Components/GRM Freeze.component/Contents/MacOS/GRM Freeze (Bad file descriptor)
    error: /Library/Developer/CommandLineTools/usr/bin/install_name_tool: can't close written on input file: /Library/Audio/Plug-Ins/Components/GRM Freeze.component/Contents/MacOS/GRM Freeze (Bad file descriptor)


    I'm wondering if anyone here can help me.

    Someone with a similar issue suggested that the newest version of Qt has a broken macdeployqt app so, would downgrading to an old Qt SDK and running sudo port uninstall qt4-mac to remove the new SDK work??

    I'm sure everyone is fed up of these reqs by now so my apologies!

    J
     
  4. Ian Duarte

    Ian Duarte Newbie

    Joined:
    Dec 18, 2016
    Messages:
    3
    Likes Received:
    0
    For me it worked on sierra 10.12.2 like this:
    Backup your original .dylib and replace with the one cracked for mavericks. The other ones will not work.
    Everything back to work

    Hope that helps.
     
  5. realpancake

    realpancake Member

    Joined:
    Nov 24, 2016
    Messages:
    44
    Likes Received:
    9
    Location:
    Upper Slaughter
    Thanks for the response Ian - I ended up gifting myself with GRM Classic bundle for Xmas - best gift so far!
     
  6. willynucka

    willynucka Ultrasonic

    Joined:
    Mar 15, 2016
    Messages:
    78
    Likes Received:
    25
    Tried the same with autotune and couldn't get it to work. Have no interest in putting anything in the usr/lib folder at all, but couldn't seem to redirect it to the applications folder :dunno:
     
Loading...
Loading...