bloody hell, forgot my point with IBM.
When multimillion dollar installations fails and you are paying for the support + guarantee on uptime you got somewhere to send the bill if shit hits the fan.
What will you do when your PG installation fail? Go on IRC and ask for help? Tools for the job; if you are spending millions on software then go with the a company that is going to charge you millions. If you want a kick ass database for free then go with PG.
The US case was about the government wanting Google's search index and a few months worth of queries, the Brazilians are asking for specific information with specific ips and with specific date time stamps on a social networking site. Big Difference.
Preventing any sort of drm is a position that is very unnecessary. It's perfectly reasonable for a hardware or software manufacturer to create products that require specific hardware or software libraries to be installed. Preventing companies from doing that, essentially forcing companies to have products that would have to support a wide variety of h/w or s/w, seems totally unrealistic. Companies should be free to create products that work under specific conditions, and I should be free to take their source code (if it open sourced) and modify their DRMed code to try and make it work under different conditions.
Keeping passwords in text files seems like a bad idea. If you want to keep passwords safe on a networked machine you should be using something like http://keepass.sourceforge.net/.
Additionally if you are worried about key loggers never type in your password even after failed attempts, just copy and paste the letters of your password into the password field (getting the letters from a web page, or typing out the alphabet and numbers 0 to 9, etc...); this is the only way to be sure that your password will never show up on the keyboard logger.
What I think this is referring to, and I am not sure, is that when you log into banking sites these days they will normally have an additional password, and will make you type in certain characters of the password, in different sequences each time you log in. E.g. it will prompt you to type in character 4, 3 & 5 of your additional password, and then randomise that sequence again for the next time you log in.
My assumption is that what these security guys found is that in 9 attempts it is possible to reconstruct this additional password.
However calling a user with a malicious key logger on his/her system a banking security vulnerability seems totally ridiculous, there must be more to it than that.
When I went looking for a CMS that is where I first tried. This page http://www.opensourcecms.com/index.php?option=com_ content&task=view&id=388&Itemid=160 is very useful. It gives the list of CMS Ratings. People should take from the ratings it what they will.
My advice for people looking for a CMS is try them all, you will probably never find something that matches what you want, but you may come close.
Some of the things you can do with CSS
on
Dvorak Rants on CSS
·
· Score: 2, Insightful
http://csszengarden.com/ highlights some of the wonderful artistry you can do with CSS. Once people get a grasp of using CSS, going back the traditional table based layouts, and mixing content and style, is no longer an option; but CSS is far from easy to pick up. In fact initially using CSS is incredibly frustrating.
Windows remote desktop suffers from very weak authentication. The best solution to this VNC flaw and using remote machines in general is to use a VPN to ensure that authentication is managed with public key cryptography, with all data thereafter being encrypted with symmetric keys. It also means it's so much simpler to run different services without having to create separate SSH tunnels.
http://openvpn.net/ has a great solution working on all platforms.
And to add, partitioning in mysql 5.1 is probably not going to be production ready.
So is Leo Laporte: http://www.twit.tv/
The US case was about the government wanting Google's search index and a few months worth of queries, the Brazilians are asking for specific information with specific ips and with specific date time stamps on a social networking site. Big Difference.
Preventing any sort of drm is a position that is very unnecessary. It's perfectly reasonable for a hardware or software manufacturer to create products that require specific hardware or software libraries to be installed. Preventing companies from doing that, essentially forcing companies to have products that would have to support a wide variety of h/w or s/w, seems totally unrealistic. Companies should be free to create products that work under specific conditions, and I should be free to take their source code (if it open sourced) and modify their DRMed code to try and make it work under different conditions.
To start a you tube you will need:r
FFMPEG http://ffmpeg.mplayerhq.hu/: for video conversion
FlowPlayer http://flowplayer.sourceforge.net/howto.html: displaying flash video
or Flash Video Player http://jeroenwijering.com/?item=Flash_Video_Playe
FFMPEG-PHP http://ffmpeg-php.sourceforge.net/: If php is used a nice extension for getting screen shots of videos, not necessary though
flvtool2 http://rubyforge.org/projects/flvtool2/: so you can seek though the created flash file
Then all you need is leverage framework or cms in php, or phython, or something and you are done. (well sort of!)
Keeping passwords in text files seems like a bad idea. If you want to keep passwords safe on a networked machine you should be using something like http://keepass.sourceforge.net/. Additionally if you are worried about key loggers never type in your password even after failed attempts, just copy and paste the letters of your password into the password field (getting the letters from a web page, or typing out the alphabet and numbers 0 to 9, etc...); this is the only way to be sure that your password will never show up on the keyboard logger.
What I think this is referring to, and I am not sure, is that when you log into banking sites these days they will normally have an additional password, and will make you type in certain characters of the password, in different sequences each time you log in. E.g. it will prompt you to type in character 4, 3 & 5 of your additional password, and then randomise that sequence again for the next time you log in. My assumption is that what these security guys found is that in 9 attempts it is possible to reconstruct this additional password. However calling a user with a malicious key logger on his/her system a banking security vulnerability seems totally ridiculous, there must be more to it than that.
When I went looking for a CMS that is where I first tried. This page http://www.opensourcecms.com/index.php?option=com_ content&task=view&id=388&Itemid=160 is very useful. It gives the list of CMS Ratings. People should take from the ratings it what they will.
My advice for people looking for a CMS is try them all, you will probably never find something that matches what you want, but you may come close.
http://csszengarden.com/ highlights some of the wonderful artistry you can do with CSS. Once people get a grasp of using CSS, going back the traditional table based layouts, and mixing content and style, is no longer an option; but CSS is far from easy to pick up. In fact initially using CSS is incredibly frustrating.
Windows remote desktop suffers from very weak authentication. The best solution to this VNC flaw and using remote machines in general is to use a VPN to ensure that authentication is managed with public key cryptography, with all data thereafter being encrypted with symmetric keys. It also means it's so much simpler to run different services without having to create separate SSH tunnels. http://openvpn.net/ has a great solution working on all platforms.