Search results

Openwall TCB is an implementation of SGID-only passwd. You need the group to access /etc/tcb, but your actual password is writable by you. It stops the user randomly editing the file, and limits any flaws in passwd to letting you mess with your password. They have the same concept for their...

Some of these points may just be my preferences, but: You don't need to roll your own argument parsing, use getopt Your code would have more clarity if you explicitly list conditions, rather than using C's integer true/false semantics. Similarly with errexit(), see errx Another clarity...

Sorry for the misunderstanding, the -u option is to ftpd. I edited my reply, and it no longer included that clarification.

There is one note that may be of use to you: the -u option. It allows you to make a file creation umask, and thus you could set it do that these files are unreadable. By default, anonymous users cannot modify existing files, so this should be adequate. For clarity, sanity, and cleanliness, I...

No, the tutorial does not address the problem mentioned, in as far as I can see. Allow me to paraphrase the quote: Does that help? Essentially, it means reviewing the file, and not the user.

What was the error when you compiled with just, <stdio.h>?

If I understand your question, then the answer is because execl never returns (unless in error, see the man page). The code between the execl and the next case statement is not run, assuming the called program can be executed. Therefore, your call to signal never happens, and, thus, your...

Hi, glad you are enjoying FreeBSD. cc is exactly the same program as gcc, currently. The name cc just means C compiler, and is where you would expect the C compiler under a Unix-like system. gcc is a specific implementation of the C compiler (and a bit more, but there is no need to worry...

Well, what you want is actually much simpler than I interpreted. If all you want is for users to be unable to view a certain directory, then you just need a couple of tips about how directory permissions work. The first problem you are probably running into is that /home on FreeBSD is, in...

May I ask, is it your intent that these users cannot affect your host system? If so, do you mind if they would, possibly, be able to affect each other? Given that you want to protect your host system, but are fine with the users, possibly, affecting each other, I would recommend you create a...

I would like to thank ChuckOp for his very informative posts. I would also commend him on the manner in which he acts, given some of the other posters in this thread. That he includes opinions is not a problem, as you are free to form your own opinions. I do not think the aggressive, and...

From userland you should look at sysctl(3), from the kernel check out http://fxr.watson.org/fxr/source/sys/sysctl.h. With the caveat that it might not actually be the value you want.

I know the issue has already been approached, but I had a client have a lot of problems with memory when using Wordpress. The easiest solution for that situation was to put a caching nginx in front of apache/Wordpress. If you can be bothered with fiddling, Varnish is pretty amazing (and by phk...

http://marc.info/?l=freebsd-stable&m=133312935416326&w=4 If you can skip by the Gentoo developer's miscomprehensions, there is actually some explanation of how kernel memory layout works. However, you may actually be looking for user land ASLR. If that is the case, I don't believe that it...

This is not really true. There is not a significant benefit to logging in as a user, and using programs to escalate privileges. The problem becomes one of root equivalency. Indeed, the only consideration is that "root" is a known account name, if you were using password authentication. If a...

Dirty Sed Okay, this appears to work, though it is an example of how ugly sed is in the wrong hands. I do not think it is particularly resilient. Especially, it will only work for documents the way you described, with no variation. That said, I used the following a test...