From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: acme.sh
Date: Wed, 07 Feb 2018 13:09:51 +0000 [thread overview]
Message-ID: <1518008991.27385.1.camel@ipfire.org> (raw)
In-Reply-To: <9523fc3701d1585091d18c9c945e2c72@web.de>
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
Hi,
On Tue, 2018-02-06 at 21:01 +0100, Marcel Lorenz wrote:
> Hi,
>
> after short testing installation of acme.sh.
>
> Log:
> [root(a)ipfire acme]# ./acme.sh --install
> [Tue Feb 6 20:37:20 CET 2018] It is recommended to install socat first.
> [Tue Feb 6 20:37:20 CET 2018] We use socat for standalone server if you
> use standalone mode.
> [Tue Feb 6 20:37:20 CET 2018] If you don't use standalone mode, just
> ignore this warning.
> [Tue Feb 6 20:37:20 CET 2018] Installing to /root/.acme.sh
> [Tue Feb 6 20:37:20 CET 2018] Installed to /root/.acme.sh/acme.sh
> [Tue Feb 6 20:37:20 CET 2018] Installing alias to '/root/.bashrc'
> [Tue Feb 6 20:37:20 CET 2018] OK, Close and reopen your terminal to
> start using acme.sh
> [Tue Feb 6 20:37:20 CET 2018] Installing cron job
> 2018-02-06 20:37:20 INFO listing root's fcrontab
> 2018-02-06 20:37:20 INFO listing root's fcrontab
> 2018-02-06 20:37:20 INFO installing file /tmp/fcr-jYUQke for user root
> /tmp/fcr-jYUQke:80: Mismatched quotes: skipping line.
> Modifications will be taken into account right now.
> [Tue Feb 6 20:37:20 CET 2018] Good, bash is found, so change the
> shebang to use bash as preferred.
> [Tue Feb 6 20:37:21 CET 2018] OK
>
> A package named socat is needed for working. I found this download
> location: http://www.dest-unreach.org/socat/download/
>
> From my side: After droppig PHP, no nice web applications more possible
> (roundcube, nextcloud, phpmyadmin).
> Sorry, i have no use for acme.sh on IPfire without PHP.
This is useful for the reverse proxies that we ship.
-Michael
> Best,
> Marcel
>
> Am 2018-02-06 20:01, schrieb Michael Tremer:
> > Hello,
> >
> > would anyone like to package acme.sh for IPFire 2?
> >
> > For some things it might make sense to generate a non-self-signed
> > certificate
> > and this is a simple shell script that should do the job.
> >
> > I haven't tested it if it runs, but it would be nice if someone could
> > do this,
> > package it and send patches.
> >
> > Best,
> > -Michael
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2018-02-07 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9523fc3701d1585091d18c9c945e2c72@web.de>
2018-02-07 13:09 ` Michael Tremer [this message]
2018-02-06 19:01 acme.sh Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1518008991.27385.1.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox