To filter a string to make sure it's a valid ip address this regexp is quite useful./^((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])$/
It really doesn't look like that will match all valid IPs, although it is very though. Surely 010.000.000.001 is still valid?
I normally use something like:/^\([0-2]\{0,1\}[0-9]\{1,2\}\.\)\{3\}[0-2]\{0,1\}[0-9]\{1,2\}$/ ( sed style, not perl style. Perl style would of course be shorter. )
Most here assembled, though not 100 percent immune, are far less susceptible than an "average" user to any sort of malware infection.
It could happen to anyone who uses windows is more accurate. I have seen smart people with current virus scanners and anti-spyware tools still suffering from DNS hijacking and spaming worms.
You only have to look at one dodgy website once. Having virus scanners and all the latest updates will not prevent infection.
:x! Many people seem to use:wq! when:x! has done the same thing for decades but gets rid of the issue of what if the write fails, does it still quit and is the ! tied to the w or the q? ZZ will also do the same thing.
You are right that most people insist on using:wq! when:x! obsoleted it in 1978.
However there is a difference,:x will not write the file where it has not changed,:wq! will write the file in any case.
Your open source software blocker is being paid off by the vendors. Maybe not in cash, might be just in dinners, trips to "conferences", or perhaps just in building his ego.
I think you are right.
I get the impression that a few free dinners is all it talks to bribe a lot of these people. A large number of middle managers are so lost in their jobs they will take guidance from anywhere.
Minor bribes are still common business practice throughout the western world. As long as it's not cash people rationalize it away as 'perks of the job'.
You can try marketing something like openssh as the best tool for the job, and point out the places you already use it. And then try pointing out all the other bits of open source that make it into windows, commercial unixes, routers, and just about everything else.
It's worth trying but you might be onto a loser anyway.
From personal experience I can tell you that the people that do well in multinationals are not qualified professionals, they are 'professional manager' idiots who 'talk the talk'. These people care about money, reputation and thats all. Sadly multinationals provide lots of places for these kind of people.
Try convincing people the value of using the best tool for the job, it's certainly worth a shot. Then if that doesn't work either put up with it or look for somewhere better to work. The other option is to use whatever you like and neglect to tell them. Chances are they are too dumb to notice anyway.
I am thinking that they are starting to try to wean people off of FW because USB3 is on the cusp of becoming available in consumer devices. It will likely replace both USB2 and FW.
Either that or they are trying to wean people off firewire before they get their asses sued for supporting such an insecure system. Firewire makes it easy to build a small device that will dump all physical memory onto a small device. Password hashes, passwords, passphrases, private keys, and kerberos tickets are all on offer.
I know there is no security without physical security but normally you can't dump all physical memory from a running system without a kernel level or hardware hack.
If you give something to someone else you are no longer in control of it. Email is a critical business tool, I'll not be giving mine away any time soon.
4GB is the maximum RAM that can be addressed by a 32 bit pointer, it's not a limit on the total ram in a 32 bit system since physical address extention ( PAE ) extends it by a few more pins.
The fact that DES passwords are 8 characters long and anything over the first 8 is silently ignored is well known.
Am I alone here in remembering the old slashdot? It used to be IT stories for IT professionals and hobbyists. Now it's dumbed down stories for help desk wannabes.
Whats next? A story on how the letters look weird with the caps lock on?
Added to that, it's not especially difficult getting Unix machines to talk to AD for authentication and other information (it's just LDAP, after all).
And thats the open source attitude and why we are always getting screwed over by microsoft.
It's not just LDAP once they get their filty paws on it, it's a twisted version designed to work 80% of the time and make it look like the non-microsoft end is screwing up the other 20%. Microsoft can't do open standards. They have a hard enough time keeping boxes up long enough to do anything at all.
Yes I have seen AD used for linux authentication. It's totally unreliable, use anything else but not AD. Use a real LDAP server or local files distributed by scp, anything but AD.
If you want something very well supported, not horribly difficult to administer in a simple environment and tried and true, just go with Active Directory and Exchange, especially if your company's focus is on something other than providing unique technology solutions. (i.e. you sell baskets)
While the open source solution might cost less up front, there is nothing in open sourece land at present that can touch the Exchange/Outlook combination. Sure, there are products such as OpenExchange, but, let's assume that you want the option to easily add other services later on, such as true handheld synchronization (i.e. www.good.com)
You want to tell that to the 1000+ users I have that could not work for a week because of AD crashing every few kinit's?
Don't go near AD for any environment except maybe a very small windows only one. It's full of application holes that somehow manage to cause OS downtime.
It's not even nearly stable in large environments. I've seen replication stop for no reason, servers crash for no reason, the performance is shockingly bad. It can also tarpit the ldap port when it gets busy, leaving your clients hanging.
It also takes microsoft around a month to fix bugs that cause random reboots, even then private fixes can cause more problems than they fix.
Local passwd files are better than AD. Way better.
Sooner or later paypal shaft everyone they deal with. They are the SCO of the banking world.
They freeze funds and keep the money whenever they feel like it, they take random amounts out of peoples credit cards whenever they feel like it, and they send a pack of lies to their debt collection agencies about their own customers whenever they feel like it.
Warning from real life experience, DON'T DEAL WITH PAYPAL!!
Slashdot Mirror
To filter a string to make sure it's a valid ip address this regexp is quite useful. /^((25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])\.){3}(25[0-5]|2[0-4][0-9]|1[0-9][0-9]|[1-9][0-9]|[0-9])$/
It really doesn't look like that will match all valid IPs, although it is very though. Surely 010.000.000.001
is still valid?
I normally use something like: /^\([0-2]\{0,1\}[0-9]\{1,2\}\.\)\{3\}[0-2]\{0,1\}[0-9]\{1,2\}$/
( sed style, not perl style. Perl style would of course be shorter. )
Most here assembled, though not 100 percent immune, are far less susceptible than an "average" user to any sort of malware infection.
It could happen to anyone who uses windows is more accurate. I have seen smart people with current virus scanners and anti-spyware tools still suffering from DNS hijacking and spaming worms.
You only have to look at one dodgy website once. Having virus scanners and all the latest updates will not prevent infection.
:x! :wq! when :x! has done the same thing for decades but gets rid of the issue of what if the write fails, does it still quit and is the ! tied to the w or the q? ZZ will also do the same thing.
Many people seem to use
You are right that most people insist on using :wq! when :x! obsoleted it in 1978.
However there is a difference, :x will not write the file where it has not changed, :wq! will write the file in any case.
encrypt:
openssl aes-256-cbc -a -e -salt -in INPUT_FILENAME -out OUTPUT_FILENAME
decrypt:
openssl aes-256-cbc -a -d -salt -in INPUT_FILENAME -out OUTPUT_FILENAME
echo Oe lbh pna vzcyrzrag UK tbireazrag fgnaqneq rapelcgvba jvgu ge | tr a-z n-za-m
Your open source software blocker is being paid off by the vendors. Maybe not in cash, might be just in dinners, trips to "conferences", or perhaps just in building his ego.
I think you are right.
I get the impression that a few free dinners is all it talks to bribe a lot of these people. A large number of middle managers are so lost in their jobs they will take guidance from anywhere.
Minor bribes are still common business practice throughout the western world. As long as it's not cash people rationalize it away as 'perks of the job'.
You can try marketing something like openssh as the best tool for the job, and point out the places you already use it. And then try pointing out all the other bits of open source that make it into windows, commercial unixes, routers, and just about everything else.
It's worth trying but you might be onto a loser anyway.
From personal experience I can tell you that the people that do well in multinationals are not qualified professionals, they are 'professional manager' idiots who 'talk the talk'. These people care about money, reputation and thats all. Sadly multinationals provide lots of places for these kind of people.
Try convincing people the value of using the best tool for the job, it's certainly worth a shot. Then if that doesn't work either put up with it or look for somewhere better to work. The other option is to use whatever you like and neglect to tell them. Chances are they are too dumb to notice anyway.
Why not check what the SLA says you are entitled to, which will be what you paid, i.e. nothing.
You get what you pay for or what you build yourself.
I am thinking that they are starting to try to wean people off of FW because USB3 is on the cusp of becoming available in consumer devices. It will likely replace both USB2 and FW.
Either that or they are trying to wean people off firewire before they get their asses sued for supporting such an insecure system. Firewire makes it easy to build a small device that will dump all physical memory onto a small device. Password hashes, passwords, passphrases, private keys, and kerberos tickets are all on offer.
I know there is no security without physical security but normally you can't dump all physical memory from a running system without a kernel level or hardware hack.
If you give something to someone else you are no longer in control of it. Email is a critical business tool, I'll not be giving mine away any time soon.
they let me listen to my music on a train at a dramatically reduced volume.
Works for me too, they really work great. Now I get to work without hearing anyone and without ringing in my ears from loud music.
4GB is the maximum RAM that can be addressed by a 32 bit pointer, it's not a limit on the total ram in a 32 bit system since physical address extention ( PAE ) extends it by a few more pins.
Google for PAE.
Thats the ugliest webpage I've seen for a very long time.
Adverts look pretty after looking at that.
Slashdot - Microsoft new for windows fanboys.
You could always fix your pam stack instead of adding limitations to AD.
The fact that DES passwords are 8 characters long and anything over the first 8 is silently ignored is well known.
Am I alone here in remembering the old slashdot? It used to be IT stories for IT professionals and hobbyists. Now it's dumbed down stories for help desk wannabes.
Whats next? A story on how the letters look weird with the caps lock on?
Added to that, it's not especially difficult getting Unix machines to talk to AD for authentication and other information (it's just LDAP, after all).
And thats the open source attitude and why we are always getting screwed over by microsoft.
It's not just LDAP once they get their filty paws on it, it's a twisted version designed to work 80% of the time and make it look like the non-microsoft end is screwing up the other 20%. Microsoft can't do open standards. They have a hard enough time keeping boxes up long enough to do anything at all.
Yes I have seen AD used for linux authentication. It's totally unreliable, use anything else but not AD. Use a real LDAP server or local files distributed by scp, anything but AD.
If you want something very well supported, not horribly difficult to administer in a simple environment and tried and true, just go with Active Directory and Exchange, especially if your company's focus is on something other than providing unique technology solutions. (i.e. you sell baskets)
While the open source solution might cost less up front, there is nothing in open sourece land at present that can touch the Exchange/Outlook combination. Sure, there are products such as OpenExchange, but, let's assume that you want the option to easily add other services later on, such as true handheld synchronization (i.e. www.good.com)
You want to tell that to the 1000+ users I have that could not work for a week because of AD crashing every few kinit's?
Don't go near AD for any environment except maybe a very small windows only one. It's full of application holes that somehow manage to cause OS downtime.
Don't go near AD for unix authentication.
It's not even nearly stable in large environments. I've seen replication stop for no reason, servers crash for no reason, the performance is shockingly bad. It can also tarpit the ldap port when it gets busy, leaving your clients hanging.
It also takes microsoft around a month to fix bugs that cause random reboots, even then private fixes can cause more problems than they fix.
Local passwd files are better than AD. Way better.
Paypal have been freezing funds of private sales and keeping the money for years now. It's amazing how they have gotten away with it for so long.
Maybe this whole thing is just a scam to collect more credit card numbers to abuse.
PayPal can expand their services to more countries...
So they can shaft their customers on a more global scale...
PayPal can't be trusted, not with 1 penny in any currency. Check out paypalsucks.com
Sooner or later paypal shaft everyone they deal with. They are the SCO of the banking world.
They freeze funds and keep the money whenever they feel like it, they take random amounts out of peoples credit cards whenever they feel like it, and they send a pack of lies to their debt collection agencies about their own customers whenever they feel like it.
Warning from real life experience, DON'T DEAL WITH PAYPAL!!
While you are at it invent books that can be read in any language that don't use words.
Somewhere in microshaft HQ:
cat ReiserFS | sed 's/Reiser/WIN/g'
Bill! We have innovated again!
I thought there were restrictions on exporting Linux from the US to Iraq (which somehow mysteriously don't apply to MS)?
Maybe the regulations only affect secure software?
So import linux from elsewhere.
There are mirrors worldwide.
They need to let go of two more people: Darl McBride and David Boies.
Thats not really enough. People need to go to jail over this and any money made from this whole con needs to be taken out of the hands of the con men.
Otherwise what message does it send?