I strongly disagree. Maybe this 4096 times applies to the traditional single DES crypt. But execept for some rare compatibilities issues with old systems or for dumb people that create Apache.htpasswd files with it, nobody uses single DES any more for years.
Passwords hashed with MD5 and Blowfish don't have the 8 character limitation. There are still some people who like to assign users passwords like "*9_p7Z9ox" even though their system doesn't use single DES any more. This is just plenty stupid. Not only it's a hell to remember for the end user, but it's damn fast to brute force when hashes are precomputed as described in this article.
A normal password like a real sentence (ex: "I'd like to have sex with Sandra") is not only way more easy to remember, it's also orders of magnitudes harder to brute force.
" there were a few areas pointed out where the open source community does not do so well, such as regression testing and setting release dates."
It really depends. Setting release dates is not mandatory for an opensource project. Those projects are not made by a company for a customer requiring a specific deadline. OSS projects are mostly made during spare time. So the most reasonnable release dates are "when the code will be completed".
Regression tests are another story, but it really depends on projects and how they are managed.
For instance OpenBSD has very strict release dates. Every 6 months. And this schedule has always been respected.
OpenBSD also always introduces regression tests for new commands or new features implemented in existing commands. Have a look at the/usr/src/regress/ directory. The tests are numerous and extensive.
IMHO the reliability of an ISP has nothing to do with the backend operating systems, especially when the study only considers the OS of the public web servers.
I'm sure that even a Win95 based ISP can provide a very reliable service. It's only a matter of redundancy.
On the other hand, the company I'm working for runs FreeBSD on its web and mail servers, but thanks to the dumb way things are installed and the lack of redundancy, a global uptime of 24 hours would be an all-time record.
With no possible single point of failure, with load balancers and correct usage of protocols like HSRP, service can be guaranteed even if some servers are continously crashing.
Have you ever seen Google unreachable? I've always seen it up. Although Google runs Linux. But they have properly designed their network for high availability. In an old Slashdot article, there was an interview of a Google techie who explained that if 1, 2 or 100 servers were down, it would have absolutely no impact on the service.
So at least for ISPs, I really think what matters is the skills of the network administrators. It brings another question : does the skills actually depends on the operating system they use?
Maybe. At least when you read mailing-lists of different operating systems, you can clearly see some common interests of the related subscribers. _This_ is really what makes differences between free operating systems. When it comes to reliability for traditional ISP services, either OpenBSD, Linux, FreeBSD or even Win2000 are quite comparable nowadays.
To get the best of two worlds, buy an iBook and Virtual PC.
Recent releases of Virtual PC are working amazingly well. Yes, it's an emulation, but no, it's not slow. Visual Studio runs flawlessly if this is what you need.
> That's probably because they don't have to. GCC isn't included with the AP.
This brings an interesting question. Should free software be redistributed with compilers that were used to generate binary packages?
If not, it would be possible to distribute source code that no one could compile. But this would still be opensource software. There's even no need to write a new compiler to do this. Encrypt the source code with GPG, say that your compiler is actually a simple wrapper that decrypts the source code before calling gcc et voila. You can distribute the encrypted source code that no one would be able to use. But this will be the real source code, so the project will be opensource.
But this is the chicken and egg problem. If opensource software should distribute the compiler that was used to generate binary packages, the compiler itself should be distributed with tools that were used to build it.
"These applications appear to adopt the "fire-and-forget" methodology. That is, they attempt to send the spam to one or several MX hosts for a domain, but then never attempt a true retry as a real MTA would."
I strongly disagree. A vaste majority of spammers actually use real mail servers like Qmail. Or strange spam-specific software with support for retries.
Apart from Spam Assassin, I'm using OpenBSD built-in "spamd" ip-based filter. A quick look at the spamd log files shows that the same spammers retry over and over, usually during 7 days.
What I like in Greylistings is that it actually prioritizes mails. A mail coming from a known source will be processed before a mail coming from an unknown source (that will have to wait for the next try) . Not really an antispam feature, but still nice to have.
I have a very positive experience with RAV Antivirus.
I'm using it daily on Windows and on corporate mail servers running Qmail on OpenBSD. No problem ever.
It is very fast, maybe 10x faster than Sophos Antivirus, and developpers are very reactive when it comes to merging new signatures to the virus database.
And the fact that it is really cross-platform and supports a lot of mail agents including Qmail is great!
The only thing I really don't like in it is the licensing scheme, based upon the number of hosted domains.
I would be very disappointed if the buyout by Microsoft removed the support for anything else than MS Exchange.
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400] Host Bridge 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 00:08.0 RAID bus controller: Promise Technology, Inc.: Unknown device 3376 (rev 02) 00:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02) 00:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74) 00:0e.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02) 00:0e.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02) 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 Audio Controller (rev 50) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon VE QY
My experiences with this mobo:
- Linux - old versions (don't remember which ones exactly, I tried a lot of kernels and various patches) : audio detected, but not working. Kernel freeze as soon as my CD writer is accessed.
- Linux 2.4.21_rc6-gss (Gentoo stable) with Alsa, ehci + uhci (not usb-uhci that crashes) : everything finally works.
- NetBSD-current : kernel freeze.
- OpenBSD 3.2-current with original BIOS : nothing worked, even disk I/O was flaky.
- OpenBSD 3.3 & current with updated BIOS : kernel freeze unless I manually disable auvia* drivers. Once auvia drivers are disabled, everything works fine except USB2 (unsupported by OpenBSD) and sound. The promise SATA controler also works in parallel mode.
- FreeBSD 5.0 and 5.1 : kernel freeze, even with the latest BIOS revision.
Fortunately, FreeBSD 5 works well with VMWare 4 on Linux.
This is stupid and obvious, but... why does Outlook allows users to execute any executable file send through email just by clicking on it?
I can understand that clicking on an attachment can open Word or Excel.
But in the real life, when do you really _need_ to send executables to your friends? Or maybe you need to send some app you designed, but in this case your friends can always save the attachement and execute it later. This is something nobody would make on untrusted mails.
Start the project at home, out of your working hours.
Make it GPL'ed. As a public proof, you can release an initial public beta version.
Back to your company, continue to work on the project. Any addition made to it must be GPL'ed as well, isn't it? So even though you are working on it while on company time, you can always release the product as free software.
Does this new boot loader finally allows to install FreeBSD on an extended dos partition ?
I don't understand why BSD never solved that issue. This is a serious showstopper for people who want to try FreeBSD and whoose hard disk already has other operating systems. I really don't want to backup and reinstall every partition of my hard disk just to see what FreeBSD 5 looks like.
Please note that on 3.3-STABLE and -current, MySQL is also finally extremely stable on OpenBSD, with native threads.
A lot of threading-related work has been made during the 3.3 development cycle and there are no more unexpected crashes with this sort of apps. For instance the new threading code solved all issues I had with the Oops proxy, that is now very stable on production servers.
Is there any way to install FreeBSD on an extended DOS partition ?
I've never been able to install FreeBSD 5 on my workstation because of this limitation.
Yes, and there already were plenty of Wikis (usually by hitting CORRECTION on a message) and Blogs (through private forums, "affiches" and responders).
Of course, instant messaging was already there (*TEL).
Oh and anyone could also create special effects using escape codes (# and $) and share them in real time. Maybe the internet world will discover this in 5 years, and this will be a revolution.
Re:Want to try a Minitel service right now ?
on
Minitel Hits Twenty
·
· Score: 2, Interesting
Not a good example.
This service is extremely ugly and bad designed:)
Videotex is way more powerful that what you can see here. Every character, including graphical ones can be redefined (8x12 dots), and latest minitels can also display jpeg images with full colors.
There are also plenty of tricks to speed up things (like using a lot CAN), and to make things look better (like overlapping double-sized characters that produces nice chrome effects). This service uses none.
"RTC"s were free local Minitel servers made by individuals.
Sure, there were not a lot of possible concurrent access (because phone lines were expensive for the server owner), but RTCs were really fun, especially because all people were living in the same area.
With some previous other RTC freaks, I'm trying to make a meeting of former RTC users in Paris. If you were addicted to RTC-ONE, JEF, OXYGENE, APOGEE and other RTCs, and if you live in Paris, please drop me a little mail at rtc@pureftpd.org . It would be really kewl to meet each other to remember the good'ol time:)
Slashdot Mirror
I strongly disagree. Maybe this 4096 times applies to the traditional single DES crypt. But execept for some rare compatibilities issues with old systems or for dumb people that create Apache .htpasswd files with it, nobody uses single DES any more for years.
Passwords hashed with MD5 and Blowfish don't have the 8 character limitation. There are still some people who like to assign users passwords like "*9_p7Z9ox" even though their system doesn't use single DES any more. This is just plenty stupid. Not only it's a hell to remember for the end user, but it's damn fast to brute force when hashes are precomputed as described in this article.
A normal password like a real sentence (ex: "I'd like to have sex with Sandra") is not only way more easy to remember, it's also orders of magnitudes harder to brute force.
I also found SuSE very responsive and helpful.
For Pure-FTPd, they subscribed to the mailing-list, reported bugs, proposed patches and they helped us to build RPMs, even for other distros.
The same thing applies to the Polish Linux Distribution.
" there were a few areas pointed out where the open source community does not do so well, such as regression testing and setting release dates."
/usr/src/regress/ directory. The tests are numerous and extensive.
It really depends. Setting release dates is not mandatory for an opensource project. Those projects are not made by a company for a customer requiring a specific deadline. OSS projects are mostly made during spare time. So the most reasonnable release dates are "when the code will be completed".
Regression tests are another story, but it really depends on projects and how they are managed.
For instance OpenBSD has very strict release dates. Every 6 months. And this schedule has always been respected.
OpenBSD also always introduces regression tests for new commands or new features implemented in existing commands. Have a look at the
IMHO the reliability of an ISP has nothing to do with the backend operating systems, especially when the study only considers the OS of the public web servers.
I'm sure that even a Win95 based ISP can provide a very reliable service. It's only a matter of redundancy.
On the other hand, the company I'm working for runs FreeBSD on its web and mail servers, but thanks to the dumb way things are installed and the lack of redundancy, a global uptime of 24 hours would be an all-time record.
With no possible single point of failure, with load balancers and correct usage of protocols like HSRP, service can be guaranteed even if some servers are continously crashing.
Have you ever seen Google unreachable? I've always seen it up. Although Google runs Linux. But they have properly designed their network for high availability. In an old Slashdot article, there was an interview of a Google techie who explained that if 1, 2 or 100 servers were down, it would have absolutely no impact on the service.
So at least for ISPs, I really think what matters is the skills of the network administrators. It brings another question : does the skills actually depends on the operating system they use?
Maybe. At least when you read mailing-lists of different operating systems, you can clearly see some common interests of the related subscribers. _This_ is really what makes differences between free operating systems. When it comes to reliability for traditional ISP services, either OpenBSD, Linux, FreeBSD or even Win2000 are quite comparable nowadays.
To get the best of two worlds, buy an iBook and Virtual PC.
Recent releases of Virtual PC are working amazingly well. Yes, it's an emulation, but no, it's not slow. Visual Studio runs flawlessly if this is what you need.
> That's probably because they don't have to. GCC isn't included with the AP.
This brings an interesting question. Should free software be redistributed with compilers that were used to generate binary packages?
If not, it would be possible to distribute source code that no one could compile. But this would still be opensource software. There's even no need to write a new compiler to do this. Encrypt the source code with GPG, say that your compiler is actually a simple wrapper that decrypts the source code before calling gcc et voila. You can distribute the encrypted source code that no one would be able to use. But this will be the real source code, so the project will be opensource.
But this is the chicken and egg problem. If opensource software should distribute the compiler that was used to generate binary packages, the compiler itself should be distributed with tools that were used to build it.
Where may I download the source code in order to port it to OpenBSD?
Greylisting mainly relies on this (quote) :
"These applications appear to adopt the "fire-and-forget" methodology. That is, they attempt to send the spam to one or several MX hosts for a domain, but then never attempt a true retry as a real MTA would."
I strongly disagree. A vaste majority of spammers actually use real mail servers like Qmail. Or strange spam-specific software with support for retries.
Apart from Spam Assassin, I'm using OpenBSD built-in "spamd" ip-based filter. A quick look at the spamd log files shows that the same spammers retry over and over, usually during 7 days.
What I like in Greylistings is that it actually prioritizes mails. A mail coming from a known source will be processed before a mail coming from an unknown source (that will have to wait for the next try) . Not really an antispam feature, but still nice to have.
I have a very positive experience with RAV Antivirus.
I'm using it daily on Windows and on corporate mail servers running Qmail on OpenBSD. No problem ever.
It is very fast, maybe 10x faster than Sophos Antivirus, and developpers are very reactive when it comes to merging new signatures to the virus database.
And the fact that it is really cross-platform and supports a lot of mail agents including Qmail is great!
The only thing I really don't like in it is the licensing scheme, based upon the number of hosted domains.
I would be very disappointed if the buyout by Microsoft removed the support for anything else than MS Exchange.
My NIC is BCM5702X.
:
:
Here's my exact hardware if it can help
00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400] Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8235
00:07.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46)
00:08.0 RAID bus controller: Promise Technology, Inc.: Unknown device 3376 (rev 02)
00:09.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5702X Gigabit Ethernet (rev 02)
00:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
00:0e.0 Multimedia video controller: Brooktree Corporation Bt878 Video Capture (rev 02)
00:0e.1 Multimedia controller: Brooktree Corporation Bt878 Audio Capture (rev 02)
00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 Audio Controller (rev 50)
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon VE QY
My experiences with this mobo
- Linux - old versions (don't remember which ones exactly, I tried a lot of kernels and various patches) : audio detected, but not working. Kernel freeze as soon as my CD writer is accessed.
- Linux 2.4.21_rc6-gss (Gentoo stable) with Alsa, ehci + uhci (not usb-uhci that crashes) : everything finally works.
- NetBSD-current : kernel freeze.
- OpenBSD 3.2-current with original BIOS : nothing worked, even disk I/O was flaky.
- OpenBSD 3.3 & current with updated BIOS : kernel freeze unless I manually disable auvia* drivers. Once auvia drivers are disabled, everything works fine except USB2 (unsupported by OpenBSD) and sound. The promise SATA controler also works in parallel mode.
- FreeBSD 5.0 and 5.1 : kernel freeze, even with the latest BIOS revision.
Fortunately, FreeBSD 5 works well with VMWare 4 on Linux.
A7V8X, not A7N8X. This is not the same chipset at all.
A7V8X is based upon a VIA chipset.
Unfortunately, once the system has been installed, I can't boot it. The kernel always crashes during the bootup phase on my ASUS A7V8X motherboard :(
Maybe it has something to do with USB2 and my CD burner (Plextor S88TU). I had similar crashes with NetBSD and old Linux kernels.
Is there any effort to port ReiserFS to *BSD systems?
All credits should be given to Tesla who did the real work. Edison was just a nasty jerk.
This is stupid and obvious, but... why does Outlook allows users to execute any executable file send through email just by clicking on it?
I can understand that clicking on an attachment can open Word or Excel.
But in the real life, when do you really _need_ to send executables to your friends? Or maybe you need to send some app you designed, but in this case your friends can always save the attachement and execute it later. This is something nobody would make on untrusted mails.
Here's what _may_ work :
Start the project at home, out of your working hours.
Make it GPL'ed. As a public proof, you can release an initial public beta version.
Back to your company, continue to work on the project. Any addition made to it must be GPL'ed as well, isn't it? So even though you are working on it while on company time, you can always release the product as free software.
Does this new boot loader finally allows to install FreeBSD on an extended dos partition ?
I don't understand why BSD never solved that issue. This is a serious showstopper for people who want to try FreeBSD and whoose hard disk already has other operating systems. I really don't want to backup and reinstall every partition of my hard disk just to see what FreeBSD 5 looks like.
Please note that on 3.3-STABLE and -current, MySQL is also finally extremely stable on OpenBSD, with native threads.
A lot of threading-related work has been made during the 3.3 development cycle and there are no more unexpected crashes with this sort of apps. For instance the new threading code solved all issues I had with the Oops proxy, that is now very stable on production servers.
Is there any way to install FreeBSD on an extended DOS partition ? I've never been able to install FreeBSD 5 on my workstation because of this limitation.
Is there any software to use Clie handhelds with Linux ?
Yes, and there already were plenty of Wikis (usually by hitting CORRECTION on a message) and Blogs (through private forums, "affiches" and responders).
Of course, instant messaging was already there (*TEL).
Oh and anyone could also create special effects using escape codes (# and $) and share them in real time. Maybe the internet world will discover this in 5 years, and this will be a revolution.
Not a good example.
:)
This service is extremely ugly and bad designed
Videotex is way more powerful that what you can see here. Every character, including graphical ones can be redefined (8x12 dots), and latest minitels can also display jpeg images with full colors.
There are also plenty of tricks to speed up things (like using a lot CAN), and to make things look better (like overlapping double-sized characters that produces nice chrome effects). This service uses none.
"RTC"s were free local Minitel servers made by individuals.
:)
Sure, there were not a lot of possible concurrent access (because phone lines were expensive for the server owner), but RTCs were really fun, especially because all people were living in the same area.
With some previous other RTC freaks, I'm trying to make a meeting of former RTC users in Paris. If you were addicted to RTC-ONE, JEF, OXYGENE, APOGEE and other RTCs, and if you live in Paris, please drop me a little mail at rtc@pureftpd.org . It would be really kewl to meet each other to remember the good'ol time
-ChrYsaLiS.
Anyone else had huge phone bills due to RTEL ?
:)
RTEL was _the_ thing that made me love Minitel.
And it was the headquarter of most Atari/Amiga demo crews
*SAL 2
#]#O#HMinitel rules#I#L#\
And Sugar ? :)
:)
Do you remember Sugar (3610)