I tried to go to your site, but apparently the server is down.
On 09/29/2014 07:16 PM, Benjamin Oppermann wrote:
> Actually, this one is a self-signed certificate, but I tried with a
> new one using your command, just to be safe.
> My Vhost is configured in /etc/apache2/sites-enabled/000-default.c
Actually, this one is a self-signed certificate, but I tried
with a new one using your command, just to be safe.
My Vhost is configured in
/etc/apache2/sites-enabled/000-default.conf, so that's where I
adjusted the path to test.pem
The page is still not available.
I was probably wrong though giv
Have you tried with a self signed certificate just to see what happens?
# openssl req -new -x509 -days 3650 -nodes -newkey rsa:4096 -out
/etc/ssl/certs/test.pem -keyout /etc/ssl/private/test.pem
# chmod go= /etc/ssl/private/test.pem
httpd.conf
SSLCertificateFile/etc/ssl/certs/test.pem
SSLCe
Ooops, my bad.
~$ sudo openssl rsa -in /etc/ssl/private/owncloud.key -check
RSA key ok
So the key file itself is not the problem...
Am Mo, 29. Sep 2014, um 22:15, schrieb Benjamin Oppermann:
So should I revoke the changes to permissions I made, or remove
permissions for my user, leaving
On 29 Sep 2014, at 19:41, Pete Houston wrote:
> It is not a flaw in apache. Apache is simply a network-enabled channel
> through which exploitative payloads may be delivered to unpatched
> installations of bash (one of many such channels).
Yep. mod_taint (or any other Apache-based solution) is
On Mon, September 29, 2014 14:50, Edgar Pettijohn wrote:
> When you go to your site from a browser are you getting the actual 403
> error page? Or are you just getting errors in the logs?
>
I get the 403 Forbidden error page.
--
*** E-Mail is NOT a SECURE channel ***
James B.
So should I revoke the changes to permissions I made, or remove
permissions for my user, leaving only root?
~$ openssl rsa -in /etc/ssl/private/owncloud.key -check
Error opening Private Key /etc/ssl/private/owncloud.key
139748944725664:error:0200100D:system library:fopen:Permission
denied:bss_
a private key should never be accesible to groups or others, just root as
read only.
Having said this... have you checked the key file is correct?
try this:
openssl rsa -in /etc/ssl/private/owncloud.key -check
2014-09-29 21:22 GMT+02:00 Benjamin Oppermann :
> Ok, I tried this. The permissions a
Ok, I tried this. The permissions are now:
~$ sudo ls -l /etc/ssl/private/owncloud.key
-rw-r--r-- 1 root ben 1704 Sep 28 04:01 /etc/ssl/private/owncloud.key
I still get the same error.
Regards Ben
Am Mo, 29. Sep 2014, um 14:12, schrieb Bremser, Kurt (AMOS Austria
GmbH):
> The first thing that I
When you go to your site from a browser are you getting the actual 403
error page? Or are you just getting errors in the logs?
On 09/29/2014 01:19 PM, James B. Byrne wrote:
> On Mon, September 29, 2014 13:57, Edgar Pettijohn wrote:
>> As a full disclaimer I don't use 2.4.9 so I set it up on a vir
On Mon, Sep 29, 2014 at 01:09:19PM -0500, Sharon Zastre wrote:
> Is it safe to assume that a fix/patch/upgrade will become available to
> address the shellshock vulnerability?
Yes, but not in apache. The vulnerability dubbed "shellshock" is a
flaw in bash and patches and upgrades are already wide
On Mon, September 29, 2014 13:57, Edgar Pettijohn wrote:
> As a full disclaimer I don't use 2.4.9 so I set it up on a virtual
> machine to test out. I am getting the same error apparently due to not
> having a favicon.ico. I'm willing to bet the situation is the same for
> you and that would be
I will admit that I am far from an advanced user of Apache. So for now I think
I will hold off on trying to create the module. Is it safe to assume that a
fix/patch/upgrade will become available to address the shellshock vulnerability?
Thanks,
Sharon
-Original Message-
From: Nick Kew
On 29 Sep 2014, at 17:35, Sharon Zastre wrote:
> Thank you Nick for quickly looking into a solution/work around for the
> shellshock vulnerability. But I'm confused as to how to implement it. I am
> currently at Apache 2.4.9 with OpenSSL 1.0.1g. Do I need to upgrade to
> 2.4.10 or 2.5(?) fi
As a full disclaimer I don't use 2.4.9 so I set it up on a virtual
machine to test out. I am getting the same error apparently due to not
having a favicon.ico. I'm willing to bet the situation is the same for
you and that would be where I would start to correct the error or just
disregard it.
On
Thank you Nick for quickly looking into a solution/work around for the
shellshock vulnerability. But I'm confused as to how to implement it. I am
currently at Apache 2.4.9 with OpenSSL 1.0.1g. Do I need to upgrade to 2.4.10
or 2.5(?) first? Will it simply be in the install and I include mod_
On Mon, September 29, 2014 07:00, Edgar Pettijohn wrote:
> The problem is most likely in the config somewhere, but we will never
> know if you don't post the entire httpd.conf.
>
Here is a diff between the active and the original (as distributed with the
source tarball) httpd.conf for httpd-2.4.9
The first thing that I'd try is
sudo chmod go+r /etc/ssl/private/owncloud.key
Kurt Bremser
AMOS Austria
Newton was wrong. There is no gravity. The Earth sucks.
Von: Benjamin Oppermann [ben@eml.cc]
Gesendet: Montag, 29. September 2014 13:31
An: users@ht
Hi,
I can't reach my website, I get a "corrupted content" error message in
the browser.
Looking into apache (version 2.4.7 on Ubuntu 14.04), I get
~$ apachectl -S
AH00526: Syntax error on line 22 of
/etc/apache2/sites-enabled/000-default.conf:
SSLCertificateKeyFile: file '/etc/ssl/priv
The problem is most likely in the config somewhere, but we will never
know if you don't post the entire httpd.conf.
On 09/28/2014 10:43 PM, James B. Byrne wrote:
> On Fri, September 26, 2014 21:28, Edgar Pettijohn wrote:
>> Try:
>> |
>> AllowOverride none
>> Require all denied
>>
>> ||
>>
Hi, I am Bae (from Japan).
(apache Version: 2.0.64)
I installed the mod_dumpio, and getting request and reponse information
from error.log.
But in case of "GIF"(image) file, output chars are missing.
(Example) test.gif
①[binary] ...d8 ff e0 00 10 4a 46 49 46 00 01 01 01 00 48 00...
②[dumpio_out]
21 matches
Mail list logo