Re: Have I been hacked?
On 01/10/2015 12:01 AM, Jerry Stuckle wrote: > On 1/9/2015 10:24 PM, scott wrote: >> On 01/09/2015 09:19 PM, Jerry Stuckle wrote: >>> On 1/9/2015 8:49 PM, Joel Rees wrote: On Fri, Jan 9, 2015 at 6:25 PM, Martin Steigerwald wrote: > Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: >> On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: >>> Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: Just ensure you're using good security practices - don't allow root login, use long, random passwords, etc. I also use a random character strings for the login ids, as well as passwords - just one more thing for the hackers to have to figure out how to get around. >>> >>> Only allow SSH key based logins. Of course, only after you copied a >>> public >>> key onto the machine with ssh-copy-id. >>> >>> And have SSH keys with *strong* passphrases, to protect against someone >>> stealing your key. Use ssh-agent wisely only on trusted machines. >> >> SSH password logins are just as safe. 20 characters gives a strong >> password for use on trusted machines. There is no need to worry about >> it being stolen because it is in your memory, > > I think SSH keys are safer, cause there is no password at all that can be > brute forced. What do you mean by that? > Okay, one can try to guess the key, but try that with a 4096 bit > key. Hmm. 10 characters, 6 to 7 bits per character, that's 60 bits. If the bits are truly random, straight brute-force will take, on average, half of 2^60 attempts. We can hold the integer 2^59 in a C variable on most recent desktops, but if we have bc (dc if you like post-fix), we can do this on even 32 bit CPUs: 576460752303423488 (base ten) At one milion attempts per second, that's 5764607523034 seconds, or 182678 CPU-years. There's no way that's going to happen on-line, if the password is truly random, and not randomly a password that's a quick permutation of common memes or of entries in rainbow tables. >>> >>> Actually, 62 possible characters (upper case, lower case and digits), 10 >>> positions is 62^10 or 839,299,365,868,340,224 possible combinations. >>> >>> Adding in special characters obviously would increase that. >>> >>> But there is no way you'll hit a server 1,000,000 times a second trying >>> to brute force a password. >>> >>> I currently use sixteen or more letters in my passwords, don't use simple permutations or common phrases (as for the first leter trick), use disconnected words from multiple languages. Or use 16 character true random passwords for the important stuff. >>> >>> All good suggestions. >>> SSH keys are useful, but you have to keep them somewhere. The real danger to good passwords is the off-line attempts, and the passphrase you use for your private keystore is potentially subject to off-line if your password is. >>> >>> Yes, keys may actually be less secure than passwords. >>> >>> Jerry >>> >>> >> If you have a dedicated hacker, or hackers, time is on their side. I >> would much rather use a key with a passphrase. >> >> > > That's fine, if you don't care about security. Lose your laptop and > your pass phrase can be broken at a rate of 1 billion attempts per > second, since it is local to your machine. > > There is no way you're going to get even 100 attempts per second into an > SSH server. And since the hacker doesn't have direct access to the > encrypted password on the server, he can't break it on a local machine. > Using the same password/pass phrase for both systems, it would take > 10,000,000 times longer to hack the SSH password than your local pass > phrase. > > And then there's the problem you can only access the server from a > system with the key file. And the more computers the key file resides > on, the less secure it is. > > Since a password is not stored on any machine (except the server), there > is nothing to break. > > Jerry > > I replied to your post to me specifically, so I 'll do it here, also. The fact is that if you have physical access to any machine, unfettered, it's game over. Scotty -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b0b779.2010...@gmx.com
Re: Have I been hacked?
On 1/9/2015 10:24 PM, scott wrote: > On 01/09/2015 09:19 PM, Jerry Stuckle wrote: >> On 1/9/2015 8:49 PM, Joel Rees wrote: >>> On Fri, Jan 9, 2015 at 6:25 PM, Martin Steigerwald >>> wrote: Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: > On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: >> Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: >>> Just ensure you're using good security practices - don't allow root >>> login, use long, random passwords, etc. I also use a random character >>> strings for the login ids, as well as passwords - just one more thing >>> for the hackers to have to figure out how to get around. >> >> Only allow SSH key based logins. Of course, only after you copied a >> public >> key onto the machine with ssh-copy-id. >> >> And have SSH keys with *strong* passphrases, to protect against someone >> stealing your key. Use ssh-agent wisely only on trusted machines. > > SSH password logins are just as safe. 20 characters gives a strong > password for use on trusted machines. There is no need to worry about > it being stolen because it is in your memory, I think SSH keys are safer, cause there is no password at all that can be brute forced. >>> >>> What do you mean by that? >>> Okay, one can try to guess the key, but try that with a 4096 bit key. >>> >>> Hmm. >>> >>> 10 characters, 6 to 7 bits per character, that's 60 bits. >>> >>> If the bits are truly random, straight brute-force will take, on >>> average, half of 2^60 attempts. >>> >>> We can hold the integer 2^59 in a C variable on most recent desktops, >>> but if we have bc (dc if you like post-fix), we can do this on even 32 >>> bit CPUs: >>> >>> 576460752303423488 (base ten) >>> >>> At one milion attempts per second, that's 5764607523034 seconds, or >>> 182678 CPU-years. >>> >>> There's no way that's going to happen on-line, if the password is >>> truly random, and not randomly a password that's a quick permutation >>> of common memes or of entries in rainbow tables. >>> >> >> Actually, 62 possible characters (upper case, lower case and digits), 10 >> positions is 62^10 or 839,299,365,868,340,224 possible combinations. >> >> Adding in special characters obviously would increase that. >> >> But there is no way you'll hit a server 1,000,000 times a second trying >> to brute force a password. >> >> >>> I currently use sixteen or more letters in my passwords, don't use >>> simple permutations or common phrases (as for the first leter trick), >>> use disconnected words from multiple languages. Or use 16 character >>> true random passwords for the important stuff. >>> >> >> All good suggestions. >> >>> SSH keys are useful, but you have to keep them somewhere. The real >>> danger to good passwords is the off-line attempts, and the passphrase >>> you use for your private keystore is potentially subject to off-line >>> if your password is. >>> >> >> Yes, keys may actually be less secure than passwords. >> >> Jerry >> >> > If you have a dedicated hacker, or hackers, time is on their side. I > would much rather use a key with a passphrase. > > That's fine, if you don't care about security. Lose your laptop and your pass phrase can be broken at a rate of 1 billion attempts per second, since it is local to your machine. There is no way you're going to get even 100 attempts per second into an SSH server. And since the hacker doesn't have direct access to the encrypted password on the server, he can't break it on a local machine. Using the same password/pass phrase for both systems, it would take 10,000,000 times longer to hack the SSH password than your local pass phrase. And then there's the problem you can only access the server from a system with the key file. And the more computers the key file resides on, the less secure it is. Since a password is not stored on any machine (except the server), there is nothing to break. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b0b23c.8060...@gmail.com
RE: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Bob, Trying my best with the trimming; I'll keep observing how other people do it and try to learn from that. > > It does work in other Linux distros that I have tried. > > If it works anywhere then it should be possible to learn why and/or why not and > to transfer that knowledge. > > The other distro may have done something unique and special there to make it > work. The task is then to figure this out and make it available in Debian. That's what I would have thought. > > Rhythm Box appears to work just fine. > > How would Rhythm Box know what your smb username and password would > be? Good question. My guess is perhaps since it's part of Gnome it's more integrated and since Gnome must know my credentials when I access the Windows shares initially, it probably has a standard place to store that information. But this is just a guess from a day 3 day old Debian user. > I suggest that you post a new message to the mailing list. >[snip] > Give it a go. Good luck! I was thinking that myself but wasn't sure on the best procedure there either so thanks for filling me in. When I get a chance I'll do just that. Cheers, Wayne. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/008801d02c8f$97d839a0$c788ace0$@ozemail.com.au
Re: Have I been hacked?
On 01/09/2015 09:19 PM, Jerry Stuckle wrote: > On 1/9/2015 8:49 PM, Joel Rees wrote: >> On Fri, Jan 9, 2015 at 6:25 PM, Martin Steigerwald >> wrote: >>> Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: > Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: >> Just ensure you're using good security practices - don't allow root >> login, use long, random passwords, etc. I also use a random character >> strings for the login ids, as well as passwords - just one more thing >> for the hackers to have to figure out how to get around. > > Only allow SSH key based logins. Of course, only after you copied a public > key onto the machine with ssh-copy-id. > > And have SSH keys with *strong* passphrases, to protect against someone > stealing your key. Use ssh-agent wisely only on trusted machines. SSH password logins are just as safe. 20 characters gives a strong password for use on trusted machines. There is no need to worry about it being stolen because it is in your memory, >>> >>> I think SSH keys are safer, cause there is no password at all that can be >>> brute forced. >> >> What do you mean by that? >> >>> Okay, one can try to guess the key, but try that with a 4096 bit >>> key. >> >> Hmm. >> >> 10 characters, 6 to 7 bits per character, that's 60 bits. >> >> If the bits are truly random, straight brute-force will take, on >> average, half of 2^60 attempts. >> >> We can hold the integer 2^59 in a C variable on most recent desktops, >> but if we have bc (dc if you like post-fix), we can do this on even 32 >> bit CPUs: >> >> 576460752303423488 (base ten) >> >> At one milion attempts per second, that's 5764607523034 seconds, or >> 182678 CPU-years. >> >> There's no way that's going to happen on-line, if the password is >> truly random, and not randomly a password that's a quick permutation >> of common memes or of entries in rainbow tables. >> > > Actually, 62 possible characters (upper case, lower case and digits), 10 > positions is 62^10 or 839,299,365,868,340,224 possible combinations. > > Adding in special characters obviously would increase that. > > But there is no way you'll hit a server 1,000,000 times a second trying > to brute force a password. > > >> I currently use sixteen or more letters in my passwords, don't use >> simple permutations or common phrases (as for the first leter trick), >> use disconnected words from multiple languages. Or use 16 character >> true random passwords for the important stuff. >> > > All good suggestions. > >> SSH keys are useful, but you have to keep them somewhere. The real >> danger to good passwords is the off-line attempts, and the passphrase >> you use for your private keystore is potentially subject to off-line >> if your password is. >> > > Yes, keys may actually be less secure than passwords. > > Jerry > > If you have a dedicated hacker, or hackers, time is on their side. I would much rather use a key with a passphrase. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b09b89.5060...@gmx.com
Re: Have I been hacked?
On 1/9/2015 8:49 PM, Joel Rees wrote: > On Fri, Jan 9, 2015 at 6:25 PM, Martin Steigerwald > wrote: >> Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: >>> On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: > Just ensure you're using good security practices - don't allow root > login, use long, random passwords, etc. I also use a random character > strings for the login ids, as well as passwords - just one more thing > for the hackers to have to figure out how to get around. Only allow SSH key based logins. Of course, only after you copied a public key onto the machine with ssh-copy-id. And have SSH keys with *strong* passphrases, to protect against someone stealing your key. Use ssh-agent wisely only on trusted machines. >>> >>> SSH password logins are just as safe. 20 characters gives a strong >>> password for use on trusted machines. There is no need to worry about >>> it being stolen because it is in your memory, >> >> I think SSH keys are safer, cause there is no password at all that can be >> brute forced. > > What do you mean by that? > >> Okay, one can try to guess the key, but try that with a 4096 bit >> key. > > Hmm. > > 10 characters, 6 to 7 bits per character, that's 60 bits. > > If the bits are truly random, straight brute-force will take, on > average, half of 2^60 attempts. > > We can hold the integer 2^59 in a C variable on most recent desktops, > but if we have bc (dc if you like post-fix), we can do this on even 32 > bit CPUs: > > 576460752303423488 (base ten) > > At one milion attempts per second, that's 5764607523034 seconds, or > 182678 CPU-years. > > There's no way that's going to happen on-line, if the password is > truly random, and not randomly a password that's a quick permutation > of common memes or of entries in rainbow tables. > Actually, 62 possible characters (upper case, lower case and digits), 10 positions is 62^10 or 839,299,365,868,340,224 possible combinations. Adding in special characters obviously would increase that. But there is no way you'll hit a server 1,000,000 times a second trying to brute force a password. > I currently use sixteen or more letters in my passwords, don't use > simple permutations or common phrases (as for the first leter trick), > use disconnected words from multiple languages. Or use 16 character > true random passwords for the important stuff. > All good suggestions. > SSH keys are useful, but you have to keep them somewhere. The real > danger to good passwords is the off-line attempts, and the passphrase > you use for your private keystore is potentially subject to off-line > if your password is. > Yes, keys may actually be less secure than passwords. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b08c3d.4090...@gmail.com
Re: Have I been hacked?
On Fri, Jan 9, 2015 at 6:25 PM, Martin Steigerwald wrote: > Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: >> On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: >> > Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: >> > > Just ensure you're using good security practices - don't allow root >> > > login, use long, random passwords, etc. I also use a random character >> > > strings for the login ids, as well as passwords - just one more thing >> > > for the hackers to have to figure out how to get around. >> > >> > Only allow SSH key based logins. Of course, only after you copied a public >> > key onto the machine with ssh-copy-id. >> > >> > And have SSH keys with *strong* passphrases, to protect against someone >> > stealing your key. Use ssh-agent wisely only on trusted machines. >> >> SSH password logins are just as safe. 20 characters gives a strong >> password for use on trusted machines. There is no need to worry about >> it being stolen because it is in your memory, > > I think SSH keys are safer, cause there is no password at all that can be > brute forced. What do you mean by that? > Okay, one can try to guess the key, but try that with a 4096 bit > key. Hmm. 10 characters, 6 to 7 bits per character, that's 60 bits. If the bits are truly random, straight brute-force will take, on average, half of 2^60 attempts. We can hold the integer 2^59 in a C variable on most recent desktops, but if we have bc (dc if you like post-fix), we can do this on even 32 bit CPUs: 576460752303423488 (base ten) At one milion attempts per second, that's 5764607523034 seconds, or 182678 CPU-years. There's no way that's going to happen on-line, if the password is truly random, and not randomly a password that's a quick permutation of common memes or of entries in rainbow tables. I currently use sixteen or more letters in my passwords, don't use simple permutations or common phrases (as for the first leter trick), use disconnected words from multiple languages. Or use 16 character true random passwords for the important stuff. SSH keys are useful, but you have to keep them somewhere. The real danger to good passwords is the off-line attempts, and the passphrase you use for your private keystore is potentially subject to off-line if your password is. > Anyway, I will unsubscribe now. > > Staying on this list has not been beneficial for me. > > The amount of traffic on this list, that is not related to Debian or is > bickering like this is soo high that I find it too time consuming to find out > the rare gems of threads where I can still learn something new about Debian or > that I enjoy in engaging and replying to. > > Don´t bother to answer. I will likely delete it. > > Ciao, > -- > Martin 'Helios' Steigerwald - http://www.Lichtvoll.de > GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- Joel Rees Freedom costs in software, too. How much, and what, are you willing to pay for your freedom? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caar43imglrutsiitri17xotaz0qvwip5eymc1z-q+vsd_ss...@mail.gmail.com
Tip: Search Command Line Commands w/First Letters And Tab
On 5/2/14, Ralf Mardorf wrote: > > Ok, if I don't remember the complete command name and I like to use the > tab key to show me a list of available commands (r typing the complete > command name is to much work, then I first type the first characters > without sudo, push the tab key and after that I add sudo. > > [rocketmouse@archlinux ~]$ ch > chacl chattrcheckdotdin checkupdates chfn > chmod chpasswordchrt > chage chcon checkgid checkXML chgpasswd > chmorph chromedriver chsh > charmap chcp check_hd cheesechgrp > chown chromium chuser > chat chcpu check-regexp chem chktex > chpasswd chrootchvt > [rocketmouse@archlinux ~]$ sudo ch Am in my inbox digging around and came across this older post. Seemed like a useful memory aid oriented tip to highlight. I just tried it, and it works great in GNOME Terminal. I tried three letters, too. I tried "deb" and received just "debconf" back at first for some reason. For kicks and giggles since only one command came back, I hit the tab key a couple more times again and ended up receiving a list of all commands that begin with "debconf". Very cool. My thoughts are always that maybe someone else doesn't know it exists, and maybe they know of just the right wish list where this feature or a tweak of it would be perfect for the next upgrade of something else Debian out there. :) Cindy :) -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * runs with plastic sporks * -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAO1P-kBf7mjVRi0u6cLv09XBQCycOEb=pjhdndn2lrcn3uf...@mail.gmail.com
Re: Have I been hacked?
2015/01/09 23:46 "Danny" : > > > > > You have completely failed to understand what fail2ban is telling you. > > > > > Anyway, I have decided to get new hardware and do a clean install of > > > everything > > > ... as many of you have suggested ... > > > > It was heading that way so it is probably best for you. > > > > You sound like a heartless Seargeant Major in the Marines ... ;) ... I'm afraid you're going to like my comments here even less. > > > However, as I fly a lot internationally, is there a way I can temporarily > > > block > > > these country's IP's for a few days at most untill I have enough time on > > > hand to do a fresh install ... > > > > What has flying got to do with it? > > > What I meant was that I fly a lot and don't have time in the immediate future > to > do a fresh install ... So I wanted a temporary stop-gap solution for a few > days > untill time would lend itself for the task ... Which was why I was trying to tell you to quit wasting time looking for shortcuts and consolation and re-install. Start with new hardware if you can possibly afford it, to be safe and to save time. Now it looks like your server needs to be off-line for a while until you get back. Also, once you're back up, you need a second, someone who can at least pull the plug while you're out, preferably someone who can also help you review your system design and implementation. Patience, and willingness to listen while you ramble, can be more important than technical expertise. -- Joel Rees Freedom costs in software, too. How much, and what, are you willing to pay for your freedom? > > > Currently my iptables looks like this ... > > > > If you have resorted to using iptables you have lost it. A standard > > Debian install doesn't need it. > > > Yip ... definately a Seargeant Major ... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caar43in7jyn-dg2tb29o6kkrmjloxpzxnq9nmq7iry5q+fq...@mail.gmail.com
Re: _COMPLETE_ instructions for debootstrap &/or multistrap
2015/01/09 6:40 "Cindy-Sue Causey" : > > [...] > > As an aside and yet really directly related, my complaints and > observations a while back about the seeming uptick in people having > trouble with incompatibility became more clear in the last few weeks. > There's some what *FEELS LIKE* bad advice running around out there > about how to bind and mount while working with chroot to complete the > rest of a system install. Won't explain everyone's incompatibility > issues, but it sure as heck explained mine. Free advice is worth what you pay for it. Bad advice is part of the price. So is learning to weed the bad out, > [...] If you're new to this, don't to do what I've been > doing. Instead work that page top to bottom, and research what you > need to in order to do it as they've outlined there. In hindsight, I > can see the benefit of following every single step in order as it > applies to or needs altered slightly to fit each, our own singular > install instances. > [...] Inside-out is sometimes the only way in. Which is another of the costs of free advice. There are other costs, including such things as enduring stupid questions, flame wars, and social engineering attempts. (Not to Cindy-Sue as much as to the entire list.) -- Joel Rees Freedom costs in software, too. How much and what are you willing to pay for your freedom? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/caar43iozgdhungbur_692oky7n0tvuyge8bfc6x2aa1wq+2...@mail.gmail.com
Re: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
On Friday 09 January 2015 22:35:45 Bob Proulx wrote: > And also good editor skills of trimming out unneeded excess quoting. > Be brutal with removing excess quotes! Personally I would rather see > no previous quoted material rather than bad full quoting. Want to see > what the message looks like to other people? Take a look at it in the > mailing list archive. If it is hard for you to read then it will be > hard for other people to read too. > > https://lists.debian.org/debian-user/2015/01/msg00288.html > > Contrast that to this message in the archive. I have brutally trimmed > the quotes to just the points to which I am replying. > > > https://lists.debian.org/20150109151004514416184.noccsple...@bob.proulx.com Most of the bad trimming in the first of these is mine. I am very bad at trimming. I over-cut or cut the wrong thing so that when I read the nessage back later I can't follow it - so how can anyone else. So then I cut too little. But don't blame poor Wayne who made quite a good job of my hash. I was told always to leave enough for someone new to the list/thread to be able to follow what the discussion is about just by reading your posting, and not a scrap more. But I am not very good at it. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501092328.46242.lisi.re...@gmail.com
Re: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
On 01/09/2015 07:20 AM, Wayne Hartell wrote: > [snip] > Yes, you're right I am using Outlook since I've signed up to this list on a > virtual machine that is configured for taking on the road for my work. I > haven't yet taken a look at Evolution and others e-mail clients, but I fear > that I'll be stuck on Outlook for a little while longer, until I convince > myself to make a permanent switch. Hopefully this is a little better in > terms of what is expected on the list. I edited a couple of settings to try > to improve things. I come from windows/outlook IMO Thunderbird is a wonderful alternative and is very easy to configure to look/feel/behave the way you want, might want to give it a try. -Joris signature.asc Description: OpenPGP digital signature
Re: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Hi Wayne, Wayne Hartell wrote: > Thanks. I'm sure to violate some conventions here in reply format or what > have you. Just let me know if I do and I'll try to remedy in future. I see you have already exchanged mail concerning one of those things. :-) There are 2,000+ subscribers on this mailing list. If you could imagine a town hall meeting with 2,000+ physical people in the room all with voices you can imagine how difficult it can be to keep discussion efficient. That is why trimming excess words is so important. It makes it easier for people to read and understand the message. If they can read and understand then you are much more likely to receive a high quality reply in return. > With respect to reporting the issue as a bug I started down that path using > Reportbug, but noticed that a similar issue (not quite the same, or maybe I > just didn't understand it fully), so I wanted to discuss it first. Thanks > for providing that opportunity. Please feel welcome to discuss problems such as you have found on this mailing list. We are mostly all simple users of the Debian system. A few are developers. Have some patience. You may get answers or help that is better or worse on different days. > It does work in other Linux distros that I have tried. If it works anywhere then it should be possible to learn why and/or why not and to transfer that knowledge. The other distro may have done something unique and special there to make it work. The task is then to figure this out and make it available in Debian. > "VLC is unable to open the MRL" (I have more detailed debug output if > needed). > ... > The work around is to edit the smb:.mp3 to be > smb://user:password@//.mp3 That makes sense to me. With the username and password it can then access the media. > When I do this, it will work, but I have to do it for every file I add to > the play list. I understand that can be quite the pain. :-( > Rhythm Box appears to work just fine. How would Rhythm Box know what your smb username and password would be? > I'm not overly concerned about the issue which is why I wanted to discuss it > before I submitted any official bug (that would obviously be low priority). > I noticed Debian bug #602985 appears quite similar (it's about getting VLC > to prompt for smb credentials), but I'm not sure if it's exactly the same. > > Anyway, I appreciate you taking the time to respond to my post. This may > seem a little trivial, but it's my first serious foray into Linux, just a > couple of days old, and rather than run from issues I want to learn not only > how to tackle the issues, but the processes that go along with Debian in > general. I don't have any knowledge of either of the two areas needed. I don't know about smb shares. I don't know about vlc using remote media through smb shares. Sorry I can't help there. And I don't see other help on this issue. (At least not yet). I suggest that you post a new message to the mailing list. (I will be specific about it being a NEW message. If you reply to any mailing list message then your reply will be threaded below it. Since Outlook does not handle message threads most Outlook users don't realize that replying to start a new message causes threading problems. That creates a situation known as thread stealing or thread hijacking. To avoid that simply start a new message every time you have a new topic.) I suggest that you post a new message to the mailing list. Pick a good short concise subject. In this case I would definitely mention both VLC and SMB shares and password in the subject. There is no right answer but just to get the thought processes going I will suggest something like: VLC password in SMB shares URL? You want to attract the attention of people who are knowledgeable about those things. It is in your interest to choose the subject to make it clear to those people so that they will choose to read your message. This current thread is not good because those people not interested in web forums have already skipped over it. Remember that there are 2,000+ people on the list. Meaning that there are a lot of postings. Not every posting will interest everyone. At some point everyone is going to be skipping a lot of messages. Connecting you and them together needs good subject lines. And also good editor skills of trimming out unneeded excess quoting. Be brutal with removing excess quotes! Personally I would rather see no previous quoted material rather than bad full quoting. Want to see what the message looks like to other people? Take a look at it in the mailing list archive. If it is hard for you to read then it will be hard for other people to read too. https://lists.debian.org/debian-user/2015/01/msg00288.html Contrast that to this message in the archive. I have brutally trimmed the quotes to just the points to which I am replying. https://lists.debian.org/20150109151004514416184.noccsple...@bob.proulx.com Include
Re: Have I been hacked?
On 1/9/2015 4:37 PM, Bob Holtzman wrote: > On Fri, Jan 09, 2015 at 10:49:49AM -0500, Jerry Stuckle wrote: > >snip... >> >> SSH passwords are very safe, if they are long enough. For instance, if >> you have a 10 character password, mixed case and numbers (no special >> characters), a brute force attack of 100 attempts per second would take >> almost 266 million years to cover all possibilities. 11 characters >> would take over 16 billion years - longer than the life of the universe. > > That's the key phrase, "to cover all possibilities" Don't forget, it's > possible to hit pay dirt on the first try...or the 3rd...or the 20th... > or the 500th...or the 50,000th...or the last possibility. > > I constantly hear references to mind boggling lengths of time required > to crack passwords/phrases. I think it's misleading, especially to a > beginner. On the other hand I have to admit I can't come up with a > better way. > >...snip.. > That's true. On average it will take 1/2 as long - or about 133 million years for a 10 character password or 8 billion years for an 11 character password. But that's also assuming the hacker knows how long your password is. He/she would also have to consider all possible combinations of 1-9 character passwords. That alone would take almost 4.36 million years just to ensure the password wasn't shorter. Of course, the hacker could also probably skip 1 character passwords (< 1 second), 2 character passwords (38 seconds), etc. But even going through all the possibilities of 9 character passwords would take around 4.29 million years (without a hit because the password is 10 characters). Of course, *anything* can be caught on the first, second or third try. But the odds of hitting it on the first try are over 13 quadrillion (13 followed by 15 zeros) to 1. You have a better chance of being struck by lightning while in an elevator 300' underground! Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b0530a.4020...@gmail.com
Re: Have I been hacked?
Bob Holtzman writes: > That's the key phrase, "to cover all possibilities" Don't forget, it's > possible to hit pay dirt on the first try And it's about equally likely that a burst of cosmic rays of just the right pattern will strike your computer so as to reconfigure it to allow passwordless root logins via telnet. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87vbkfha85@thumper.dhh.gt.org
Re: test VMs
Bonno Bloksma wrote: > I was thinking I could run something which Debian Install runs too > but then later realized that probably depends on files like ssh keys > not being present yet and only creating new keys when that is the > case. There isn't anything that runs later that does this in the debian-installer. Things are built up from nothing in place with the settings as given by the user. > > A very basic list of things that need to be changed are: > > Thanks, that is enough for now. Just going to install a machine with > only the system tools installed, need to do some basic routing / > firewall testing. I think you will do fine then. Note that there are often some lingering places where a previous hostname persists. Mostly those are harmless. But they do persist. Therefore picking a neutral hostname for the initial installation that won't do any harm later is good. Such as "localhost" is typical. But otherwise something else innocuous is good too. For example the mdadm tool encodes the system name into arrays constructed by the debian-installer. mdadm --examine /dev/sda1 Bob signature.asc Description: Digital signature
Re: How can g++ (stable) be incompatible with a fresh stable install?
On 01/09/2015 at 03:57 PM, Sven Hartge wrote: > Kynn Jones wrote: > >> On Thu, Jan 8, 2015 at 7:18 PM, Sven Hartge >> wrote: >> >>> Kynn Jones wrote: >>> Your priorities for the different versions seem off. Security >>> should have to same priority as stable, not a higher one. >>> >>> And security should not need a higher priority, because security >>> updates (not already included via point-release) will always have >>> a higher version than the non-security package from the normal >>> repository. > >> OK, I thought I understood what was going on, but it turns out >> that I'm more baffled than ever. (E.g. I don't understand why I'm >> given the *option* of setting a priority for security when in fact, >> if I understand you correctly, there's only one sensible setting >> for it, namely "identical to stable"...) > > The option exists because there might be a use case for someone > somewhere. Just because an option is useless for you does not mean it > is useless for everybody. (See also "root should be able to shoot itself in the foot".) Also because the stable security updates repository is, in terms of technical implementation, exactly like any other package repository. In particular, it uses the same infrastructure - including tools which have support for repository priorities built in, and have no way of knowing that this particular repository is in any way special. It's possible (and often desirable) to set a separate priority for an ordinary package repository, and because the security-updates repository uses the same infrastructure, it's necessarily possible (although rarely desirable) to set one for the security-updates repository as well. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: help in purging old packages
On 09/01/15 11:23 AM, Comer Duncan wrote: Hi, I have a situation in which I am running wheezy 7.7 and for various reasons now want to purge all packages which for some reason are still present from etch, lenny, and squeeze. What I would like to know is how can I purge all such packages using dpkg? I can not seem to find how to select just those old packages for purging. Can those who know about this please help? Thanks. Check out aptitude autoclean and aptitude clean. Or you can install deborphan. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b04b87.1020...@torfree.net
Re: Have I been hacked?
On Fri, Jan 09, 2015 at 10:49:49AM -0500, Jerry Stuckle wrote: snip... > > SSH passwords are very safe, if they are long enough. For instance, if > you have a 10 character password, mixed case and numbers (no special > characters), a brute force attack of 100 attempts per second would take > almost 266 million years to cover all possibilities. 11 characters > would take over 16 billion years - longer than the life of the universe. That's the key phrase, "to cover all possibilities" Don't forget, it's possible to hit pay dirt on the first try...or the 3rd...or the 20th... or the 500th...or the 50,000th...or the last possibility. I constantly hear references to mind boggling lengths of time required to crack passwords/phrases. I think it's misleading, especially to a beginner. On the other hand I have to admit I can't come up with a better way. ...snip.. -- Bob Holtzman Giant intergalactic brain-sucking hyperbacteria came to Earth to rape our women and create a race of mindless zombies. Look! It's working! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109213704.ga32...@cox.net
Re: How can g++ (stable) be incompatible with a fresh stable install?
Kynn Jones wrote:
> On Thu, Jan 8, 2015 at 7:18 PM, Sven Hartge wrote:
>> Kynn Jones wrote:
>>> libc6-dev:
>>> Installed: (none)
>>> Candidate: 2.13-38+deb7u4
>>> Version table:
>>> 2.19-13 0
>>> 750 http://debian.csail.mit.edu/debian/ testing/main amd64
>>> Packages
>>> 750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
>>> 50 http://debian.csail.mit.edu/debian/ unstable/main amd64
>>> Packages
>>> 50 http://ftp.us.debian.org/debian/ unstable/main amd64
>>> Packages
>>> 2.13-38+deb7u6 0
>>> 995 http://debian.csail.mit.edu/debian/ stable/main amd64
>>> Packages
>>> 995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
>>> 2.13-38+deb7u4 0
>>>1000 http://security.debian.org/ stable/updates/main amd64
>>> Packages
>>
>> Your priorities for the different versions seem off. Security should
>> have to same priority as stable, not a higher one.
>>
>> And security should not need a higher priority, because security updates
>> (not already included via point-release) will always have a higher
>> version than the non-security package from the normal repository.
> OK, I thought I understood what was going on, but it turns out that
> I'm more baffled than ever. (E.g. I don't understand why I'm given
> the *option* of setting a priority for security when in fact, if I
> understand you correctly, there's only one sensible setting for it,
> namely "identical to stable"...)
The option exists because there might be a use case for someone
somewhere. Just because an option is useless for you does not mean it is
useless for everybody.
>> Please post the content of /etc/apt/preferences and any file in
>> /etc/apt/preferences.d
> As I mentioned in my original post, my configs for
> /etc/apt/{sources.list,preferences}.d are based on those given here
> http://serverfault.com/a/382101.
Ouch. Please do _not_ follow that guide. The pinnings shown there are
dangerous and wrong, as you have seen. Please remove them from your
system. Please also remove any sources.list files with testing/jessie or
unstable/sid from your configuration until you have configured the
preferences correctly.
> It may have been unwise of me to follow those recommendations, but
> they are the best (actually, the only) ones I was able to find when I
> searched for apt configuration "best practices". (I will resume my
> search now, of course.)
It is true that the pinning feature is under-documented and a bit
"arcane" to use. This may be because the normal user never has any need
of changing them.
What do you want to accomplish? To have some packages from Testing but
the majority of the system to remain Stable?
Then just pin testing to a value between 0 and 100 to prevent an
automatic upgrade of every package to the testing version.
To do so, please delete every preferences fil from
/etc/apt/preferences.d and just put on file with the following content
inside:
Package: *
Pin: release n=jessie
Pin-Priority: 50
You then can reenable any apt-sources for jessie.
This has the following effects:
a) All packages from Stable will automatically get a prio of 500
b) All packages from Jessie will get a prio of 50
Packages with a priorioty lower than 100 will never be installed unless
1) a dependency requests this or 2) the admin tells apt-get to do so.
To install a package, you then use "apt-get -t jessie install package".
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/6b9s301ba...@mids.svenhartge.de
Re: Have I been hacked?
On 01/09/2015 11:29 AM, Danny wrote: I am an Aircraft Engineer by trade not a Computer Scientist Have you considered that alone would make you a tasty bit to hack, and for that reason, if you have anything tasty on your machine, you REALLY need to clear it up soonest with a complete re-install. I'd add a measure of panic to that level of concern. No need for the black hats to have access at all. :) Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. Linux user# 44256 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b021fc.6080...@gmail.com
Re: Have I been hacked?
On Fri 09 Jan 2015 at 16:19:39 +, Eduardo M KALINOWSKI wrote: > On Sex, 09 Jan 2015, Jerry Stuckle wrote: > >SSH passwords are very safe, if they are long enough. For instance, if > >you have a 10 character password, mixed case and numbers (no special > >characters), a brute force attack of 100 attempts per second would take > >almost 266 million years to cover all possibilities. 11 characters > >would take over 16 billion years - longer than the life of the universe. > > If the characters are random, that is. > > The problem is that passwords are often not really random. So even > seemingly secure passwords may be guessed relatively easy. This > article gives a good overwiew about this topic: > http://arstechnica.com/security/2013/05/how-crackers-make-minced-meat-out-of-your-passwords/ Please note that this excellent article describes off-line cracking. The number of attempts per second is limited only by the machinery at hand. The 100 attempts per second for on-line cracking isn't something which can be increased to the same level. Jerry's argument still holds up. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/09012015175110.acd723095...@desktop.copernicus.demon.co.uk
Re: How can g++ (stable) be incompatible with a fresh stable install?
On Thu, Jan 8, 2015 at 7:18 PM, Sven Hartge wrote:
> Kynn Jones wrote:
>
>> libc6-dev:
>> Installed: (none)
>> Candidate: 2.13-38+deb7u4
>> Version table:
>> 2.19-13 0
>> 750 http://debian.csail.mit.edu/debian/ testing/main amd64
>> Packages
>> 750 http://ftp.us.debian.org/debian/ testing/main amd64 Packages
>> 50 http://debian.csail.mit.edu/debian/ unstable/main amd64
>> Packages
>> 50 http://ftp.us.debian.org/debian/ unstable/main amd64 Packages
>> 2.13-38+deb7u6 0
>> 995 http://debian.csail.mit.edu/debian/ stable/main amd64
>> Packages
>> 995 http://ftp.us.debian.org/debian/ stable/main amd64 Packages
>> 2.13-38+deb7u4 0
>>1000 http://security.debian.org/ stable/updates/main amd64
>> Packages
>
> Your priorities for the different versions seem off. Security should
> have to same priority as stable, not a higher one.
>
> And security should not need a higher priority, because security updates
> (not already included via point-release) will always have a higher
> version than the non-security package from the normal repository.
OK, I thought I understood what was going on, but it turns out that
I'm more baffled than ever. (E.g. I don't understand why I'm given
the *option* of setting a priority for security when in fact, if I
understand you correctly, there's only one sensible setting for it,
namely "identical to stable"...)
> Please post the content of /etc/apt/preferences and any file in
> /etc/apt/preferences.d
As I mentioned in my original post, my configs for
/etc/apt/{sources.list,preferences}.d are based on those given here
http://serverfault.com/a/382101. It may have been unwise of me to
follow those recommendations, but they are the best (actually, the
only) ones I was able to find when I searched for apt configuration
"best practices". (I will resume my search now, of course.)
As far as /etc/apt/preferences.d goes, my configs are exactly as
suggested in that post. Specifically:
(no /etc/apt/preferences file)
==> /etc/apt/preferences.d/security.pref <==
Package: *
Pin: release l=Debian-Security
Pin-Priority: 1000
==> /etc/apt/preferences.d/stable.pref <==
Package: *
Pin: release a=stable
Pin-Priority: 995
==> /etc/apt/preferences.d/testing.pref <==
Package: *
Pin: release a=testing
Pin-Priority: 750
==> /etc/apt/preferences.d/unstable.pref <==
Package: *
Pin: release a=unstable
Pin-Priority: 50
==> /etc/apt/preferences.d/experimental.pref <==
Package: *
Pin: release a=experimental
Pin-Priority: 1
Thank you for your comments. I much appreciate them.
kj
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAFvQaj4o0pYUHzJB87nwUQD=8orhHH3X5D=biwgGsQrRrE=r...@mail.gmail.com
Re: Have I been hacked?
On Fri 09 Jan 2015 at 10:41:02 -0500, Jerry Stuckle wrote: > On 1/8/2015 3:02 PM, Brian wrote: > > > > If you have resorted to using iptables you have lost it. A standard > > Debian install doesn't need it. > > I disagree. iptables is a great tool for blocking unwanted connections. > > What do you have against it? I have nothing against it and, in fact, agree with you. I'll enlarge on my sketchy remarks. The OP installs Debian with (say) Gnome. There are no listening services so there is no need to block any connections. If it happened that sshd was installed at the same time (or later) the use of ssh keys or a very strong password for authentication is sufficient to protect the service. However, there can be a big annoyance factor when attempts to log on the server take place. Software like fail2ban (which uses iptables) can be some comfort here and will at least reduce the noise in auth.log. Last year this machine saw about 4000 such random connections. I don't know how typical that is but none of them caused me to lose any sleep. Iptables can do a great job blocking unwanted connections. If someone wants to use it as a way of obtaining peace of mind, that's fine. But it doesn't add one iota of security to a well-set-up and well-managed sshd. With more services running the need is to understand their different security needs. Substituting the use of iptables for understanding isn't (IMO) something that needs to be top of the list. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109175103.ga15...@copernicus.demon.co.uk
Re: help in purging old packages
> If you want to purge all packages which have been uninstalled but for > which configuration remains: aptitude purge ?config-files > > If you want to purge all packages which are installed but which no > longer have a candidate in debian: aptitude purge ?obsolete > > If you want to purge all packages which are installed and installable, > but where the version is the same as in an earlier release... that's > probably going to need some scripting :) > Also a good way: Install package deborphan, then run aptitude purge `deborphan --guess-all`. Be carefull, what it wants do deinstall. However, I am using it regularly and it did not deinstall accidently a package, I did not want to be deinstalled. Ok, might be, I was lucky. If it does, I would just reinstall it. I suggest, just to take a look and then decide for yourself. Best regards Hans signature.asc Description: This is a digitally signed message part.
Re: Have I been hacked?
On 1/9/2015 11:19 AM, Eduardo M KALINOWSKI wrote: > On Sex, 09 Jan 2015, Jerry Stuckle wrote: >> SSH passwords are very safe, if they are long enough. For instance, if >> you have a 10 character password, mixed case and numbers (no special >> characters), a brute force attack of 100 attempts per second would take >> almost 266 million years to cover all possibilities. 11 characters >> would take over 16 billion years - longer than the life of the universe. > > If the characters are random, that is. > That's just good security practice. > The problem is that passwords are often not really random. So even > seemingly secure passwords may be guessed relatively easy. This article > gives a good overwiew about this topic: > http://arstechnica.com/security/2013/05/how-crackers-make-minced-meat-out-of-your-passwords/ > > If you don't follow good security practices, it's your own fault if you get hacked. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b00528.2040...@gmail.com
Re: help in purging old packages
On Fri, Jan 09, 2015 at 11:23:17AM -0500, Comer Duncan wrote: >Hi, > >I have a situation in which I am running wheezy 7.7 and for various >reasons now want to purge all packages which for some reason are still >present from etch, lenny, and squeeze. What I would like to know is how >can I purge all such packages using dpkg? I can not seem to find how to >select just those old packages for purging. Can those who know about this >please help? If you want to purge all packages which have been uninstalled but for which configuration remains: aptitude purge ?config-files If you want to purge all packages which are installed but which no longer have a candidate in debian: aptitude purge ?obsolete If you want to purge all packages which are installed and installable, but where the version is the same as in an earlier release... that's probably going to need some scripting :) > >Thanks. signature.asc Description: Digital signature
help in purging old packages
Hi, I have a situation in which I am running wheezy 7.7 and for various reasons now want to purge all packages which for some reason are still present from etch, lenny, and squeeze. What I would like to know is how can I purge all such packages using dpkg? I can not seem to find how to select just those old packages for purging. Can those who know about this please help? Thanks.
Re: Have I been hacked?
On Sex, 09 Jan 2015, Jerry Stuckle wrote: SSH passwords are very safe, if they are long enough. For instance, if you have a 10 character password, mixed case and numbers (no special characters), a brute force attack of 100 attempts per second would take almost 266 million years to cover all possibilities. 11 characters would take over 16 billion years - longer than the life of the universe. If the characters are random, that is. The problem is that passwords are often not really random. So even seemingly secure passwords may be guessed relatively easy. This article gives a good overwiew about this topic: http://arstechnica.com/security/2013/05/how-crackers-make-minced-meat-out-of-your-passwords/ -- Eduardo M KALINOWSKI edua...@kalinowski.com.br -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109161939.horde.0abxbzwnoqt8_zsbyxhd...@mail.kalinowski.com.br
Re: Have I been hacked?
On 1/9/2015 11:29 AM, Danny wrote: >> If you want to inspect further, I would suggest you look at each of the >> jobs being run. See if they are what you expect them to be. Also check >> your /etc/crontab and /etc/anacrontab to see what is in them. > > I would love to investigate further but I am afraid I am not inclined towards > forensics ... lol ... I am an Aircraft Engineer by trade not a Computer > Scientist ... :) ... I played around with sleuthkit but that confused the > living > hell out of me ... lol ... I don't even know what to look for ... The server I > have is a small community/family server that gives wireless access to poor > families ... > >> >> As for the attacks - I've seen a big uptake in the attacks over the last >> couple of weeks. The worst I've seen is > 100 IP's locked out in one 24 >> hour period. They are coming from all over the world, although since >> there are a lot of proxies (many of them from trojans/viruses installed >> on unsuspecting machines), there's no easy way to tell what the real >> origins are. > > It's astonishing how quick they can find an IP ... > >> I have permanently blocked the IP ranges of some of the worst offenders, >> but the only real way to stop it is to take your machine off the >> internet completely. >> >> Just ensure you're using good security practices - don't allow root >> login, use long, random passwords, etc. I also use a random character >> strings for the login ids, as well as passwords - just one more thing >> for the hackers to have to figure out how to get around. > > That's the problem right there ... random passwords ... lol ... but I will > have > to adapt ... > > Thank You > > Yes, randomizing your passwords is important - as is not using the same password on multiple systems. One trick I use is to take a long phrase and use the first (or second or third...) letter of each word. Then capitalize certain characters. For instance, if you used "To be or not to be, that is the question". Your password could be something like 2bOn2BtiTq (capitalizing every 3rd character). It's a lot easier to remember a phrase than a bunch of random characters. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54aff9e5.1020...@gmail.com
Re: Have I been hacked?
On 1/9/2015 4:25 AM, Martin Steigerwald wrote: > Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: >> On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: >>> Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: Just ensure you're using good security practices - don't allow root login, use long, random passwords, etc. I also use a random character strings for the login ids, as well as passwords - just one more thing for the hackers to have to figure out how to get around. >>> >>> Only allow SSH key based logins. Of course, only after you copied a public >>> key onto the machine with ssh-copy-id. >>> >>> And have SSH keys with *strong* passphrases, to protect against someone >>> stealing your key. Use ssh-agent wisely only on trusted machines. >> >> SSH password logins are just as safe. 20 characters gives a strong >> password for use on trusted machines. There is no need to worry about >> it being stolen because it is in your memory, > > I think SSH keys are safer, cause there is no password at all that can be > brute forced. Okay, one can try to guess the key, but try that with a 4096 > bit > key. > SSH passwords are very safe, if they are long enough. For instance, if you have a 10 character password, mixed case and numbers (no special characters), a brute force attack of 100 attempts per second would take almost 266 million years to cover all possibilities. 11 characters would take over 16 billion years - longer than the life of the universe. The biggest disadvantage of using keys is it limits the machines you can access the server from. That's not good if you need to access the server and you're not near your machine. > Anyway, I will unsubscribe now. > > Staying on this list has not been beneficial for me. > > The amount of traffic on this list, that is not related to Debian or is > bickering like this is soo high that I find it too time consuming to find out > the rare gems of threads where I can still learn something new about Debian > or > that I enjoy in engaging and replying to. > > Don´t bother to answer. I will likely delete it. > > Ciao, > If a little off-topic discussion bothers you, then it probably is best you unsubscribe. Personally, I've learned a lot just from reading this list. Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54aff89d.4000...@gmail.com
Re: Have I been hacked?
On 1/8/2015 3:02 PM, Brian wrote: > > If you have resorted to using iptables you have lost it. A standard > Debian install doesn't need it. > > I disagree. iptables is a great tool for blocking unwanted connections. What do you have against it? Jerry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54aff68e.8020...@gmail.com
Re: Are these Jessie installer images hybrid images?
Lisi wrote: >On Friday 09 January 2015 14:19:52 Steve McIntyre wrote: >> In article <201501091406.08420.lisi.re...@gmail.com> you write: >> >Are these Jessie installer images hybrid images? It appears not, but I >> >thought all Debian installer images were now. >> > >> >https://www.debian.org/devel/debian-installer/ > >Thanks, Steve. That's great. > >> All the bootable amd64 and i386 images are hybrid, yes. (i.e. disc 1 >> in each set and the netinst). What makes you think they're not, OOI? > >Purely that I could find no mention of it and it explicitly says "CD" >and "DVD", with no mention of anything else that I could see. It may be my >sight that is at fault again! No problem. :-) I was just checking that we hadn't found a new bug, that's all! -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1y9bzw-0004d8...@mail.einval.com
Re: Are these Jessie installer images hybrid images?
On Friday 09 January 2015 14:19:52 Steve McIntyre wrote: > In article <201501091406.08420.lisi.re...@gmail.com> you write: > >Are these Jessie installer images hybrid images? It appears not, but I > >thought all Debian installer images were now. > > > >https://www.debian.org/devel/debian-installer/ Thanks, Steve. That's great. > All the bootable amd64 and i386 images are hybrid, yes. (i.e. disc 1 > in each set and the netinst). What makes you think they're not, OOI? Purely that I could find no mention of it and it explicitly says "CD" and "DVD", with no mention of anything else that I could see. It may be my sight that is at fault again! Lisi. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501091522.21536.lisi.re...@gmail.com
RE: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
> Sorry, Wayne. I have done it yet again. Clicked "reply" in the Debian list. > I should have pressed "l" and replied to the list, not you personally. > :-( > Lisi > > Hi, Wayne, > > Welcome to Debian! Good choice! And also welcome to the list. Thank you. So far I am liking what I see. > On Friday 09 January 2015 06:07:52 Wayne Hartell wrote: > > Thanks. I'm sure to violate some conventions here in reply format or > > what have you. Just let me know if I do and I'll try to remedy in future. > > You have a basic underlying problem: Your email client does not quote > correctly. I had a look. You are running Outlook. All I can say is: bad luck! But > your quoting is a bit of a mess and I tried to sort it out for my reply, but it is too > early in the morning (I am on GMT and had a late night.). So we all just have to > be patient. Most of us have been there, done that and got the T-shirt. There > are lots of super Linux email clients out there. Yes, you're right I am using Outlook since I've signed up to this list on a virtual machine that is configured for taking on the road for my work. I haven't yet taken a look at Evolution and others e-mail clients, but I fear that I'll be stuck on Outlook for a little while longer, until I convince myself to make a permanent switch. Hopefully this is a little better in terms of what is expected on the list. I edited a couple of settings to try to improve things. > Once you are on a civilised email client, bottom posting, or even better, > interleaving, is preferred. With suitable trimming, of course. (Which I am not > very good at myself.) I'm sure I'll take a while to look anything but amateur. > > Now, the problem [snip] is that > > when I attempt to play an mp3 file using vlc, where that mp3 file is > > located on a password protected Windows share, vlc fails to play the file. > > > > "VLC is unable to open the MRL" (I have more detailed debug output if > > needed). > > > > Now, I have tried a newer version of VLC from the backports (2.1.2 I > > think), and it did not help. > > > > The work around is to edit the smb:.mp3 to be > > smb://user:password@//.mp3 > > > > When I do this, it will work, but I have to do it for every file I add > > to the play list. > > > > Rhythm Box appears to work just fine. > [snip] > > > > Anyway, I appreciate you taking the time to respond to my post. This > > may seem a little trivial, > > If you use vlc frequently and it does this every time, that is not trivial!! > > I can't really be any help at all, since I don't use vlc and have no Windows in the > house so don't use Samba, but you only had one reply and it didn't feel very > welcoming. Agreed; it's not trivial if that's what you are trying to do. Right now listening to music is not high on my agenda; it just jumped out at me as something that should probably work off the bat, especially when there seems to be no other samba related issues. I may end up just logging the issue when I am confident I understand the process and am not just wasting other people's time. Cheers, Wayne. > > but it's my first serious foray into Linux, just a couple of days old, > > and rather than run from issues I want to learn not only how to tackle > > the issues, but the processes that go along with Debian in general. > > :-)) > > Lisi > > > Wayne Hartell wrote: > > > I'm a new Debian/Linux user and brand new to this mailing list. > > > > Welcome. > > > > > To that end I have been tinkering with various Linux distros and I > > > have found a reproducible issue in Wheezy ... > > > > Please report it as a bug. > > > > https://www.debian.org/Bugs/ > > > > > that I wish to discuss on the Debian user Forums, but I appear to be > > > unable to register. Every IP I try I appears to be black-listed. I > > > even attempted using TOR and those IPs were also black-listed. The > > > problem is I can't post to the forums to tell them I can't register. > > > I can't find anything on Google about this > > > > problem. > > > > I for one don't like web forums. Fortunately most of the real > > activity takes place on the mailing lists. You have subscribed to > > this mailing list and so don't need any of the web forums. Simply discuss the > problem here. > > > > > If there is a better way to report this issue please let me know. > > > > Please discuss your problem here. What problem are you having? What > > reproducible issue have you found in Wheezy? > > > > Bob > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/201501091410.39304.lisi.re...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/005701d02c1f$d4318d90$7c94a8b0$@ozemail.com.au
Re: Have I been hacked?
> > You have completely failed to understand what fail2ban is telling you. > > > Anyway, I have decided to get new hardware and do a clean install of > > everything > > ... as many of you have suggested ... > > It was heading that way so it is probably best for you. > You sound like a heartless Seargeant Major in the Marines ... ;) ... > > However, as I fly a lot internationally, is there a way I can temporarily > > block > > these country's IP's for a few days at most untill I have enough time on > > hand to do a fresh install ... > > What has flying got to do with it? > What I meant was that I fly a lot and don't have time in the immediate future to do a fresh install ... So I wanted a temporary stop-gap solution for a few days untill time would lend itself for the task ... > > Currently my iptables looks like this ... > > If you have resorted to using iptables you have lost it. A standard > Debian install doesn't need it. > Yip ... definately a Seargeant Major ... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109164451.GE17386@fever.havannah.local
Re: Have I been hacked?
*me* < blushing > > Why? > > If you don't know anyone in China, don't pick up the phone. Why are > your services responding to them? > > You're not seriously telling us you're accepting user name and password > for ssh authentication from the Internet, are you? > Uhm ... yes ... (looking down ashamed ...) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109163909.GD17386@fever.havannah.local
Re: Have I been hacked?
> Blocking a country which is famous for producing chocolate and beer. > What is the world coming to? rofl :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109163622.GC17386@fever.havannah.local
Re: Have I been hacked?
So Many?? > For instance here is a list of the blocks for Belgium: > http://www.nirsoft.net/countryip/be.html > > -Joris > Feel sorry for iptables ;) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109163429.GB17386@fever.havannah.local
Re: Have I been hacked?
> If you want to inspect further, I would suggest you look at each of the > jobs being run. See if they are what you expect them to be. Also check > your /etc/crontab and /etc/anacrontab to see what is in them. I would love to investigate further but I am afraid I am not inclined towards forensics ... lol ... I am an Aircraft Engineer by trade not a Computer Scientist ... :) ... I played around with sleuthkit but that confused the living hell out of me ... lol ... I don't even know what to look for ... The server I have is a small community/family server that gives wireless access to poor families ... > > As for the attacks - I've seen a big uptake in the attacks over the last > couple of weeks. The worst I've seen is > 100 IP's locked out in one 24 > hour period. They are coming from all over the world, although since > there are a lot of proxies (many of them from trojans/viruses installed > on unsuspecting machines), there's no easy way to tell what the real > origins are. It's astonishing how quick they can find an IP ... > I have permanently blocked the IP ranges of some of the worst offenders, > but the only real way to stop it is to take your machine off the > internet completely. > > Just ensure you're using good security practices - don't allow root > login, use long, random passwords, etc. I also use a random character > strings for the login ids, as well as passwords - just one more thing > for the hackers to have to figure out how to get around. That's the problem right there ... random passwords ... lol ... but I will have to adapt ... Thank You -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150109162948.GA17386@fever.havannah.local
Re: Are these Jessie installer images hybrid images?
In article <201501091406.08420.lisi.re...@gmail.com> you write: >Are these Jessie installer images hybrid images? It appears not, but I >thought all Debian installer images were now. > >https://www.debian.org/devel/debian-installer/ All the bootable amd64 and i386 images are hybrid, yes. (i.e. disc 1 in each set and the netinst). What makes you think they're not, OOI? -- Steve McIntyre, Cambridge, UK.st...@einval.com "...In the UNIX world, people tend to interpret `non-technical user' as meaning someone who's only ever written one device driver." -- Daniel Pead -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1y9apo-0007vt...@mail.einval.com
Re: Unable to join the Debian User Forum; appears that all IPs are being black-listed.
Sorry, Wayne. I have done it yet again. Clicked "reply" in the Debian list. I should have pressed "l" and replied to the list, not you personally. :-( Lisi Hi, Wayne, Welcome to Debian! Good choice! And also welcome to the list. On Friday 09 January 2015 06:07:52 Wayne Hartell wrote: > Thanks. I'm sure to violate some conventions here in reply format or what > have you. Just let me know if I do and I'll try to remedy in future. You have a basic underlying problem: Your email client does not quote correctly. I had a look. You are running Outlook. All I can say is: bad luck! But your quoting is a bit of a mess and I tried to sort it out for my reply, but it is too early in the morning (I am on GMT and had a late night.). So we all just have to be patient. Most of us have been there, done that and got the T-shirt. There are lots of super Linux email clients out there. Once you are on a civilised email client, bottom posting, or even better, interleaving, is preferred. With suitable trimming, of course. (Which I am not very good at myself.) [snip] > Now, the problem [snip] is that > when I attempt to play an mp3 file using vlc, where that mp3 file is > located on a password protected Windows share, vlc fails to play the file. > > "VLC is unable to open the MRL" (I have more detailed debug output if > needed). > > Now, I have tried a newer version of VLC from the backports (2.1.2 I > think), and it did not help. > > The work around is to edit the smb:.mp3 to be > smb://user:password@//.mp3 > > When I do this, it will work, but I have to do it for every file I add to > the play list. > > Rhythm Box appears to work just fine. [snip] > > Anyway, I appreciate you taking the time to respond to my post. This may > seem a little trivial, If you use vlc frequently and it does this every time, that is not trivial!! I can't really be any help at all, since I don't use vlc and have no Windows in the house so don't use Samba, but you only had one reply and it didn't feel very welcoming. > but it's my first serious foray into Linux, just a > couple of days old, and rather than run from issues I want to learn not > only how to tackle the issues, but the processes that go along with Debian > in general. :-)) Lisi > Wayne Hartell wrote: > > I'm a new Debian/Linux user and brand new to this mailing list. > > Welcome. > > > To that end I have been tinkering with various Linux distros and I > > have found a reproducible issue in Wheezy ... > > Please report it as a bug. > > https://www.debian.org/Bugs/ > > > that I wish to discuss on the Debian > > user Forums, but I appear to be unable to register. Every IP I try I > > appears to be black-listed. I even attempted using TOR and those IPs > > were also black-listed. The problem is I can't post to the forums to > > tell them I can't register. I can't find anything on Google about this > > problem. > > I for one don't like web forums. Fortunately most of the real activity > takes place on the mailing lists. You have subscribed to this mailing list > and so don't need any of the web forums. Simply discuss the problem here. > > > If there is a better way to report this issue please let me know. > > Please discuss your problem here. What problem are you having? What > reproducible issue have you found in Wheezy? > > Bob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501091410.39304.lisi.re...@gmail.com
Are these Jessie installer images hybrid images?
Are these Jessie installer images hybrid images? It appears not, but I thought all Debian installer images were now. https://www.debian.org/devel/debian-installer/ Thanks, Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201501091406.08420.lisi.re...@gmail.com
Re: Have I been hacked?
On Thu, Jan 08, 2015 at 10:53:45PM +0200, Danny wrote: > Hi guys, > > My apologies for replying a little late ... [cut] > > As you can see ... I am already DROPping some of these IP's ... I just need > something to block an ENTIRE country ... Install xtables-addons-dkms (which will build the module for your current kernel). You can then use instructions such as those at [1] to set up xtables (basically, though, you use xt_geoip_dl to download the GeoIP database and then do something akin to "iptables -A INPUT -m geoip --src-cc CN -j DROP). [1]: http://blog.jeshurun.ca/technology/block-countries-ubuntu-iptables-xtables-geoip > > Thank you ... and thanks to everyone replying ... I apreciate it ... > > Danny > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/20150108205345.GA4732@fever.havannah.local > signature.asc Description: Digital signature
Re: Have I been hacked?
On Thursday 08 January 2015 21:53:45, Danny wrote : > Hi guys, > > So what I did was do disable all startup scripts/servers/services and then > enable only one at a time ... then I would reboot and wait and keep an eye > on "/boot" (I deleted all randomly generated files, so I could see if a > file was added or not, and it was also the only way I knew for certain > that the culprit was active or not, hence that is how I could time it) ... > > All went well untill I enabled cron ... I checked all cron jobs and they > all "look" normal ... here is an "ls" of my cron directories ... > > ### > /etc/cron.d/ > anacron atop mrtg php5 > > /etc/cron.daily/ > anacron atop mrtg php5 > > /etc/cron.hourly/ > cron.sh sarg > > /etc/cron.monthly > 0anacron sarg > > /etc/cron.weekly > 0anacron apt-xapian-index man-db sarg > ### Have a look at /etc/crontab. The file contains commands to be run by cron. The directory /var/spool/cron/crontabs also contains user's cron jobs. If anacrontab is installed, /etc/anacrontab may contain more jobs. > Since I killed cron at bootup everything seems fine ... network is back to > normal ... I don't get the transition between the above paragraph (network is normal if cron is killed) and the below paragraph (troubles begin when network is up). Do you have any evidence that cron is triggering the attack or am I misreading your mail? > However, as soon as my network was up and running I got attacked ... > here is an excerpt of one of the fail2ban mails ... > > ### > The IP 204.12.241.227 has just been banned by > Fail2Ban after > 3 attempts against ssh. > > Jan 8 04:23:15 fever sshd[17406]: Connection from 204.12.241.227 port > 38090 on 10.0.0.5 port 22 Jan 8 04:23:17 fever sshd[17406]: Invalid user > zhangyan from 204.12.241.227 Jan 8 04:23:17 fever sshd[17406]: > pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh > ruser= rhost=204.12.241.227 Jan 8 04:23:20 fever sshd[17406]: Failed > password for invalid user zhangyan from 204.12.241.227 port 38090 ssh2 Jan > 8 04:23:20 fever sshd[17406]: Received disconnect from 204.12.241.227: > 11: Bye Bye [preauth] Jan 8 04:23:20 fever sshd[17408]: Connection from > 204.12.241.227 port 39800 on 10.0.0.5 port 22 Jan 8 04:23:22 fever > sshd[17408]: Invalid user dff from 204.12.241.227 Jan 8 04:23:23 fever > sshd[17408]: pam_unix(sshd:auth): authentication failure; logname= uid=0 > euid=0 tty=ssh ruser= rhost=204.12.241.227 Jan 8 04:23:24 fever > sshd[17408]: Failed password for invalid user dff from 204.12.241.227 port > 39800 ssh2 > ## The mail is sent because someone is brute force attacking your ssh server. Not starting fail2ban or your mail server would suppress those mails but not the attack. Turning off ssh or the network would stop the attack though :-) If your line of reasoning is to correlate the mail arrival with starting cron, then maybe cron is the last link required to make the fail2ban alert functional. > What is interesting to me is the user in the above excerpt "zhangyan" ... > By using a username that is unfamiliar to the western world tells me that > whatever is on my system had to respond to this username otherwise why > would this guy use a username that only he is familiar with ... Other > usernames that were used: 3D, ssht and ftfl ... Also, attempts were made > from China, Hong Kong, Belgium and Canada ... You cannot tell something is responding to that user name on your system based only on that fail2ban alert. On the contrary, the mail means fail2ban successfully thwarted that particular attempt. Attackers can't know what names are valid login names unless they can find one by hacking into a legitimate user's computer or a user posted its login on the net. What hackers do instead, is to try a long list of possible login names collected on servers they have hacked in the past. That's the reason this particular bot was trying to login with the "zhangyan" user name. There is nothing to worry about unless you receive alerts about a valid login name. > Currently my iptables looks like this ... > > ### > > -A INPUT -p tcp -s 122.0.0.0/8 -j DROP > -A INPUT -p tcp -s 61.0.0.0/8 -j DROP > -A INPUT -p tcp -s 117.0.0.0/8 -j DROP > -A INPUT -p tcp -s 103.0.0.0/8 -j DROP > -A INPUT -p tcp -s 82.0.0.0/8 -j DROP > -A INPUT -p tcp -s 204.0.0.0/8 -j DROP > -A INPUT -p tcp -s 218.0.0.0/8 -j DROP > ### > > As you can see ... I am already DROPping some of these IP's ... I just need > something to block an ENTIRE country ... You can't ban an enti
Re: Have I been hacked?
Am Freitag, 9. Januar 2015, 00:24:06 schrieb Brian: > On Thu 08 Jan 2015 at 22:36:46 +0100, Martin Steigerwald wrote: > > Am Donnerstag, 8. Januar 2015, 14:20:27 schrieb Jerry Stuckle: > > > Just ensure you're using good security practices - don't allow root > > > login, use long, random passwords, etc. I also use a random character > > > strings for the login ids, as well as passwords - just one more thing > > > for the hackers to have to figure out how to get around. > > > > Only allow SSH key based logins. Of course, only after you copied a public > > key onto the machine with ssh-copy-id. > > > > And have SSH keys with *strong* passphrases, to protect against someone > > stealing your key. Use ssh-agent wisely only on trusted machines. > > SSH password logins are just as safe. 20 characters gives a strong > password for use on trusted machines. There is no need to worry about > it being stolen because it is in your memory, I think SSH keys are safer, cause there is no password at all that can be brute forced. Okay, one can try to guess the key, but try that with a 4096 bit key. Anyway, I will unsubscribe now. Staying on this list has not been beneficial for me. The amount of traffic on this list, that is not related to Debian or is bickering like this is soo high that I find it too time consuming to find out the rare gems of threads where I can still learn something new about Debian or that I enjoy in engaging and replying to. Don´t bother to answer. I will likely delete it. Ciao, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/3714920.DLpo8KHxcl@merkaba
