{"schema":"libjg2-1", "vpath":"/git/", "avatar":"/git/avatar/", "alang":"", "gen_ut":1756843616, "reponame":"openssl", "desc":"OpenSSL", "owner": { "name": "Andy Green", "email": "andy@warmcat.com", "md5": "c50933ca2aa61e0fe2c43d46bb6b59cb" },"url":"https://warmcat.com/repo/openssl", "f":3, "items": [ {"schema":"libjg2-1", "cid":"4c8b95accd0a196ad7347d37ffeb1f59", "commit": {"type":"commit", "time": 1463413596, "time_ofs": 120, "oid_tree": { "oid": "31cd7185173a82f18b896bf32386b6ac8951bdc0", "alias": []}, "oid":{ "oid": "531e9dcc243a967832fbe784dfc0d226422216b2", "alias": []}, "msg": "Windows: Add CRYPT32.LIB to the libraries to link you app with", "sig_commit": { "git_time": { "time": 1463413596, "offset": 120 }, "name": "Richard Levitte", "email": "levitte@openssl.org", "md5": "b737120f0642a6a5c30c6291e6170c77" }, "sig_author": { "git_time": { "time": 1463085132, "offset": 120 }, "name": "Richard Levitte", "email": "levitte@openssl.org", "md5": "b737120f0642a6a5c30c6291e6170c77" }}, "body": "Windows: Add CRYPT32.LIB to the libraries to link you app with\n\nReviewed-by: Matt Caswell \u003cmatt@openssl.org\u003e\n(Merged from https://github.com/openssl/openssl/pull/1063)" , "diff": "diff --git a/NOTES.WIN b/NOTES.WIN\nindex 1c10b75..f2fb087 100644\n--- a/NOTES.WIN\n+++ b/NOTES.WIN\n@@ -105,18 +105,18 @@\n This section applies to non-Cygwin builds.\n \n If you link with static OpenSSL libraries then you're expected to\n- additionally link your application with WS2_32.LIB, ADVAPI32.LIB,\n- GDI32.LIB and USER32.LIB. Those developing non-interactive service\n- applications might feel concerned about linking with the latter two,\n- as they are justly associated with interactive desktop, which is not\n- available to service processes. The toolkit is designed to detect in\n- which context it's currently executed, GUI, console app or service,\n- and act accordingly, namely whether or not to actually make GUI calls.\n- Additionally those who wish to /DELAYLOAD:GDI32.DLL and /DELAYLOAD:USER32.DLL\n- and actually keep them off service process should consider\n- implementing and exporting from .exe image in question own\n- _OPENSSL_isservice not relying on USER32.DLL.\n- E.g., on Windows Vista and later you could:\n+ additionally link your application with WS2_32.LIB, GDI32.LIB,\n+ ADVAPI32.LIB, CRYPT32.LIB and USER32.LIB. Those developing\n+ non-interactive service applications might feel concerned about\n+ linking with GDI32.LIB and USER32.LIB, as they are justly associated\n+ with interactive desktop, which is not available to service\n+ processes. The toolkit is designed to detect in which context it's\n+ currently executed, GUI, console app or service, and act accordingly,\n+ namely whether or not to actually make GUI calls. Additionally those\n+ who wish to /DELAYLOAD:GDI32.DLL and /DELAYLOAD:USER32.DLL and\n+ actually keep them off service process should consider implementing\n+ and exporting from .exe image in question own _OPENSSL_isservice not\n+ relying on USER32.DLL. E.g., on Windows Vista and later you could:\n \n \t__declspec(dllexport) __cdecl BOOL _OPENSSL_isservice(void)\n \t{ DWORD sess;\n","s":{"c":1756843616,"u": 5041}} ],"g": 6509,"chitpc": 0,"ehitpc": 0,"indexed":0 , "ab": 0, "si": 0, "db":0, "di":0, "sat":0, "lfc": "0000"}