When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
The old system's encrypted passwords were not readable by the new system hence the need for new passwords. Call us silly but we think password security is an important thing!
The sad fact is very few V10's are sold in comparison to the Powerstroke, especially with the 6.0 out now and the incentives on the 7.3.
Did you switch software packages for the Forum? Upgrades usually import old passwords. I always assume the people running the system can read my password file. Nice for it not to be so but SOOOO easy to do it.
This wasn't an upgrade. It was a change to a completely different software package. (From DCForum at www.dcscripts.com to VBulletin at www.vbulletin.com).
Unix (Linux) systems aren't like Windows systems. They use one-way encryption rather than two-way encryption.
Basically, you enter your password and the system encrypts it. Then it compares it to the encrypted password on file. It can't decrypt the password, only encrypt, using the password itself as the encryption key so it's damn near impossible to decrypt it.
Passwords on the FTE forums have never been readable, even by the admins. All we can do is assign a new password.
I know this forum has been dead lately. Has everyone gone somewhere else ? I'm disappointed it's not more activity. Well maybe not ! Let's see flutter, spark plug blow out's, and no MPG. That's about all our problems, guess this is good.
Password algorithms are not really OS related for the most part. I understand one way encryption - cake to crack with a good basher.
I would have done something like replace the built in log in a month before with a pass through to save them, then entered the data into the new system for ease of use, then asked the users to change their passwords.
Or leave the old system up and running, pass through the log in and check for a valid id from the new system (screen scraping if no nice XML interface).
Lots of ways to do it. I have about 300,000 users on our systems, not counting suppliers and customers and such.
Password algorithms are not really OS related for the most part.
Depends on the approach. Many of the industry standard functions for handling it aren't part of Windows implementations of a lot of server-side scripting languages. Its the reason why many Windows versions of the exact same BBS systems store passwords plain text. I programmed under Winblows for a decade and I'm glad to be rid of it. Nice worm two weeks ago.
I understand one way encryption - cake to crack with a good basher.
Depends on the number of bits used and how well the user choose their password. I use a large password with randomly selected letters, numbers, using upper and lower case.
I would have done something like replace the built in log in a month before with a pass through to save them, then entered the data into the new system for ease of use, then asked the users to change their passwords.
What you would have done is irrelevant. I work 60-80 hour weeks already. I handle coding during my spare time here, when that time exists. Have you seen the source code from the prior software we bought? You're making an assumption about what is and what isn't practical without knowing the source code. Your option would not have worked --- the majority of users use a session cookie tied to a session id on the server to stay logged on for months at a time. A password is never passed in such a case.
Or leave the old system up and running, pass through the log in and check for a valid id from the new system (screen scraping if no nice XML interface).
Saying we ought to have done it with method XYZ without considering the resources I have at my disposable is insensitive to the reality of our situation. What is possible is one thing, what is feasible and realistic given the time and resources available is quite another. What I had the time to do working for a Fortune 50 was a lot different from when I worked for a Fortune 500, a mid-sized company and now a 5 person company.
Lots of ways to do it. I have about 300,000 users on our systems, not counting suppliers and customers and such.
This discussion reminds me of the term "armchair quarterback."
Originally posted by webmaster Okay... let's start over. This thread has gone down the wrong road.
Sounds good to me Ken....
My V10 is running great. Really enjoying the SCMT settings so far.
Nuttn' much to complain/ask about I guess.....
Now I see Ford is putting the 3 valve/cylinder heads on the V10's in the near future (like they just did on the V8's).... dang, gonna have to save my pennies to upgrade to an '04 or '05 with the new SD look (whatever that'll be) and the new engine.
If anyone gets some specs/pix of the new 3 valve Triton V10's, please post!!
Rezvani's Latest Post-Apocalyptic Monster Is a Ford F-150 Raptor Underneath
Slideshow: Called the Fortress, the 850-horsepower pickup combines Raptor underpinnings with military-inspired features, survival equipment, and a starting price of $285,000.