Re: Problem with creating home directories when creating users using pw under 5.2.1 Release i386
On Thu, Nov 25, 2004 at 03:37:24PM +0100, Olaf Greve wrote: pw useradd testusr -g testgrp -s /bin/sh No home directory gets created Give pw the -m option to instruct it to mkdir the home directory. - D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /bin/rm: Argument list too long.
On Fri, Nov 19, 2004 at 09:58:40AM +0100, Mipam wrote: I tried to delete all files from a dir, however I got this message: /bin/rm: Argument list too long. You probably did rm *, and * expanded to too many files. One way is to simply remove the directory completely (rm -r /foo/bar), but this also removes all subdirectories. Other way would be to use find and xargs; in this example for only the files in one specific directory and no subdirectories (and no symlinks, that is): find /foo/bar -type f -maxdepth 1 | xargs rm -n100 ... where -n controls the number of arguments passed per one execution of rm. HTH, - D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Transferring system to a new hard drive
On Fri, Nov 05, 2004 at 09:13:25AM -0600, CHris Rich wrote: My original install of FreeBSD is on a 30 gig hard drive, I want to move it to an 80 gig I now have, but i don't want to have to reinstall everything since I've spent hours waiting for some ports to install. [...] If I do move it over will I have ot make new slices to take advantage of the bigger hard drive? What I usually do is: - install the new hd as second drive in the running system - partition/slice it as you like - newfs the new partitions - mount the whole structure somewhere, like * mount /dev/ad1s1a /mnt * mount /dev/ad1s1e /mnt/usr * mount /dev/ad1s1f /mnt/var etc. - go single user - cd / find all dirs except mnt, proc, tmp | cpio -padmuv /mnt - check /mnt/etc/fstab - write boot sector to ad1 - shutdown, replace old drive with new drive - done The find|cpio combination will copy your entire system 1:1 to the new hard disk and it's slice structure below /mnt. HTH, - D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GPL vs BSD Licence
On Mon, Oct 25, 2004 at 11:32:04PM -0700, Ted Mittelstaedt wrote: Because Juniper, for example [...] You do realize, don't you, that the interesting part of a Juniper is the microcode in their DSP routing engine. FreeBSD is only used to control the routing engine in a Juniper router, it isn't used AS the routing engine. Of course I do realize that. It was merely an example, apparently not the best one. It's their choice to do or don't, that's all I said. (For terminology: The i386 part with FreeBSD is the routing engine, the awesome hardware is the forwarding engine). And now I need to digest this Linksys + Zebra mixture... ;-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GPL vs BSD Licence
On Mon, Oct 25, 2004 at 09:44:36AM +0200, Philipp Huber wrote: But equally important is the ability to join back forks, when/if some group finds the right solution to a problem. And that's where the GPL comes in: you can really think of the whole license as nothing more than a requirement to be able to re-join a forked project from either side. i don't really get what the gpl or bsd license has to do with rejoining forks. why shouldn't bsd licensed projects be able to refork in case... Because Juniper, for example, are perfectly free to decide against making their changes to the (in this case) FreeBSD code available anyone at all. For them, that may be a positive thing, because they don't have to open their work for the competition. But this is exactly what the GPL is aiming to avoid. HTH, - D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Protecting SSH from brute force attacks
On Sun, Oct 10, 2004 at 04:45:26PM -0400, Matt Juszczak wrote: Isn't it hard (and sort of more insecure) to use the keys? Why that? Start an agent together with your login session, have it load the key(s) (after you've entered the holy passphrase(s), of course) and you're set to go. Simply 'ssh foo' and you're logged in. For instance, anyone who gets access to your home dir would be able to get the keys for all your servers True, but that's why they're protected by a passphrase (which is symmetric encryption, i.e. you can change it without having to tell your servers about it). I'm just kind of confused on how the keys could be much more secure than passwords. Well, a password works from everywhere and can be brute-forced. Or someone might get to know it via others means, hacking one of your target hosts for example (the password is sent over the wire when you log in!). If someone compromises a target host and you use public keys, the attacker only gains your public key. Which he can have. ;) OTOH your point is valid, of course. But when someone is in control of your machine, he might intercept your password anyway... - D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Protecting SSH from brute force attacks
Hi, On Thu, Oct 07, 2004 at 03:15:25PM -0700, Luke wrote: There are several script kiddies out there hitting my SSH server every day. Sometimes they attempt to brute-force their way in trying new logins every second or so for hours at a time. Given enough time, I fear they will eventually get in. Apart from what was already noted here it may be a good idea to not use PasswordAuthentication at all, you can disable it in the sshd_config. Personally preferred solution would be public key authentication, but there are other options as well. No passwords used - no passwords can be brute-forced. HTH, - D. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
