Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About SteveW

  • Rank
    Distant Family

Profile Information

  • Gender
  1. As you said, it's best not to use your cPanel userID/password for database connections, for two reasons: 1) Your cPanel password is a very powerful one that allows a high level of access to your website. It should never be stored in a text file inside your website. But database connection passwords MUST be stored in a text file inside your website. Therefore, the one in the text file should not be your cPanel password. 2) When you use a separate MySQL userID/password for your database connections, you can change your cPanel password anytime you want, without breaking your database conn
  2. I think that could happen if you have been using your cPanel userID/password to connect to your database, and if you then changed your cPanel password in cPanel. Your database script would still be trying to connect to the database using the old password. Does that sound like it describes your situation? Most software applications store their database connection data in one file, called something like config.php, config.inc.php, or settings.php, in one of the folders used by that application. The solution would be to edit that file in a text editor (such as the one you can launch f
  3. Up to now, gedit has been my favorite all-purpose text editor in Ubuntu. It came with a few plug-ins. I enabled some of them, but my memory is that most seemed fairly minor, so maybe there's a bunch more available that I'm not aware of? I like Geany, too, and Bluefish, but haven't used either of them often enough for their intended purposes to have a valid opinion. I think one of them allows selecting text and clicking a button to surround the text with HTML tags (which a Notepad++ plugin does), and the other allows clicking to create empty HTML tags which you can then fill with contents.
  4. GoodBYtes's post above (#157) expressed much the same as I was thinking, better than I can ^. Especially appreciate the prompt status announcement in the forum. The notification email was how I learned of the incident. I found it a non-jarring way to be notified. Truly amazing, skillful, and fast. Thank you.
  5. It makes me glad when someone seems to be having a good experience with one of the linuxes. I've been using Ubuntu Jaunty ever since first trying it about 2 1/2 years ago. It's well past its support period and feels creaky (with Firefox 3.0 when I've got FF12 in Windows XP), but, at the time, I downloaded every software package I thought might ever be of interest, 2000 of them, 2GB+, which took two weeks on dial-up. I'd like to try Debian, but am not anxious to do a two-week-installation repeat and don't want to risk having no working linux because I quickly discovered that once I had it,
  6. I don't like to let a question go unanswered, but all I know about those certificates was from some reading at their website and Wikipedia after you mentioned them. I thought I saw one comment that some of their free certificates aren't free anymore. I don't know that much about SSL, but it seems as though there are different levels of trust and corresponding differences in price. It would seem to me that all you need is something suitable for encryption, and that the question of whether you are "who you say you are" is not that important in this situation, and maybe an inexpensive certifi
  7. The purpose of a privacy policy should be to state honestly what the actual situation is, not to try to instill confidence in visitors by making comforting mission statements that might not be achievable. Even an honest privacy policy like "I can't really promise that people's private information will stay private" is better than a more comforting one that is false. However, a privacy policy generally only pertains to factors under your control. Some risks of electronic communications are not under your control. It is not necessary to make a sweeping promise like "people's private informat
  8. Either method could allow a brute-force password guessing attack to succeed unless all your passwords for all your MySQL database users (not just the new one you created) are very secure, an absolute minimum of 12 completely random characters, upper/lower/punct. More is better. If you don't use punct, make the password at least 2 chars longer to compensate. With the phpMyAdmin method, you'd need to make sure that your version of phpMyAdmin is always kept up to date, which could sometimes involve installing an update about once a month based on the history at http://secunia.com/a...task=adv
  9. Glad to hear it, Bill. TCH deserves the success. You and the TCH staff do a great job. I'm very happy to be hosted here, and I'm sure many others are, as well.
  10. In addition to the other suggestions, Microsoft's successor to FrontPage is called Expression Web. There was a time when you could upgrade from FP to EW for only about $80.
  11. If you post a message to the other thread, the person who started it should get a notification that somebody replied to it. They might be willing to post how the situation turned out. What antivirus program do you use?
  12. Announcement at http://www.simplemachines.org/community/index.php?topic=452888.0
  13. Thank you for responding so quickly. I got this email today also. Would it help you to have a copy of it with all headers? If so, just let me know who to send it to.
  14. I used Trend Micro Internet Security for about 5 years and thought that it, and especially its firewall, were very good. However, at renewal time I learned that I'd be automatically upgraded to their new "Titanium" product which according to my online reading seemed to be a very much changed product with a simplified interface (it was already perhaps too simple), fewer configuration options, and, what caught my attention, no longer included a firewall. IF that's true, it could be because the standard Windows Vista/7 Firewalls are now so much improved over the old Windows XP version. But I
  • Create New...