RE: ext3 filesystem and file name restrictions
After reading the comments here: http://www.macosxhints.com/article.php?story=20031114045400715 I think the behaviour has been changed in Mac OS X, but the userspace tools seem to handle it inconsistently. Also see http://en.wikipedia.org/wiki/Filename#Reserved_characters_and_words. > -Original Message- > From: Adam Hardy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 15, 2008 12:37 PM > To: debian-user@lists.debian.org > Cc: List Debian User > Subject: Re: ext3 filesystem and file name restrictions > > Tammo Schuelke on 15/10/08 11:15, wrote: > >> -Original Message- From: Adam Hardy > >> [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2008 > >> 12:05 PM To: List Debian User Subject: ext3 filesystem and file name > >> restrictions > >> > >> Hi, > >> > >> I created a samba share on one of my debian boxes with a ext3 file system > >> and unfortunately I can't write files with certain file names from Mac OSX. > >> > >> > >> > >> This disrupts the back-up process which takes about an hour every time to > >> fail when I want to try it out again. > >> > >> For instance, there is one file name like this: > >> > >> 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp > >> > >> which has a colon in it that I guess is the problem. > >> > >> After finding out all I could about Mac file systems and names, my > >> conclusion is that macs are pretty special, especially their file systems. > >> > >> Is there a basis for the file name restrictions on ext3, i.e. can I say, > >> well ext3 is based on a standard, so I'm going to restrict the file names > >> on macs, otherwise they won't be backed up? > > > > Have you tried creating a file with a colon in its name by hand? I just > > tested it, both ext3 and samba don't have a problem with it (only Windows > > clients don't like it). With which error message does it fail? > > > Blast! I thought I was being clever and because I didn't want to confuse the > issue, I actually changed that file name above. Originally the dialog box > error > message on the mac had a slash instead of a colon: > > 2AE2EAEE-57AC-46D8-B619-C2167D4C6786/ABPerson.abcdp > > I thought, uh-huh, let's find it then - but when I searched for it, all I > found > was the name with the colon, so I figured that must be the problem file and > that > the error handling had somehow 'escaped' the colon into a slash. > > So I can only assume that there was some sort of temporary file with the slash > in it then, which disappeared. > > Yet I do seem to have a file name with a colon in it, despite that link from > XvsXP. Here's the output from find: > > > Last login: Wed Oct 15 10:03:23 on console > Welcome to Darwin! > sylvie-computer:~ sylvie$ find . -name *ABPerson* > ./Library/Application Support/AddressBook/.skIndex.ABPerson.lockN > ./Library/Application Support/AddressBook/ABPerson.skIndexInverted > ./Library/Application Support/Quicksilver/PlugIns/iChat > Module.qsplugin/Contents/Resources/ABPerson-Fez.h > ./Library/Caches/com.apple.AddressBook/MetaData/2AE2EAEE-57AC-46D8-B619- > C2167D4C6786:ABPerson.abcdp > ./Library/Caches/com.apple.AddressBook/MetaData/4B1A764D-C182-4200-88DB- > 0686716AAB89:ABPerson.abcdp > sylvie-computer:~ sylvie$ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: ext3 filesystem and file name restrictions
Have you tried creating a file with a colon in its name by hand? I just tested it, both ext3 and samba don't have a problem with it (only Windows clients don't like it). With which error message does it fail? Tammo > -Original Message- > From: Adam Hardy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 15, 2008 12:05 PM > To: List Debian User > Subject: ext3 filesystem and file name restrictions > > Hi, > > I created a samba share on one of my debian boxes with a ext3 file system and > unfortunately I can't write files with certain file names from Mac OSX. > > This disrupts the back-up process which takes about an hour every time to fail > when I want to try it out again. > > For instance, there is one file name like this: > > 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp > > which has a colon in it that I guess is the problem. > > After finding out all I could about Mac file systems and names, my conclusion > is > that macs are pretty special, especially their file systems. > > Is there a basis for the file name restrictions on ext3, i.e. can I say, well > ext3 is based on a standard, so I'm going to restrict the file names on macs, > otherwise they won't be backed up? > > > Thanks > Adam > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: ext3 filesystem and file name restrictions
PS: the file with a colon in its name comes from a Mac? From what I just read, the Mac OS FS (HFS+) doesn't support colons in filenames. http://www.xvsxp.com/files/forbidden.php Tammo > -Original Message- > From: Adam Hardy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 15, 2008 12:05 PM > To: List Debian User > Subject: ext3 filesystem and file name restrictions > > Hi, > > I created a samba share on one of my debian boxes with a ext3 file system and > unfortunately I can't write files with certain file names from Mac OSX. > > This disrupts the back-up process which takes about an hour every time to fail > when I want to try it out again. > > For instance, there is one file name like this: > > 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp > > which has a colon in it that I guess is the problem. > > After finding out all I could about Mac file systems and names, my conclusion > is > that macs are pretty special, especially their file systems. > > Is there a basis for the file name restrictions on ext3, i.e. can I say, well > ext3 is based on a standard, so I'm going to restrict the file names on macs, > otherwise they won't be backed up? > > > Thanks > Adam > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: ext3 filesystem and file name restrictions
Have you tried creating a file with a colon in its name by hand? I just tested it, both ext3 and samba don't have a problem with it (only Windows clients don't like it). With which error message does it fail? Tammo > -Original Message- > From: Adam Hardy [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 15, 2008 12:05 PM > To: List Debian User > Subject: ext3 filesystem and file name restrictions > > Hi, > > I created a samba share on one of my debian boxes with a ext3 file system and > unfortunately I can't write files with certain file names from Mac OSX. > > This disrupts the back-up process which takes about an hour every time to fail > when I want to try it out again. > > For instance, there is one file name like this: > > 2AE2EAEE-57AC-46D8-B619-C2167D4C6786:ABPerson.abcdp > > which has a colon in it that I guess is the problem. > > After finding out all I could about Mac file systems and names, my conclusion > is > that macs are pretty special, especially their file systems. > > Is there a basis for the file name restrictions on ext3, i.e. can I say, well > ext3 is based on a standard, so I'm going to restrict the file names on macs, > otherwise they won't be backed up? > > > Thanks > Adam > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: MRT HOW TO?
I think you're confusing MRT (Multi-Threaded Routing Toolkit) and MRTG (Multi-Router Traffic Grapher). > -Original Message- > From: Clifford W. Hansen [mailto:[EMAIL PROTECTED] > Sent: Wednesday, September 10, 2008 11:35 AM > To: debian-user@lists.debian.org > Cc: [EMAIL PROTECTED] > Subject: Re: MRT HOW TO? > > On Monday 08 September 2008 06:53:24 GI_Mike - Herman von Mandel wrote: > > Greetings to the list! > > > > Does anybody have access to a good MRT (Multi-Threaded Routing Toolkit) > HOW > > TO? I have searched the web and the debian.org pages (as well as merit.edu > > - apparently the original maintainer) but I can't find a HOW TO or man/info > > page anywhere. > > > > Thanks! > > This has from what I've read and started looking at been replaced by rrdtool. > (if I am wrong please correct me). > > This will probably help with finding a good tutorial. > > I'm still trying to wade through a couple, but mainly: > apt-get install rrdtool > man rrdtool > > I think that will help the most for now... > > HTH > -- > Thank you, > > Clifford W. Hansen > PHP Developer / Linux Administrator > > (Cell)+27 82 883 8677 > (Fax) +27 86 503 0634 > (E-Mail) [EMAIL PROTECTED] > (MSN) [EMAIL PROTECTED] > (GPG) 0x936D6C19 > > "We have seen strange things today!" > > () ascii ribbon campaign - against html e-mail > /\ www.asciiribbon.org - against proprietary attachments -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: apache2 in Debian - adding vhost - which file to edit?
Addendum: the symlinks can be easily created/removed using the commands a2ensite and a2dissite, respectively. I usually forget they exist and do it by hand though =) From:Cassiel [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2008 10:51 AM To: Debian User List Subject: Re: apache2 in Debian - adding vhost - which file to edit? 2008/9/9 Zach Uram < [EMAIL PROTECTED] > I am trying to add a name based virtual host to apache2-mpm-prefork version 2.2.9-7 on Debian lenny/sid. First I read to edit /etc/apache2/httpd.conf but this file it seems is empty and not used in Debian. Then I read to edit /etc/apache2/apache2.conf but it seems that is also not the right place for adding it so then I found the file /etc/apache2/sites-enabled/000-default This is the correct file to edit? I was told to add my section to it such as: . yes, but 000-default file should be left alone with standard directives for your DocRoot /var/www/ then you should put directives for any other web site you are going to add in a separate file in /etc/apache2/sites-available/ and then create a symlink to it in /etc/apache2/sites-enabled/ so you can simply remove the symlink if you ever want to put sites offline instead of commenting out lines on a single, maybe huge, conf file, moreover you gain better control on per site directives (before going online) http://httpd.apache.org/docs/2.2/ regards
RE: apache2 in Debian - adding vhost - which file to edit?
Addendum: the symlinks can be easily created/removed using the commands a2ensite and a2dissite, respectively. I usually forget they exist and do it by hand though =) From:Cassiel [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 09, 2008 10:51 AM To: Debian User List Subject: Re: apache2 in Debian - adding vhost - which file to edit? 2008/9/9 Zach Uram < [EMAIL PROTECTED] > I am trying to add a name based virtual host to apache2-mpm-prefork version 2.2.9-7 on Debian lenny/sid. First I read to edit /etc/apache2/httpd.conf but this file it seems is empty and not used in Debian. Then I read to edit /etc/apache2/apache2.conf but it seems that is also not the right place for adding it so then I found the file /etc/apache2/sites-enabled/000-default This is the correct file to edit? I was told to add my section to it such as: . yes, but 000-default file should be left alone with standard directives for your DocRoot /var/www/ then you should put directives for any other web site you are going to add in a separate file in /etc/apache2/sites-available/ and then create a symlink to it in /etc/apache2/sites-enabled/ so you can simply remove the symlink if you ever want to put sites offline instead of commenting out lines on a single, maybe huge, conf file, moreover you gain better control on per site directives (before going online) http://httpd.apache.org/docs/2.2/ regards
RE: Syslog Garbage
man syslogd: -m interval The syslogd logs a mark timestamp regularly. The default interval between two -- MARK -- lines is 20 minutes. This can be changed with this option. Setting the interval to zero turns it off entirely. > -Original Message- > From: Volkan YAZICI [mailto:[EMAIL PROTECTED] > Sent: Monday, September 08, 2008 1:31 PM > To: debian-user@lists.debian.org > Subject: Syslog Garbage > > Hi, > > Despite I have below lines in my syslog.conf file > > auth,authpriv.*;cron.none /var/log/auth.log > *.*;auth,authpriv,cron.none -/var/log/syslog > cron.* /var/log/cron.log > daemon.*-/var/log/daemon.log > kern.* -/var/log/kern.log > lpr.* -/var/log/lpr.log > mail.* -/var/log/mail.log > user.* -/var/log/user.log > uucp.* /var/log/uucp.log > ftp.* /var/log/ftp.log > > I see /var/log/syslog filled with below garbage lines: > > ... > Sep 8 11:05:20 arge -- MARK -- > Sep 8 11:25:20 arge -- MARK -- > Sep 8 11:45:21 arge -- MARK -- > ... > Sep 8 12:05:21 arge -- MARK -- > Sep 8 12:25:21 arge -- MARK -- > Sep 8 12:45:21 arge -- MARK -- > Sep 8 13:05:22 arge -- MARK -- > Sep 8 13:25:22 arge -- MARK -- > ... > > What might be causing this garbage output. I couldn't find any related > cron jobs. Any ideas? > > > Regards. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: mail (local mail)
I'd go with postfix, which also already provides a reasonably short default "localhost only" configuration and is pretty secure by design. Compared to sendmail, the configuration is easily comprehensible and extensible for everybody (again adding to security). I wouldn't recommend working with sendmail if there's no existing infrastructure relying on it, you have specific sendmail knowledge or need it for some other special purpose that can only be achieved with it. > -Original Message- > From: Mark Allums [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 30, 2008 11:09 AM > To: debian-user@lists.debian.org > Subject: Re: mail (local mail) > > Xavier J. B. L. wrote: > > Recently I drop exim4 packages (# apt-get remove exim4 exim4-base > > exim4-config exim4-daemon-light) and so it removes "at" and "bsd-mailx". > > > > Now I haven't mail (because it drops me bsd-mailx). > > But I want having mail for simply: > > - read /var/mail > > - when I login, shell says me "you have a mail" and I can run "mail" > > or similar program > > - I can send local mails (from [EMAIL PROTECTED] to [EMAIL PROTECTED], > > etc.) > > > > What program fits into my needs (without reinstalling exim4, postfix or > > equivalents)?. Or I have to install mail server? > > Does anyone know it? > > > > I putting this question in arm list and it says me that I have to post > > here. > > > > > > Thanks a lotm > > Xan. > > > > > > > > Mostly, you want a server. It is pretty much the only way. If > resources are scarce, you can try various things, but programs which > send local mail expect it to Just Work. > > You don't have to have mail, but it is conceivable that something will > break. Mail is part of any standard system, excepting embedded. > > Look at the list of packages available, using the web or Aptitude or > Synaptic or whatever. Look for something that is mature and fairly > lightweight. It needs to be an MTA. It doesn't need to support POP3 or > IMAP necessarily; that is what Icedove (Thunderbird), Mutt, PINE, etc. > are for. > > Good ol' sendmail will work. It is reasonably light and fairly efficient. > > Mark Allums > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Which --delete* to Use in 'rsync'
The during or after options should be a bit faster because rsync already knows what to delete and doesn't have to scan for changes, but especially after may cause problems if a directory changes into a file or the other way round. I don't know how rsync handles such cases, the option should probably be combined with force. Also, deleting the files before the transfer reduces the space required for the operation and reduces the risk of running out of space. On the other hand, if for some reason the transfer fails, you still have valid copies of the files on the receiving end. Just my thoughts on this. > -Original Message- > From: Kenneth Jacker [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 21, 2008 5:47 PM > To: debian-user > Subject: Which --delete* to Use in 'rsync' > > >From rsync(1): > > --deletedelete extraneous files from dest dirs > --delete-before receiver deletes before transfer (default) > > --delete-during receiver deletes during xfer, not before > --delete-after receiver deletes after transfer, not before > > > I've always just used the first option (--delete). > > Can anyone suggest when I might use one of the last two? > > Thanks! > -- > Prof Kenneth H Jacker [EMAIL PROTECTED] > Computer Science Dept www.cs.appstate.edu/~khj > Appalachian State Univ > Boone, NC 28608 USA > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: What to do about SSH brute force attempts?
If you have an existing userbase, you can't just switch to public key authentication, depending on the type of customer. pubkey auth is also generally inconvenient if people tend to use different computers. This is also a problem we just ran into. Fortunately, recent versions of OpenSSH support match blocks and chroot. This allows you to a) selectively enable/disable password authentication, which reduces the possibility of a successful brute force attack, and b) re-root anybody to their respective homes so even if somebody successfully breaks into your system, there's no much he could do then. It also allows you to completely disable FTP access, which not only prevents passwords being transmitted in plain text but also closes a hole in your firewall setup. Combined with thorough system monitoring (prelude, snort, samhain, zabbix...) and a generally strict security policy (proper file system permissions, mount options and so on, any proactive security measures), any system can be made pretty hard to attack. On the other hand, as the recent key vulnerabilities caused by the Debian OpenSSL version have shown (http://lists.debian.org/debian-security-announce/2008/msg00152.html), you can't make sure that the programs your security policy relies on don't have holes in themselves. "Pretty hard to attack" is usually just a question of how skilled and persistent the attacker is. A script kiddy running a simple brute force attack can usually easily be blocked by having something like denyhosts running in the background. Somebody who really wants to break into your system and actually knows what to look for won't be stopped by such measures. If somebody from within the system tries to do bad things, you usually have a valid contract with that person which makes it easy to sue him for any damages or downtimes caused. Depending on the user type, it would also be possible to mount the user fs noexec and only allow access to a read-only fs containing executables from within his chroot (proactive approach again). > -Original Message- > From: Henrique de Moraes Holschuh [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 21, 2008 5:21 PM > To: Michael Tautschnig > Cc: [EMAIL PROTECTED] > Subject: Re: What to do about SSH brute force attempts? > > On Thu, 21 Aug 2008, Michael Tautschnig wrote: > > > * use a Firewall to prevent other IP address to connect to your ssh > > > service. restrict just to yours (iptables script can be easy to find on > > > the web) > > Well, I should have added that my hosts must be world-wide accessible using > > password-based authentication, so this is no option. > > In the long term, switch to key-based auth. > > > I'm not a huge fan of security by obscurity, so I'd rather stick with 22 for > > now. > > Switch to key-based auth. Brute-forcing the keys is much harder. > > Meanwhile, you really should do something to reduce your attack surface, so > fail2ban and the like, plus non-standard ports are a damn good idea while > you implement the proper "fix" (drop passwords). > > > What remains open is what could one do proactively? I don't really feel like > > striking back, but getting rid of the attackers would be kind of nice... > > Strike against a botnet? That's a waste of effort, really, with very few > exceptions. > > -- > "One disk to rule them all, One disk to find them. One disk to bring > them all and in the darkness grind them. In the Land of Redmond > where the shadows lie." -- The Silicon Valley Tarot > Henrique Holschuh > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: Which USB stick for Debian root filesystem
I'm using Sandisk Cruzer Contour sticks for this purpose (with our firewall hosts for example). They're quite durable and fast. USB sticks generally have problems when it comes to many write cycles (shouldn't fail within such a short time though, mean time between failure is about one million writes per cell iirc). Anything that causes a lot of writes shouldn't be directly on the stick if possible. E.g. /var/log can be placed in a ramdisk as well. PS: You may also consider using an (external) 2,5" harddisk instead of an USB stick. They consume almost no power, don't heat up much and you won't hear it as well. And they're fast. > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 21, 2008 6:36 AM > To: debian-user@lists.debian.org > Subject: Which USB stick for Debian root filesystem > > Hello. > > Today, I have experienced file system crash on my USB > stick. I had been running Debian on it for less than two months, and > today it just started having problems reading some files. I ran fsck > and... let's just say there was not much left from my file system > > Yes, > I heard that USB sticks are not very reliable. But it died after only > two months! I was expecting it to run without problems for at least a > year or so. > > In the light of this, I really don't know what USB > drive should I chose now. My previous USB was an cheap A-Data (which > now sounds like a very poor choice). Are other memory sticks (Kingston, > OCZ, etc) more reliable? > > Please share some of your experience. > Which USB drives would you recommend, and which are not good for 24/7 > usage as Linux root file system? > > I don't want to install my > system on a hard drive because of power consumption and heat. I really > want to use USB drive, but I need something that will last for more > than two months. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: WebMail Interface
Last time I tried roundcube it had some serious security issues (possible mysql injections). Overall the code quality seemed very unsteady. But maybe this got better in the meantime. > On 08/20/2008 01:53 PM, Lucas Mocellin wrote: > > Nowadays, Atmail is free. > > > > look at atmail.com, this is a good interface. > > apparently only as a 'teaser' version that lacks pop-, spam- or > maildir-support etc. and does not include a server. [1] > > It's also not included in debian lenny. > > Is it really s much better than what apt-cache search webmail spits > [2] at you? > > Johannes > > [1] http://atmail.org/compare.php > [2] like mailreader, prayer, roundcube, squirrelmail, sqwebmail, ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: aptitude purge
I usually do so (or create debian packages myself), but since they already provide amd64 Debian etch packages I just installed them with dpkg, e.g. http://www.zmanda.com/downloads/community/Amanda/2.6.0p1/Debian-Etch/amanda-backup-client_2.6.0p1-1_amd64.deb Unfortunately, the package has a different name: dom0:~# aptitude search amanda i amanda-backup-server - Amanda Network Backup and Archiving software c amanda-client - Advanced Maryland Automatic Network Disk Archiver (Client) c amanda-common - Advanced Maryland Automatic Network Disk Archiver (Libs) c amanda-server - Advanced Maryland Automatic Network Disk Archiver (Server) I guess I'll have to go clean this up by hand then. > In Debian you'd want to use the package manager for installation and not make > installs outside of it, like using 'make install'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
