Friday, April 13, 2007

Patching gnokii 0.6.14 for iTegno 3000 GSM Modem

Hi all. At this time i will share my experience on patching gnokii 0.6.14. Why we need to do a patch for gnokii 0.6.14 ?
Well, somebody are using iTegno 3000 GSM Modem or a device that known as a WAVECOM MODEM. And without using this patch then probably your smsd daemon won't work as expected. So, you still need this patch to make your AT Command working as you expected.

Simply editing file atgen.c (this file located at gnokii-0.6.14\common\phones\atgen.c)

Go to line 563 of your atgen.c file and you will find a code like this image below



Replace that code with the text like this image below



Go to line 1442 of your atgen.c file and you will find a code like this image below



Replace that code with the text like this image below



And all are already done. Please re-install your gnokii installation from the beginning with this new patch. Hope this article helps. Please read my another blog article about gnokii and iTegno 3000 GSM Modem on this site. It might help you too.

Saturday, April 07, 2007

Credit Card Verification

There are two verification system for the credit card. That is AVS and CVM.

1. AVS

AVS stands for Address Verification System. AVS is only available for the U.S. and partially available in four European countries. In the US, AVS checks if the cardholder's address and zip code matches the information at the card-issuing bank. AVS only uses the zip code and numeric portion of the billing street address. There are many reasons why AVS may fail (recent address change, AVS computers down, etc.). If the address verification fails on any level, the merchant may decline the transaction. If the AVS fails for any reason, the merchant should contact the customer for additional information (for example, the name of the issuing bank, the bank's toll-free telephone number, etc.).

The code will tell you whether or not the address given in the order actually matches that of the cardholder. On some system, the AVS code is comprised of three numbers. The first corresponds to the numbers in the street address. The second corresponds to the zip code. And the third is an overall verification of both. For example, an AVS code of YYY means: "yes" the address matches, "yes" the zip code matches and "yes," both the address and zip code match the cardholder's. But an AVS response code of NYZ means "no" the address does not match, "yes" the zip code matches and only the "zip" code matches.

Don't be fooled by YYY response codes. Some crooks have access to the cardholder's address information. Be observant and know what red flags to look for. Pay close attention to: the product ordered and order size; the e-mail address given; the ship-to address and shipping method requested among other things. Be suspicious of sizeable purchases that are being shipped to a different address, especially if express shipping is requested. Pay attention to whether or not the e-mail address given is valid. If the e-mail address is a person's name, check to see if it matches the cardholder's name. These, among other things, are all red flags to look for.

Below is the common AVS response code letters and their meanings :
Letter_ Meaning
Y_____ Exact Match
N_____ Not A Match
A_____ Address Match Only
Z_____ Zip Code Match Only
S_____ Service Not Supported (often for non-US credit cards, get proof from cardholder via fax if possible)
U_____ Address Information Not Available (call cardholder's issuing bank)
X_____ When with "YY" means exact match. Otherwise, "XXU" means address Information Not Available (call cardholder's issuing bank)
R_____ Retry - System Unavailable Or Timed Out
W_____ Zip Code OK
E_____ Error Response For Merchant Service Category Code

2. CVM

CVM stands for Card Verification Methods (VISA = CVV2, MasterCard = CVC2, and American Express = CID use a security code of 3 or 4 extra digits imprinted on the card, but not embedded or encrypted in the magnetic stripe. This verification code does not appear on credit card receipts. Since most fraudulent transactions result from stolen card numbers rather than the actual theft of the card, a customer that supplies this number is much more likely to be in possession of the credit card. VISA claims that the use of AVS with CVV2 validation for card-not-present transactions can reduce chargebacks by as much as 26%.

Tuesday, April 03, 2007

How To Find The Service Pack Version Installed On SQL Server

To determine the service pack that's installed on your SQL Server, open Query Analyzer. Connect to your server. Execute the following command:

SELECT @@VERSION
GO

The output of this command will be something like the one pasted below. The first line of the output displays the version number of the server. The last 3 digits (build number) of the version number are used to determine the service pack installed on your SQL Server. In this case 194.

Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 2)

Below are the SQL Server version list :

SP Version : 6.00.121
Product___ : SQL Server 6.0

SP Version : 6.00.124
Product___ : SQL Server 6.0

SP Version : 6.00.139
Product___ : SQL Server 6.0

SP Version : 6.00.151
Product___ : SQL Server 6.0

SP Version : 6.50.201
Product___ : SQL Server 6.5 (Hydra)

SP Version : 6.50.213
Product___ : SQL Server 6.5 (Hydra)

SP Version : 6.50.240
Product___ : SQL Server 6.5 (Hydra)

SP Version : 6.50.258
Product___ : SQL Server 6.5 (Hydra)

SP Version : 6.50.281
Product___ : SQL Server 6.5 (Hydra)

SP Version : 6.50.415
Product___ : SQL Server 6.5 (Hydra)

SP Version : 6.50.416
Product___ : SQL Server 6.5 (Hydra)

SP Version : 7.00.623
Product___ : SQL Server 7.0 (Sphinx)

SP Version : 7.00.699
Product___ : SQL Server 7.0 (Sphinx)

SP Version : 7.00.842
Product___ : SQL Server 7.0 (Sphinx)

SP Version : 7.00.961
Product___ : SQL Server 7.0 (Sphinx)

SP Version : 7.00.1063
Product___ : SQL Server 7.0 (Sphinx)

SP Version : 8.00.194
Product___ : SQL Server 2000 (Shiloh)

SP Version : 8.00.384
Product___ : SQL Server 2000 (Shiloh)

SP Version : 8.00.534
Product___ : SQL Server 2000 (Shiloh)

SP Version : 8.00.760
Product___ : SQL Server 2000 (Shiloh)

SP Version : 8.00.2039
Product___ : SQL Server 2000 (Shiloh)

SP Version : 9.00.1399.06
Product___ : SQL Server 2005 (Yukon)

Apart from SELECT @@VERSION, there are other commands too, that show you the build number. Try, sp_server_info and master..xp_msver. In SQL Server 2000, there is a new system function called SERVERPROPERTY, that returns service pack information. Here is an example:

SELECT SERVERPROPERTY('ProductLevel')
GO

Changing SQL Server Passwords

Most security experts recommendations include changing passwords frequently to enhance security. It is easy to change the password on a SQL Server Username via Query Analyzer. Changing the password with Query Analyzer makes it easy to coordinate changing the password on the database server at the same time as it is changed in the connection string. This approach provides the flexibility to change the password at the most appropriate time for the application.

To change the SQL Server Username password, just connect to the database with Query Analyzer using the SQL Server Username that is being updated and the current password. Then run "sp_password" to change the password.

Here is a simple example that changes the current password from "current_password" to "new_password" :

sp_password 'current_password', 'new_password'

If your first SQL Server installation use a blank password then you need this way to change the SQL Server password :

sp_password NULL, 'new_password'

Be sure to use a strong password, "new_password" is just an example. For a quick test to confirm that the new password is working, close Query Analyzer and then re-connect with the new password. That is all there is to it, except for changing your connections string. It is obvious, but still critical to remember to change the password in your connection string if this SQL Username is used in your code. Once the password has been changed and tested with Query Analyzer, update the connection string with the new password and test that everything still works correctly, and you're done.