Home / user-163660

Jan Hadáček's questions

Martin Hope
Jan Hadáček
Asked: 2018-03-30 12:28:28 +0800 CST
  • 1

My client wants a simple storage accessible via SCP and SFTP. There will be two user accounts, one is read-only and the other is read-write.

For security reasons I want to dumb it down as much as possible:

  1. I want the user to be restricted to their home directory without a way to get out
  2. User's root directory must remain writable. SSH's internal-sftp with chroot unfortunately fails this one
  3. I don't want to allow any access to a normal shell
  4. I don't want users to be able to mess with permissions/owners of the files

So far I have implemented SFTP using SSH + MySecureShell, it works and it seems pretty bulletproof. However, SCP does not work, which was one of the requirements of my client.

  1. Is there any way to make SCP work with MySecureShell? Or some other shell?
  2. If not, is there some way to use sftp from a command line like you would scp? I mean, not interactively and using syntax as close to SCP as possible.
linux
Martin Hope
Jan Hadáček
Asked: 2016-03-30 13:25:06 +0800 CST
  • 0

I'm trying to configure my server to automatically insert a tracking code (Piwik) to all pages served. I'm using both static sites and some PHP sites. I've used the following method found on Piwik forums, which is based on mod_filter and replacements.

AddOutputFilterByType SUBSTITUTE text/html application/x-httpd-php
Substitute "s~</body>~...PIWIK CODE...</body>~ni"

However, it only works for plain HTML pages. I've tried various MIMEs for PHP, like text/php or application/x-httpd-php5, but no avail. The PHP page never gets modified by the filter, while there are no problems with HTML page.

I'm starting to think that perhaps mod_php is somehow by-passing mod_filter replacements?

apache-2.4
Martin Hope
Jan Hadáček
Asked: 2013-03-09 13:15:28 +0800 CST
  • 1

I'm using Apache + PHP 5.3.3-7 on Debian Squeeze, installed from the repositories. The PHP distribution in Debian Squeeze includes Suhosin patch. I have problems uploading files bigger than cca 4 MB, some invisible limit prevents the PHP from accepting the upload.

In php.ini I have:

  1. set upload_max_filesize = 50M
  2. set post_max_size = 50M
  3. set memory_limit = 256M
  4. set max_execution_time = 120
  5. set max_input_time = 120

In suhosin.ini:

  1. suhosin.memory_limit = 256M
  2. suhosin.post.max_value_length = 50000000
  3. suhosin.request.max_value_length = 50000000
  4. suhosin.post.max_vars = 200000
  5. suhosin.request.max_vars = 200000

I actually doubt the last two ones are important at all, but I was adviced to increase them as well.

I know for sure that PHP actually loads the config values correctly, since phpinfo() matches my expectations. I'm expecting to be able to upload a file up to 50MB, but uploading of 4MB already fails. There are no logged errors in normal PHP per-site logs. And I'm sure there is enough space is available to save the uploaded file.

It seems like there is some other invisible limit preventing me from uploading the files. What could this be? Perhaps the Apache itself? Never heard of this limit though.

I spent nearly one week on this and I'm desperate, as well as my customer. Any hints are welcome.

apache-2.2