On Sat, Dec 22, 2018 at 02:07:06PM -0500, Offray Vladimir Luna Cárdenas wrote:
> In your setup, you talk about SmallCMS1 as a blog engine that runs on
> Pharo 6 and seems kind of integrated with Fossil. Brea [1] (in early
> stages now), pursuits similar goals. Do you have any link to SmallCMS1?
HI,
On 21/12/18 21:59, Pierce Ng wrote:
> See my recent blog post:
>
> https://www.samadhiweb.com/blog/2018.12.09.https.html
In your setup, you talk about SmallCMS1 as a blog engine that runs on
Pharo 6 and seems kind of integrated with Fossil. Brea [1] (in early
stages now), pursuits similar
Ignore this message. I got confused by my web browser. Everything is A-okay.
horrido wrote
> So you're saying that when users sign in with their passwords or otherwise
> enter sensitive data, they're protected by SSL, even though the web
> application is still operating through HTTP?
>
>
>
>
I noticed this in my post...
*server {
listen 80;
location / {
proxy_pass http://192.99.58.29:1701;
}
}
server {
listen 443;
ssl_certificate /etc/nginx/cert_chain.crt;
ssl_certificate_key /etc/nginx/cert.key;
ssl on;
location / {
proxy_pass
So you're saying that when users sign in with their passwords or otherwise
enter sensitive data, they're protected by SSL, even though the web
application is still operating through HTTP?
Sven Van Caekenberghe-2 wrote
>> On 22 Dec 2018, at 16:52, horrido
> horrido.hobbies@
> wrote:
>>
>> I
On Sat, 22 Dec 2018 at 23:57, horrido wrote:
>
> Why does the forum editor add those stupid anchor tags without permission???
I'm not clear what you are referring to. Which anchor tags?
cheers -ben
> On 22 Dec 2018, at 16:52, horrido wrote:
>
> I need help with one issue, though. Do I need to enable SSL in Pharo?
No
> After proxy pass, I only get HTTP.
That is the idea: the browser talks HTTPS to nginx which proxies to pharo in
HTTP.
Why does the forum editor add those stupid anchor tags without permission???
horrido wrote
> I've had tons of trouble trying to get Letsencrypt working. It was so
> frustrating that I decided to go with PositiveSSL from Comodo. It only
> cost
> me US$15.76 for two years, so I don't care about
I've had tons of trouble trying to get Letsencrypt working. It was so
frustrating that I decided to go with PositiveSSL from Comodo. It only cost
me US$15.76 for two years, so I don't care about price.
Letsencrypt's setup procedure is extremely arcane. For a noob like myself,
this is not good.
> On 22 Dec 2018, at 03:59, Pierce Ng wrote:
>
> See my recent blog post:
>
> https://www.samadhiweb.com/blog/2018.12.09.https.html
Wow, very well done, very well written, thank you.
On Fri, Dec 21, 2018 at 02:42:04PM -0600, horrido wrote:
> Okay, I will dispense with the self-signed certificate and purchase a
> commercial one, say, from Comodo (PositiveSSL).
Use Let's Encrypt-issued certificates, available without charge. Let's
Encrypt's CA certificate is built-in trusted by
On Sat, 22 Dec 2018 at 04:42, horrido wrote:
>
> Okay, I will dispense with the self-signed certificate and purchase a
> commercial one, say, from Comodo (PositiveSSL).
My web host uses "Lets Encrypt"
https://www.dreamhost.com/hosting/ssl-tls-certificates/
I haven't looked into it deeply, but
> On 21 Dec 2018, at 21:42, horrido wrote:
>
> Okay, I will dispense with the self-signed certificate and purchase a
> commercial one, say, from Comodo (PositiveSSL).
But you cannot buy a certificate for localhost, only for a real domain name
(that you host for real).
> I presume once I
Okay, I will dispense with the self-signed certificate and purchase a
commercial one, say, from Comodo (PositiveSSL).
I presume once I get it, the code below will work correctly (?). If not,
I'll be back.
Sven Van Caekenberghe-2 wrote
>> On 20 Dec 2018, at 22:09, horrido
> horrido.hobbies@
> On 21 Dec 2018, at 12:00, Sven Van Caekenberghe wrote:
>
> I just tried in Ubuntu 18.04.O1 LTS 64-bit, using Pharo 7 and FireFox, and it
> worked.
BTW, I made my certificate like this (on macOS):
prometheus:tmp sven$ mkdir ssl
prometheus:tmp sven$ cd ssl
prometheus:ssl sven$ openssl
> On 20 Dec 2018, at 22:09, horrido wrote:
>
> I had this working some many months ago, but now I can't get it to work.
> Really annoying. The entire process is so arcane...
>
> My HTTP server starts like this:
>
> Teapot stopAll.
> Teapot on
> Get: blah blah blah
>
> Then I visit
16 matches
Mail list logo
