Re: [WebDNA] WebDNA and macOS 10.4 Mojave - Operational?
This WebDNA talk-list message is from 2018
It keeps the original formatting.
numero = 114420
interpreted = N
texte = 2039 Somes news about this subject. The problem comes from Mojave that does not let unsigned applications = running, since none of our binaries are signed with a developer = certificate. Seems Mojave is more strict about this, probably to stop = malware. Furthermore, signing with our name will NOT help. The issue isn't just = that the library isn't signed. With "Library Validation" enabled, the library has to be signed by the = same developer that made the application. "Plug-ins or frameworks signed = by other developers" cannot be loaded. So if we want to run our own = module with the Apache that comes with OSX, Apple has to sign the module = themselves. Obviously that will never happen. Seems like disabling SIP or installing another separate copy of Apache = are the only options. To disable SIP, boot in the recovery OS, open a terminal, and run: csrutil disable Also, I guess lighttpd comes with its own fastcgi support included, and = it should work fine if you want to run lighttpd with WebDNA. (The built-in OSX Apache does not include a fastcgi/fcgid module, and = thats why we provide one.) - chris > On Oct 5, 2018, at 20:24, Patrick McCormick
= wrote: >=20 > Mojave is far less important than getting a docker image running. >=20 > While I understand that it is nice to have a local version running = under Mojave, wasting time building for any system dependent on a GUI = misses the entire idea of how the internet works today - particularly = with the rise of cloud computing. >=20 > Not only can you already run docker images and containers in Mojave, = those same containers and images can be immediately deployed into any = scalable cloud hosting environment. Why on Earth would it be important = to build a version that runs within a single, individual, GUI = environment? >=20 > This has been the Achilles Heel of WebDNA for the past 10 years. >=20 >=20 >=20 >> On Oct 4, 2018, at 2:21 AM, Michael Davis = wrote: >>=20 >> Chris, >>=20 >> Possible to have you recompile fastcgi.so for Mojave? >>=20 >>=20 >> MD >>=20 >>> On Oct 1, 2018, at 10:27 AM, Michael Davis = wrote: >>>=20 >>> My experience thus far is that the version of fastcgi.so is no = longer compatible with Mojave. So for the fcgi version, we're needing a = newly compiled fastcgi.so. I grabbed the source but haven't had time to = compile it yet. On the server version, I did try to run the High Sierra = installer, but after it ran there was still no active .dna parsing. So = there's something to look into there as well. Apple does the obligatory = backup of old Apache configs when upgrading, so remember to flip your = conf files back to the .orig versions. >>>=20 >>>=20 >>>=20 >>> Mike >>>=20 >>>=20 >>>=20 >>>> On Oct 1, 2018, at 6:54 AM, christophe.billiottet@webdna.us wrote: >>>>=20 >>>> Hi Palle! no, there is no experience yet with Mojave, but my guess = is there will be no problem. Both versions of WebDNA just need standard = apache. The only thing is Apple sometimes change the way apache runs = under OSX, so in the worst case, we will have to change the installer = that was working with the two last versions. But WebDNA will work fine = at the end. >>>>=20 >>>> If you have a production server, it is not advisable to jump on the = new releases. Wait a little. >>>>=20 >>>> - chris >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>> On Oct 1, 2018, at 16:24, Palle Bo Nielsen = wrote: >>>>>=20 >>>>> No experience, macOS 10.14 Mojave and WebDNA? >>>>>=20 >>>>> /Palle --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
2039 Somes news about this subject. The problem comes from Mojave that does not let unsigned applications = running, since none of our binaries are signed with a developer = certificate. Seems Mojave is more strict about this, probably to stop = malware. Furthermore, signing with our name will NOT help. The issue isn't just = that the library isn't signed. With "Library Validation" enabled, the library has to be signed by the = same developer that made the application. "Plug-ins or frameworks signed = by other developers" cannot be loaded. So if we want to run our own = module with the Apache that comes with OSX, Apple has to sign the module = themselves. Obviously that will never happen. Seems like disabling SIP or installing another separate copy of Apache = are the only options. To disable SIP, boot in the recovery OS, open a terminal, and run: csrutil disable Also, I guess lighttpd comes with its own fastcgi support included, and = it should work fine if you want to run lighttpd with WebDNA. (The built-in OSX Apache does not include a fastcgi/fcgid module, and = thats why we provide one.) - chris > On Oct 5, 2018, at 20:24, Patrick McCormick = wrote: >=20 > Mojave is far less important than getting a docker image running. >=20 > While I understand that it is nice to have a local version running = under Mojave, wasting time building for any system dependent on a GUI = misses the entire idea of how the internet works today - particularly = with the rise of cloud computing. >=20 > Not only can you already run docker images and containers in Mojave, = those same containers and images can be immediately deployed into any = scalable cloud hosting environment. Why on Earth would it be important = to build a version that runs within a single, individual, GUI = environment? >=20 > This has been the Achilles Heel of WebDNA for the past 10 years. >=20 >=20 >=20 >> On Oct 4, 2018, at 2:21 AM, Michael Davis = wrote: >>=20 >> Chris, >>=20 >> Possible to have you recompile fastcgi.so for Mojave? >>=20 >>=20 >> MD >>=20 >>> On Oct 1, 2018, at 10:27 AM, Michael Davis = wrote: >>>=20 >>> My experience thus far is that the version of fastcgi.so is no = longer compatible with Mojave. So for the fcgi version, we're needing a = newly compiled fastcgi.so. I grabbed the source but haven't had time to = compile it yet. On the server version, I did try to run the High Sierra = installer, but after it ran there was still no active .dna parsing. So = there's something to look into there as well. Apple does the obligatory = backup of old Apache configs when upgrading, so remember to flip your = conf files back to the .orig versions. >>>=20 >>>=20 >>>=20 >>> Mike >>>=20 >>>=20 >>>=20 >>>> On Oct 1, 2018, at 6:54 AM, christophe.billiottet@webdna.us wrote: >>>>=20 >>>> Hi Palle! no, there is no experience yet with Mojave, but my guess = is there will be no problem. Both versions of WebDNA just need standard = apache. The only thing is Apple sometimes change the way apache runs = under OSX, so in the worst case, we will have to change the installer = that was working with the two last versions. But WebDNA will work fine = at the end. >>>>=20 >>>> If you have a production server, it is not advisable to jump on the = new releases. Wait a little. >>>>=20 >>>> - chris >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>=20 >>>>> On Oct 1, 2018, at 16:24, Palle Bo Nielsen = wrote: >>>>>=20 >>>>> No experience, macOS 10.14 Mojave and WebDNA? >>>>>=20 >>>>> /Palle --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list talk@webdna.us To unsubscribe, E-mail to: talk-leave@webdna.us archives: http://www.webdna.us/page.dna?numero=3D55 Bug Reporting: support@webdna.us .
christophe.billiottet@webdna.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Hiding HTML and page breaks (1997)
is [Bankres] an internal webcat variable? (1999)
New iMac, now ... how do I make webdna serve .html files? (2005)
WebCat2 - Getting to the browser's username/password data (1997)
SiteEdit Pro Update Announcement (1997)
WebCatalog for Postcards ? (1997)
Smart caching problems with 2.1b3? (1997)
Cart Creation (1998)
unable to launch acgi in WebCat (1997)
Opinion: [input] should be called [output] ... (1997)
Use of & in text areas.... (1998)
Editing the search string (1997)
RAM variables (1997)
[isfile] ? (1997)
Templates on Unix & CGI on Mac? (1997)
Today's suggestions (1998)
Calculating multiple shipping... (1997)
b12 cannot limit records returned and more. (1997)
Caching [include] files ... (1997)
[subtotal] and others (1997)