There are commands given to us in Scripture that we often don’t understand. Our usual response is to ignore these commands. I’ll give three examples.

The ancient Jews were given religious dietary laws that some Jews still try to live by. One of these laws prohibited certain kinds of meat, one of which is pork. It would have been useless to try to explain things like trichinosis to a primitive people. It’s probably useless to try to explain it to most people now. But, if one obeys the religious law, one won’t get the disease. Because we now know that we can avoid trichinosis by cooking pork well, we assume that it is OK to eat it. Are there things in religiously forbidden food (that includes catfish and shellfish) that we don’t know about that could hurt us? Possibly.

Jesus, in the Lord’s Prayer or the Our Father (whichever you prefer to call it) bade us pray “Forgive us our trespasses as we forgive those who trespass against us.” He followed up this prayer by telling His disciples, “For if you forgive men their trespasses, your heavenly Father will also forgive you. But if you do not forgive men their trespasses, neither will your Father forgive your trespasses.” This is in the sixth chapter of St. Matthew. Notice that this command does not refer to the worthiness of the other person to be forgiven. Neither does it refer to your feelings toward the other person. It’s between you and God. You may be forgiven by God only if you forgive other people. Period. We don’t understand the unconditional nature of forgiveness. We assume that we can’t do what God commands because our feelings don’t immediately line up with the command or because we reason that the person that we’re commanded to forgive doesn’t deserve it. (Implicit in this reasoning is that we do deserve God’s forgiveness. Wrong!!) We think that God won’t hold us accountable for obeying this command because we assume that He is being unreasonable. So we reason it away and ignore it.

The third example really gets into unknown territory for me. Women are told to be quiet in the church. (I Corinthians 14:34) St. Paul, in I Timothy 2:11-15 come up with the most weird reasons for making this demand. First is that Adam was formed before Eve was. The second is that, in the fall, Eve was deceived into thinking that she was doing right when she sinned. Therefore, she “fell into transgression”. What have either of these things to do with women speaking in churches? Don’t ask me. I haven’t a clue. I’ve read commentaries that give reasons why we need not observe these rules in the modern church, even among those who say they believe that the Bible is (not contains) the Word of God. I live among a people whose principal church (85% of the population) had a pastor arrested because he believed this Scripture and refused to serve in the same service with a female priest. Most churches today consider this command to be unreasonable, so they ignore it.

My point is that we humans tend to ignore what we don’t understand or consider to be unreasonable. In the Garden of Eden, God told Adam and Eve, “for in the day that you eat of it, you shall surely die.” That old serpent, Satan, told Eve, “You shall not surely die.” It was unreasonable to believe that eating a piece of fruit could cause death. There are many people who will spend an eternity in Hell because they think that repenting and believing in the finished work of our Lord Jesus as payment for our sins is unreasonable.

The computer threat is called a “rootkit”. I’ll explain how it works later, but I want to point out that it is like the sin nature in a human being. Even as our sin nature makes us susceptible to the moral virus of temptation, so the rootkit downloads and installs viruses. We Christians must die before our sin nature “rootkit” is removed from us. A computer must be turned off (dead) to remove a rootkit.

This kind of thinking continues into the way we use our computers. We don’t understand certain warnings or we believe that some one else, such as Microsoft or the writers of our anti-virus software, are responsible for our computer security. We don’t understand, so we ignore the warnings. I am going to explain just one threat and give a couple of easy things that a person can do to reduce the threat of having his bank account open to hackers. It will start out with a very basic explanation and solution. Then I’ll explain my reasons in more detail.

If what I write goes over your head technically, please find someone who can help you. I am not a security expert, but sometimes the security experts can lose us with the amount of knowledge that they have and try to share.

This warning is especially for those of you in Europe and more especially if you use Internet Explorer (IE) as your web browser.

This warning comes from web sites that I’ve seen that talk about rootkit malware that is being used to get access to bank accounts. If you do not now have a rootkit, you may protect yourself by doing two things. Stop using IE. In addition, use a router. These two actions reduce your vulnerability considerably, but does not eliminate it.

How do you know if you have a rootkit? Windows users can Google with “windows rootkit” to find a detector program. (Microsoft has a free one called RootkitDetector.) Your anti-virus software may (or may not) be able to detect a rootkit. It cannot remove one, even if it is found, for the computer must be turned off during the process. Linux users can freely download and install “chkrootkit”.

Use Firefox instead of IE. There are a few sites that require the use of IE. I get along fine without using them, although I once had to change banks because the bank’s web site required IE. The reason to stop using IE is that it is a huge security hole, even with the latest versions of IE and with the use of Windows XP or Windows Vista. The rootkit that I just read about gets installed through one of these security holes. (There are other ways to put rootkits on computers. This is the most commonly used, so I am told.)

The other recommended action, to install a router, is only recommended for those who have high-speed internet. This is because those with high-speed internet are connected any time their computer is on. A router does many things, but what we are interested in here is its “insulating” capability. A router is a tiny, special purpose computer that is connected to the Internet. Your computer is connected to the router. A malicious hacker who is looking for computers to attack can see your router, but he can’t see your computer. Most routers are so special purpose that a hacker couldn’t see or do anything with one that he could see. Most modern routers have a firewall built in. A firewall’s purpose is to keep hackers from invading your system.

What is a rootkit? A rootkit is a program that is installed in the place that starts your operating system (Windows, OsX or Linux) when you turn your computer on. While it is not technically a virus itself, it downloads viruses into your computer, so that even if your virus protection software removes the virus, the rootkit will install the virus again.

Why do I warn Europeans more than others? There is a site in Russia that sends out rootkits and viruses that are aimed at Europeans who access their bank accounts with their computers. The virus sends the victim’s bank login and password to the Russian site. They can then get into the victim’s bank account. Some European banks change login information regularly. This makes it more inconvenient to access an account, but if this Russian site were to somehow get information from such a bank, they could use it for only a short time before having to start all over again. I don’t know of any American bank that has this protection.

Here’s to your enjoying the use of your computer!

P.S. Outlook and Outlook Express are other big security holes, but those vulnerabilities are necessary to give Windows users the ability to do things that non-Windows users can’t do, like having an email start a program automatically or to pass something on to everybody in your address book. It’s every individual’s choice, but I can do without features like that to protect my computer.

My extension is to make the importation of the code dynamic, i.e. this code may be used, as is, to import any CSV file into any table without changing the code. The first row of the CSV file consists of column headers. In keeping with the convention over configuration principle of Rails, these column headers must be identical to the field names of the table that the data is to be imported into. (The exception to this rule is that the column headers may be mixed case.)

file: app/views/infolake/index.rhtml

<html>
  <head>
    <title> Import InfoLake Spreadsheet </title>
  </head>
  <body>
    <h1>Import InfoLake Spreadsheet</h1>
    <% form_for :load, :url=>{:controller=>"infolake", :action=>"csv_import"},
      :html => { :multipart => true } do |f| -%>
    <table>
      <tr>
        <td>
          <label for="load_file"> Select a CSV File :</label>
        </td>
        <td >
          <%= f.file_field :file -%>
        </td>
      </tr>
      <tr>
        <td colspan='2'>
          <%= submit_tag 'Submit' -%>
        </td>
      </tr>
    </table>
  <% end -%>
  </body>
</html>

file: app/views/infolake/csv_import.rhtml

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html>
  <head>
    <meta name="generator" content="HTML Tidy, see www.w3.org">
    <title>Spreadsheet Import Confirmation</title>
  </head>
  <body>
    <h1>Spreadsheet Import Confirmation</h1>
    <p style="color: green"><%= flash[:message] %></p>
  </body>
</html>

file: app/views/infolake/csv_import.rhtml

class InfolakeController < ApplicationController
  require 'csv'

  def index
    @load
  end

  def csv_import
    @file = CSV.open(params[:load][:file].path, 'r')
    @cols = Hash.new
    @nbr_rows = 0
    @file.each { |row|
# This code will have another iteration, so we'll use "case" instead of "if"
      case @nbr_rows
      when 0: # Store the column headers and their positions in the CSV file in a hash
        row.each_with_index { |col,i|
          unless col.nil?
            col.downcase!
            @cols[col] = i
          end
        }
        @nbr_rows += 1
      else
        import(row)
      end
    }
  end # def csv_import

  def import(row)
    @infolake = Infolake.new
    @cols.each { |col_name,col_ix|
      unless row[col_ix].nil? || row[col_ix].empty?
        eval("@infolake.#{col_name} = row[#{col_ix}]")
      end
    }
    if @infolake.save!
      @nbr_rows += 1
      GC.start if @nbr_rows % 50 == 0
    else
      identifier = "#{row[@cols['identifier']]}"
      puts "CSV record with identifier = #{identifier} was not saved."
    end
    msg = "No new records were added to the data base"
    flash.now[:message]= msg if @nbr_rows == 0
    msg = "#{@nbr_rows} new records were added to the data base"
    flash.now[:message]= msg if @nbr_rows > 0
  end # def import_row
end