Hot answers tagged

8

One option is to change the network adaptor of the virtual machine to bridged mode; you should then be able to access the virtual server from the other machines on the network, by providing your guest's IP address. Edit: For practical aspects, look at the VirtualBox documentation on Virtual networking. Your options are to use bridged networking With ...


4

Finally, here is the ultimate "secret sauce": Pass the SSL Labs Test on Lighttpd (Mitigate the CRIME and BEAST attack, Disable SSLv2 and Enable Perfect Forward Secrecy). Please read the link for concrete configuration directives.


3

For a general approach/tutorial on how to build the right cipher suite config you might like to have a look here: http://www.skytale.net/blog/archives/22-SSL-cipher-setting.html However, the author did not seem to pay attention to implementing DHE cipher suites; you will need these DHE ciphers in order to allow Forward Secrecy (FS) for your SSL connection. ...


3

Yes, it's possible to download the entire repository contents (including history) – a simple git clone would do it. However, this assumes someone knew about the existence of that .git directory...it's more likely that nobody has even noticed it. You can always check your web server's logs to be sure.


2

2 options: put something like this into your lighttpd.conf: server.port = 8000 launch lighttpd with admin-rights via sudo: $> sudo lighttpd -f lighttpd.conf -D Also read the lighthttpd configuration tutorial.


2

A simple git clone on the document root is not entirely accurate. Cloning an exposed GIT repository is not possible with "dumb" servers, such as an accidental exposure of .git via HTTP, unless git update-server-info is executed on the server. While some of the metadata is available, obtaining the contents of the .git/objects directory (aka the juicy stuff) ...


2

Make each user's files readable by their usergroup, and then add lighttpd to each user's usergroup. If we have bob and charlie, and lighttpd is running as www-data: # Bob and Charlie own their public_html folders # And cannot see each others' files chown bob:bob /home/bob/public_html chmod 770 /home/bob/public_html chown charlie:charlie /home/charlie/...


2

I retrieved the doc of lighttpd's mod_alias module. I bet you have a problem with the trailing slashes. Be sure that all alias entries end with a slash: alias.url = ( "/acruz/" => "/var/www/localhost/htdocs/acruz/", "/jvangemeren/" => "/var/www/localhost/htdocs/jvangemeren/", "/doceno/" => "/var/www/localhost/htdocs/doceno/" ) ...


2

Use lighttpd -p -f /etc/lighttpd/lighttpd.conf to see how lighty sees your config after += evaluation.


2

The configuration looks correct, and the other services already set up are apparently working correctly. After discussing the problem with the questioner, we tested setting the router to map the HTML port 80 on the web server to a different external port, and this works. It seems that the ISP is discouraging web servers by blocking port 80, and this is why ...


1

It is unusual to get a "Permission denied" message when running a command using sudo. I might check that SELinux isn't installed/enabled. The usual reason a network service fails to bind to a port is because the TCP port is already in use by some other service. The usual way to check this is $ sudo netstat -plnt Active Internet connections (only servers) ...


1

I don't have a lot of experience with lighttpd itself, but from the semantics of the config file, it seems to me, that if you have a connection coming in on port 443, it will redirect to port 443 regardless if you specify http:// in the URL or not. If I understand correctly and you want to redirect to port 80, you need to specify it explicitly in the ...


1

Yes. Ofcourse it is possible. Just define a redirect. This Doc will help you to do that http://redmine.lighttpd.net/projects/1/wiki/Docs_ModRewrite


1

Well, it was the bin-path setting that I was getting hung up on. My application resides now at: /var/www/localhost/cgi-bin/tiny.fcgi The socket is created at: /var/run/lighttpd/tiny.socket-1 (the '-1' is created by spawn-fcgi, and it's chmod'd so lighttpd can r/w to it) The mod_fcgi.conf file: server.modules += ("mod_fastcgi") fastcgi.debug = 1 ...


1

Looks like an SELinux issue. You could temporarily disable SELinux and test this theory. Try executing on the command line sudo echo 0 >/selinux/enforce and then restart lighttpd. See if it works. If it doesn't work, it isn't an SELinux issue. Reboot the machine to re-enable SELinux or execute: sudo echo 1 >/selinux/enforce If it does fix it, you ...


1

Ok, I have solved this, after few hours of digging in the Internet. The problem was my IM communicator spik which was listening on port 80. After turning it off and rebooting the machine everything works like charm :) I have read that one might have the same issue with e.g. Skype.


1

The init script probably contains the location and name of the config file. It might not be exactly lighttpd.conf, and if not a find won't succeed. Look for a file in /etc/init.d/ that is named something like lighttpd. It should contain a statement like DAEMON_ARGS="-f /etc/lighttpd.conf" which contains the file you're searching for.


1

$SERVER["socket"] == ":443" { ssl.engine = "enable" ssl.pemfile = "/path/to/pem/file/unknown.pem" } $SERVER["socket"] == ":80" { $HTTP["host"] =~ "(.*)" { url.redirect = ( "^/(.*)" => "https://%1/$1" ) } } solved it for me.


1

What I do in this situation is have a small one-page site available through HTTP that contains a single page with a meta refresh tag and possibly an explanation for browsers that have redirects disabled or unsupported for some reason. Create a custom 404 error page that also does the same thing. The meta tag should then redirect to https://127.0.0.1 or ...


1

In Apache you can define patterns (similar to mod_cgi) which designate requests sent to FastCGI applications. Mod_fcgid is a FastCGI process manager, spawning each unique application with a specific permissions (suexec). This is not possible with lighttpd. Lighttpd does not have a FastCGI process manager, which can change permissions, built-in (which is ...


1

The simplest alternative is not to run a web server at all. This generally makes little difference in the browser, compared to returning an empty page. Otherwise, lightweight web servers available through MacPorts include Abyss, Cheetah, Lighttpd, LWS, Mathopd, Mongoose, Monkeyd, Pico Server, Webfs, … It's hard to give a specific recommendation since you ...



Only top voted, non community-wiki answers of a minimum length are eligible