Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Help with apache2
« Reply #15, on June 1st, 2012, 02:13 PM »
That's a good plan, I like that :)
When we unite against a common enemy that attacks our ethos, it nurtures group solidarity. Trolls are sensational, yes, but we keep everyone honest. | Game Memorial

Dragooon

  • I can code! Really!
  • polygon.com has to be one of the best sites I've seen recently.
  • Posts: 1,841
Re: Help with apache2
« Reply #16, on June 1st, 2012, 02:17 PM »
Yeah it works fairly well, although it does lock Package manager and the likes out by default, but that should be the case anyway.
The way it's meant to be

Arantor

  • As powerful as possible, as complex as necessary.
  • Posts: 14,278
Re: Help with apache2
« Reply #17, on June 1st, 2012, 02:18 PM »
Sadly if only people were happy with that, people love having one-click updates to things...

Dragooon

  • I can code! Really!
  • polygon.com has to be one of the best sites I've seen recently.
  • Posts: 1,841
Re: Help with apache2
« Reply #18, on June 1st, 2012, 02:20 PM »
Quote from Arantor on June 1st, 2012, 02:18 PM
Sadly if only people were happy with that, people love having one-click updates to things...
Until one day a creep comes in and bombs their forum into oblivion...:P

MultiformeIngegno

  • Posts: 1,337
Re: Help with apache2
« Reply #19, on June 1st, 2012, 02:20 PM »
I remember a topic on Mantis about Suhosin + SMF auth. Nao lost days on that..... :^^;:
Re: Help with apache2
« Reply #22, on June 1st, 2012, 09:14 PM »
Uhm.. I need a little help with users permissions I think.
Here's the content of the /etc/vsftpd.conf file:
Code: [Select]
# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone?  vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=YES
#
# Run standalone with IPv6?
# Like the listen parameter, except vsftpd will listen on an IPv6 socket
# instead of an IPv4 one. This parameter and the listen parameter are mutually
# exclusive.
#listen_ipv6=YES
#
# Allow anonymous FTP? (Beware - allowed by default if you comment this out).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in  your  local  time  zone.  The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
#connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
ftpd_banner=Welcome to our FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may restrict local users to their home directories.  See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
chroot_list_enable=YES
# (default follows)
chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# Customization
#
# Some of vsftpd's settings don't fit the filesystem layout by
# default.
#
# This option should be the name of a directory which is empty.  Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/private/vsftpd.pem

listen_port=21

And I have a vsftpd.chroot_list file with a list (well.. just one) of users with the perms to use ftp (as far as I understood). Just the name of the users.

To create the user whom name is in the vsftpd.chroot_list file I used the command:
useradd -d /home/www USERNAME

Then:
chown USERNAME /home/www/

and finally:
passwd USERNAME

When I try to connect via FTP using the credentials of this username I manage to connect!
The problems are:
1) I can access not only the dir /home/www/ but also parent dirs!
2) User doesn't have write perms..


EDIT: Of course I restarted the vsftpd process.

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Help with apache2
« Reply #23, on June 1st, 2012, 09:31 PM »
I don't remember that suhosin thing?

URL tags are parsed because of the Aeva rewrite I guess.
Uh... So many things to fix.

MultiformeIngegno

  • Posts: 1,337

Nao

  • Dadman with a boy
  • Posts: 16,082
Re: Help with apache2
« Reply #25, on June 1st, 2012, 09:35 PM »
Did you edit that post to have it crash like that? Before you fixed it...

MultiformeIngegno

  • Posts: 1,337
Re: Help with apache2
« Reply #26, on June 1st, 2012, 09:39 PM »
Quote from Nao on June 1st, 2012, 09:35 PM
Did you edit that post to have it crash like that? Before you fixed it...
Which post? The one above yours containing the link to SMF?
I first posted the link with a smiley, than edited it changing smiley. URL tags brake and I had to edit it again replacing the URL with the right one.
Re: Help with apache2
« Reply #27, on June 1st, 2012, 09:58 PM »
Ok, solved the problem of the write perms. I had to chown -R /home/www/ (all subfolders..), not just chown /home/www/ :)
Re: Help with apache2
« Reply #28, on June 2nd, 2012, 05:42 PM »
Stupid stupid stupid question... :blush:
To make the PHP mail() function work do I need a SMTP server installed or something..? If yes can you suggest one? :)

Dragooon

  • I can code! Really!
  • polygon.com has to be one of the best sites I've seen recently.
  • Posts: 1,841
Re: Help with apache2
« Reply #29, on June 2nd, 2012, 05:50 PM »
Quote from MultiformeIngegno on June 2nd, 2012, 05:42 PM
Stupid stupid stupid question... :blush:
To make the PHP mail() function work do I need a SMTP server installed or something..? If yes can you suggest one? :)
If you only need send and not receive, you can do a basic installation of Exim and be done in 5 minutes.