search for: polyinstanti

...om main() until all calls are statically resolved. It seems to me, however, that this duplicates (nearly) functionality that is probably already present in the LLVM JIT layer. Here is what I am wondering: Is there some way we can "hook" the global symbol resolver so that we can run the polyinstantiator on demand? I *think* this could be done by running the resolver normally, noticing failure on a symbol that we know ought to exist, code generating the instance definition corresponding to the needed symbol, and then re-performing the lookup at global scope. What I'm not sure about here is...

...resolved. > > It seems to me, however, that this duplicates (nearly) functionality > that is probably already present in the LLVM JIT layer. > > Here is what I am wondering: > > Is there some way we can "hook" the global symbol resolver so that > we can run the polyinstantiator on demand? I *think* this could be > done by running the resolver normally, noticing failure on a symbol > that we know ought to exist, code generating the instance definition > corresponding to the needed symbol, and then re-performing the > lookup at global scope. > &gt...

...equence that GlobalScope will have been // updated to contain a binding for the desired symbol. sym = llvm_resolve_global(GlobalScope, symName); if (!sym) some_failure_action(); I don't think that it's any more complicated than that. This is basically the test that our static polyinstantiator runs right now. Note: I'm still not claiming that this is a good approach in the context of LLVM. I don't have my head wrapped around LLVM enough to have an opinion about that. I simply wanted to make sure that the question was clearly framed. I do, provisionally, think that this part...

...-7.8p1-role-mls.patch Proper handling of MLS systems and basis for other SELinux improvements * openssh-6.6p1-privsep-selinux.patch Properly set contexts during privilege separation * openssh-6.6p1-keycat.patch Add ssh-keycat command to allow retrival of authorized_keys on MLS setups with polyinstantiation * openssh-6.6.1p1-selinux-contexts.patch Additional changes to set the proper context during privilege separation * openssh-7.6p1-cleanup-selinux.patch Various changes and putting the pieces together I would like to get these changes upstream. SELinux is now pretty common on Linux syste...

...been > // updated to contain a binding for the desired symbol. > sym = llvm_resolve_global(GlobalScope, symName); > if (!sym) > some_failure_action(); > > I don't think that it's any more complicated than that. This is > basically the test that our static polyinstantiator runs right now. > > Note: I'm still not claiming that this is a good approach in the context > of LLVM. I don't have my head wrapped around LLVM enough to have an > opinion about that. I simply wanted to make sure that the question was > clearly framed. > > I do, pr...

...clients. Remove COMPOSITE ifdefs around WindowRec bitfield as it has no ABI effect. XACE: Make the default window background state configurable per-window. security: Register resource names in the server-side name registry. xselinux: Rip out the selection code in advance of polyinstantiation support. xselinux: Stub out selection protocol requests. XACE: Require "manage" permission for XKBSetNames. xselinux: Don't throw BadAccess if DixUnknownAccess is passed in to a hook. xselinux: Prefix a few remaining error messages with "SELinux"...

Hello all, in order to connect to my SSH servers from untrusted devices like company computers or my smartphone, I set up 2FA with google-authenticator hooked into PAM. However, this is not really 2FA at least for the smartphone, since I use the same device for generating the TANs and it is also at least inconvenient to always require a new TAN for each connection. I do not want to solely rely