You're right, the can is open right now. Apple is working on closing that can under our feet (see the DYLD_* variable unsetting upon exec in 10.11). I wouldn't be surprised if that trend continues elsewhere :)
Simon ________________________________________ From: Development <development-boun...@qt-project.org> on behalf of Koehne Kai <kai.koe...@theqtcompany.com> Sent: Friday, January 29, 2016 9:10 To: André Somers; development@qt-project.org Subject: Re: [Development] Modify QLibraryInfo to support any default location of qt.conf > -----Original Message----- > From: Development [mailto:development-boun...@qt-project.org] On > Behalf Of Andre Somers > Sent: Friday, January 29, 2016 9:05 AM > To: development@qt-project.org > Subject: Re: [Development] Modify QLibraryInfo to support any default > location of qt.conf > > > > Op 28/01/2016 om 13:00 schreef Maximilian Hrabowski: > >> Why isn't this first ? > >> I would generally expect an environment variable to take precedence > >> over all other configuration options except command-line options. > > You are right, that an environment variable should be considered first. But > I think one of the three possible solutions is enough. I did not mean to > implement all three in this order. For me the environment variable is the > solution that i like least. > > > Wouldn't that open up a can of worms in terms of security of the > application? If setting an environment variable is enough to change what > libs get loaded and you can point to arbitrary different libs, that means > injecting your own code in other peoples applications becomes really easy, > right? I think you could use that to get rights escalation. The can is already open in this case. You can set PATH, LD_LIBRARY_PATH, QML_IMPORT_PATH .... Regards Kai _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
