Archive for November 2011

How To Be A Safe Hacker?

Safe Hacker

            This article will show you some of the top ways the best hackers use to keep themselves hidden and out of jail and to be a better Hacker. Educational purposes only. Written for beginners.


  •   1. Never Hack without a proxy

  •   2. Always use a proxy when doing anything remotely illegal

  •   3. Never Hack from your house

  •   4. Never use your real name in a conversation or sign up sheet

  •   5. Always use fake information when signing up for something such as an account

  •   6. Never use the same password more than once

  •   7. Never use a password that can be found in the dictionary

  •   8. Always use a firewall

  •   9. Never let the F.B.I. into your house without a warrant stating their intentions.

  • 10. Never let the F.B.I. in period.

  • 11. Always have a panic button that mass deletes all your questionable material.

  • 12. Make sure that the deletion of your files it is at least in compliance with the Department of Defense deletion protocol if you have time; The Guttman Method is the best.

  • 13. Never Hack from the same computer twice if possible
    • 14. Always wave to cops

  • 15. Keeping a low profile is very important, it reduces your chances of getting caught

  • 16. When using open-wireless network for hacking make sure to change your computer MAC address and hostname

  • 17. If you ever have to relocate, make sure all your secrets are destroyed and the place wiped clean.

  • 18. Make use of heavy encryption when possible.

  • 19. Passwords should never contain dictionary words, always use long phrases instead 

You might say to yourself that you do not follow one or more of these rules. This is why most hackers get caught. They forget to cover their tracks and get busted. The more rules you abide by, the better your chances are of staying hidden.
Wednesday, November 30, 2011
Tag :

How to Create a Simple Backup Job in SQL Server

Create a Simple Backup Job in SQL Server

                There are several ways to create a backup job in SQL Server 2008 and I’m going to show you how to create a very simple one for both a single database and for multiple databases.  And since there are so many ways to do this, I’m going to briefly discuss most of them at the end of this article so you’ll have a good idea of what other options you have.

So let’s go ahead and jump in and get started with a very simple backup routine.
              First you start by opening a query window in SSMS and connect to the server you want to backup.  It’s worth noting that it doesn’t matter which database you’re connect to, but I typically do it from master just to be consistent.

The basic backup syntax that you need to type is here:

BACKUP DATABASE databaseName
TO DISK = 'file location'

OK, let me explain a couple of these items.

BACKUP Database – T-SQL command for what you want to do, which in this case is backing up a database.

databaseName – this is the name of the database you want to backup.

To disk = 'file location' – Backups are written to files.  This is the full path to the file.  Typically, a full backup such as this one will have the extension of .bak, but that’s just what everyone does.  It can have any extension you like or no extension at all if you like.

Now let’s see a real example with all of the values filled in.  Here we’re going to backup the Model database to a file called ModelBackup.bak on C:\.

BACKUP DATABASE Model
TO DISK = 'c:\ModelBackup.bak'

That’s it.  You have now taken a full backup of the Model database.  I’ll also go ahead and add that unless SQL Server 2008 was installed with a case-sensitive collation (this is very rare), the parser ignores whitespace and case.  For example, the following 3 commands are equal on a case-insensitive system.

backup database Model
To disk = 'c:\ModelBackup.bak'


BACKUP DATABASE MODEL
To disk = 'c:\ModelBackup.bak'

bacKup DataBasE ModeL To dIsk = 'C:\MODELBACKUP.BAK'

However, you don’t want to backup your database by hand every time so you want to schedule this to run on its own.  And for this you’re going to put the above code into a job and schedule it.  The easiest way to do this is to create a job in SSMS.  Follow these steps to create the job and put your backup statement inside of it.

Expand the ‘SQL Server Agent’ tree and right-click on ‘Jobs’.  Then choose the top item, ‘New Job…
Now you’ve got the new job dialog box.  Filling in the info is pretty easy.  You need to give your job a name, and everything else is optional.  Here I’m going to fill in the name of the job as ‘Backup user database’.
Next click on the ‘Steps’ pane on the left and you’ll be presented with this screen.  It’s blank because you haven’t created any steps yet.  So go ahead and click on the ‘New’ button at the bottom.
This is where the real magic happens.  Again, you have to fill in a name so you know what the step is called.  Make it something descriptive.  There are several step types to choose from, but the default is T-SQL and since we’re running a T-SQL command that’s clearly the one we want to go with.  The database defaults to ‘master’ and that’s just fine with us.  Here’s what we have so far.  You see the only thing we’ve had to do is fill in the step name.
The only thing left to do is to copy your backup statement into the query window.  Of course it’s always a good idea to make sure your code will parse before you try to run it.  Just click the ‘Parse’ button I’ve circled.  Here’s what that looks like.
Now click OK and it’ll take you back to your new job window and now you’ll see your job step listed.  And you can stack as many as you like inside there.

To schedule your job, just click on ‘Schedules’ on the left and then choose the schedule that’s right for you.  It works similar to the the way it does in Windows so there’s really not much need for me to rehash it here.

Once you click OK all the way out until the new job box is closed, your job will be added to the job tree.  You may have to right-click on ‘Jobs’ and refresh the display for it to show up.
Now that you’ve created the job to backup your database I’d like to go back to the command again and add one more part.  See, when you backup a database to a file it won’t overwrite the file by default.  By default it will append to the file, so your backup file will just get bigger and bigger.  So what you want to do is add a special flag to the command that tells it to initialize (or overwrite) the file every time.  That makes our backup command look like this
now:
BACKUP Database Model

To disk = ‘c:\ModelBackup.bak’

With INIT
This is a good thing to keep in mind while you’re creating your job.

But what if you wanted to backup more than one database?  Well, again, there are several ways to do this and I’m going to show you the easiest just to get you going.

There are 2 methods we’re going to discuss here:


1.  In the job step you just created, you can just stack backup commands one after another.  So the window that holds your backup code inside the step could easily hold the code for several databases.  That would look something like this:
2.  The other way you could do it is to add each one of your backup commands to their own step by repeating from step 3 above.

Here I’ve shown you how to create a simple backup job.  Most tutorials will show you how to use the backup wizard, but that’s ridiculous because you’ll never do that in production.  Nobody wants to manually backup their databases every day.


Wireshark University Network Training ( 4 DVD )

Wireshark University Network Training

                 This course focuses on network forensics including capture locations, stealth-mode capture, optimal capture and display filters, validating encrypted logins, identifying reconnaissance processes, locating header and payload signatures, catching penetration tests, malware  ehavior, backdoor communications and virus traffic.

Download Links :-

Wireshark University Network Training.Part01
Wireshark University Network Training.Part02
Wireshark University Network Training.Part03
Wireshark University Network Training.Part04
Wireshark University Network Training.Part05
Wireshark University Network Training.Part06
Wireshark University Network Training.Part07

Transferring FSMO Roles in Windows Server 2008

Transferring FSMO Roles in Windows Server 2008

Introduction
              This is a must to read article for any system administrator who administers Microsoft Windows Servers. One of any system administrator duties, would be to upgrade a current domain controller to a new hardware server. One of the crucial steps required to successfully migrate your domain controller, is to be able to successfully transfer the FSMO roles to the new hardware server. FSMO stands for Flexible Single Master Operations, and in a forest there are at least five roles. In this article, I will be showing you how to transfer the FSMO in Windows Server 2008,  and in my next article, I will show you the complete steps required to successfully migrate/upgrade your domain controller to a new hardware server.

The five FSMO roles are:
  1. Schema Master
  2. Domain Naming Master
  3. Infrastructure Master
  4. Relative ID (RID) Master
  5. PDC Emulator
The FSMO roles are going to be transferred, using the following three MMC snap-ins :
  • Active Directory Schema snap-in  : Will be used to transfer the Schema Master role
  • Active Directory Domains and Trusts snap-in : Will be used to transfer the Domain Naming Master role
  • Active Directory Users and Computers snap-in : Will be used to transfer the RID Master, PDC Emulator, and Infrastructure Master roles
Note: 

 The following steps are done on the Windows Server 2008 machine that I intend to set as the roles holder ( transfer the roles to it )

Lets start transferring the FSMO roles
  • Using Active Directory Schema snap-in to transfer the Schema Master role
You have to register schmmgmt.dll in order to be able to use the Active Directory Schema snap-in

1.Click Start > Run

2.Type regsvr32 schmmgmt.dll

  • 3.Click OK

  • A popup message will confirm that schmmgmt.dll was successfully registered. Click OK
    4.Click Start > Run, type mmc, then click OK
    5.Click File > then click Add/Remove Snap-in...
    6.From the left side, under Available Snap-ins, click on Active Directory Schema, then click Add > and then click OK
    7.Right click Active Directory Schema, then click Change Active Directory Domain Controller...
    8.From the listed Domain Controllers, click on the domain controller that you want to be the schema master role holder and then click on OK
    You will receive a message box stating that the schema snap-in is not connected to a schema operations master. That is for sure, as we have not yet set this Windows Server 2008 domain controller as a Schema Master role holder. This will be done in the next step. Click OK
    9.In the console tree, right click Active Directory Schema [DomainController.DomainName], and then click Operations Master...
    10.On the Change Schema Master page, the current schema master role holder will be displayed ( ex. ELMAJ-DC.ELMAJDAL.NET) and the targeted schema holder as well (ex. ELMAJ-DC2K8.ELMAJDAL.NET). Once you click Change, the schema master holder will become
    ELMAJ-DC2K8.ELMAJDAL.NET , click Change

    Click Yes to confirm the role transfer
    The role will be transferred and a confirmation message will be displayed. Click OK
     Then click Close, as you can see in the below snapshot, the current schema master is ELMAJ-DC2K8.ELMAJDAL.NET

    Using Active Directory Domains and Trusts snap-in to transfer the Domain Naming Master Role

    Click Start > Administrative Tools > then click Active Directory Domains and Trusts
    Right click Active Directory Domains and Trusts, then click Change Active Directory Domain Controller...
    From the listed Domain Controllers, click on the domain controller that you want to be the Domain Naming master role holder and then click on OK
    Right click Active Directory Domains and Trusts, then click Operations Master...
    On the Operations Master page, we are going to change the Domain Naming role holder from ELMAJ-DC.ELMAJDAL.NET to ELMAJ-DC2K8.ELMAJDAL.NET, Click Change
    Click YES to confirm the transfer of the Domain Naming role
    The role will be transferred and a confirmation message will be displayed. Click OK , then click Close

    Till now, we have successfully transferred two FSMO roles, the Schema Master role and the Domain Naming role. The last three roles can be transferred using a single Snap-in.

    Using Active Directory Users and Computers snap-in to transfer the RID Master, PDC Emulator, and Infrastructure Master Roles

    Click Start > Administrative Tools > then click Active Directory Users and Computers
    Right click Active Directory Users and Computers, then click All Tasks > Operations Master...
    You will have three Tabs, representing three FSMO roles (RID, PDC, Infrastructure). Click the Change button under each of these three tabs to transfer the roles.
    Click Yes to confirm the role transfer
    The role will be transferred and a confirmation message will be displayed. Click OK
    As for the Infrastructure role, once you click on the Change button you will receive the below message
    By default, when you first install your first Domain Controller, it holds the five roles and beside that it is a Global Catalog. If your environment is a multi-domain/forest, then you should think about structuring your FSMO roles and transfer the Infrastructure role to a none Global Catalog domain controller. Else if you have small number of domain controllers ( ex. two domain controllers) then you should not worry about this. Click Yes
    The Tabs should now look like this:
    That's it, by now, you have successfully transferred the five FSMO roles to the Windows Server 2008 Domain Controller.

    Tuesday, November 29, 2011
    Tag :

    Upgrading TMG Server 2010 Standard Edition To Enterprise Edition

    Introduction :
                       With TMG Server 2010, upgrading from TMG 2010 Standard Edition to Enterprise Edition is a very easy step. You do not have to uninstall the Standard Edition and then import the policies/configuration that you've had exported previously into your newly installed Enterprise Edition. The upgrade process is simply done by entering the Enterprise Edition product key inside the Standard Edition Management console. Let's see how.

    Steps To Go:
    1.Open TMG Server 2010 management console, and from the left pane, click on the System node
    From the middle pane , click on your server's name to become selected, and then from the right side pane, under the Tasks tab, click on Upgrade to Enterprise Edition as shown below.
    The Server properties page will open, under the Product ID tab, click on the Upgrade To Enterprise Edition...
    The Product Key Entry page will open, where here you should enter the product key for Forefront TMG Server 2010 Enterprise Edition.
    Once you type the product key, click on the OK bytton.
    You will get back to the server properties page, and as you can notice, the Product ID has changed and also the Production Edition is now Enterprise. Click OK

    One last step is remaining to completely upgrade TMG 2010 Standard to Enterprise, and this is to confirm the changes by clicking on the Apply Button.

    As you can see, from the upper right side, the word Standard is now changed to Enterprise, and in the right pane, under the Tasks tab, the option Upgrade to Enterprise has been removed after you used it.

    Note : If for some reason you want to cancel the changes, then click on the Discard button and make sure to close the management console.

    Summary
    The process of upgrading TMG Server 2010 Standard Edition to Enterprise Edition is very easy. Neither reinstallation is required nor re-importing policies. It is simply done by typing the Enterprise Edition product key, and instantly the Enterprise Edition features will become available.

    Cloud Computing 101: Private vs Public Cloud

    Cloud Computing 101: Private vs Public Cloud

                  The “cloud” is a term with a debatable meaning. Even in the enterprise, surveys have revealed that there are some who have yet to develop a clear understanding of cloud computing. A recent survey by Virtacore Systems published in this CompTIA SmartBrief estimates that 48% of IT professionals at mid-sized companies don’t understand what the term actually means.

    Perhaps some of the confusion comes from the fact that there are two types of clouds: public and private. Let’s take a closer look at what the main differences are between private and public clouds and later, what you should take into consideration when looking for a cloud computing provider.

    Private vs Public Clouds

    A public cloud is one in which a service provider serves customers, with functionality like applications, infrastructure, and storage. These services are available to businesses and individuals over the Internet. Public cloud services may be free or offered on a pay-per-usage model; sometimes it’s referred to with the -aaS acronym, meaning “as a Service” as in IaaS (Infrastructure as a Service), PaaS (Platform as a Service) and SaaS (Software as a Service). More on this here: What Cloud Computing Really Is.

    This is a scalable service provided by a vendor, designed to be easier to setup and administer with less cost, in addition to reducing waste from lesser used data center resources.

    The idea is to eliminate physical location from the data and system access equation. Data from several corporate or individual clients are segmented but do share server space — called, co-location. 
    Public Cloud

    The private cloud describes an internal computing model and architecture which provides hosted services similar to those of the public cloud, but reserved for corporate users and those that are approved; essentially, a private cloud is not open to the public and us usually setup behind a firewall. In a sense, this turns the IT department into the service provider or vendor for cloud resources. For those interested in reaping the benefits of virtualized cloud architecture, yet needing more control and security, this is a popular option.
    Virtualization and data center automation allows for the scalability, maximizing hardware usage, and flexibility to support internal corporate clients. And, if your organization is so inclined, metering also allows you to charge departments based on their usage.
     Private Cloud


    Top 5 Things to Look for In A Cloud Computing Provider

    For many organizations, the benefits of the public cloud outweigh the risks. But before making a decision on shifting an application or service to the cloud, there are a few things to consider. The first question is whether or not the intended application is suitable for use in a cloud-based setting.

    Assuming your application has been deemed a good candidate for the cloud, the second consideration is who to trust with your data.

    So here are the top 5 things you should consider when selecting a public cloud vendor.

     #1 Is the company viable?

    Before handing over your critical applications and data, an important first step is to assess the financial viability of the company. Find out how long the company has been in business. Given the relative immaturity of this market, it may be unlikely to find vendors with several decades of presence, but you almost certainly don’t want a company that has just set up shop either. In addition, look for any indicators of past or future economic issues, along with frequent leadership changes.

    #2 Are service level agreements offered?

    For organizations entrusting mission critical data to a vendor, you’ll want to ensure that your systems will not suffer from frequent or extended outage periods. Downtime can have disastrous consequences both in terms of financial loss and damage to company reputation. For this reason, a service level agreement with negotiable terms, should be available. This agreement should outline provisions for everything from server or software issues, to more detailed disaster recovery plans.

    #3 Is customer service a priority?

    One guarantee with corporate networks is that something often can and will go wrong. In these instances, it is imperative that the vendor respond quickly, efficiently, and professionally. You should determine things like: response times, dedicated vs. general support, and phone/email/chat availability. Depending on the nature of the application that the vendor hosts, you may find that a dedicated support engineer, with 24×7 availability better suits your needs than calling a general help line and waiting in a call queue.

    #4 Will my customers have the same level of performance?

    Another issue cited with cloud services is the perceived negative performance impact. Customers and employees have an expectation that no matter where data is housed, they will enjoy the same level of performance. The cloud provider should be able to define how they measure performance and be able to provide real-time and ongoing measurements and statistics to back this up.

    #5 How is security handled?

    Perhaps the most frequent reason cited for not pursuing cloud computing is security. Many organizations have invested considerable financial and human resources in order to secure their network environments and the thought of abandoning that level of control and comfort to an unknown entity can seem like an unnecessary gamble. Any reputable vendor should be able to outline their security practices and modify them based on your requirements, particularly as it relates to any industry-specific regulatory requirements you have.

    Summary

    The decision to pursue cloud computing is one that many organization have or will make as this technology grows and matures. But this decision need not be one fraught with uncertainty. With a little due diligence, and answering a few key questions, you can ensure that your cloud vendor selection is a sound one.





    How to Configure Wireless Encryption on a WLAN

    Wireless Encryption on a WLAN

    Wireless Router Configuration

                       Configuring the wireless security on a router can vary from router to router but the general options are the same. There are three main security options that typically are supported on modern routers, these include (listed from least to most secure):

    • Wireless Equivalent Privacy (WEP)
    • Wi-Fi Protected Access (WPA)
    • Wi-Fi Protected Access2 – IEEE 802.11i (WPA2)

    WEP typically requires that a key be entered on the router that will also be configured on the endpoint wireless devices. Routers that support WPA and/or WPA2 typically support two modes of operation: Personal Mode and Enterprise Mode. Personal Mode utilizes a passphrase (Pre-Shared Key – PSK) that is entered at both sides and is used to encrypt the connection. Enterprise Mode utilizes a connection to a remote authentication server which governs access onto the wireless network.

    This article takes a look at the configuration of WPA2-Personal configuration on a Linksys WRT610N router. This router supports only WPA2 (with the current firmware) and this is the configuration that will be shown.

    Configuring a Linksys WRT610N Wireless Router

    The first step is to log in to the router and to click on the Wireless option and from here navigate to the Wireless security tab; the Wireless Security tab screen is shown in figure
    Wireless Security Tab Screen

    On this screen, we are able to choose the security mode that is being configured. On this router WEP, WPA and WPA2 are supported; these options are shown in Figure
    Wireless Security Modes

    As stated previously, we will focus on the configuration of WPA2-Personal. Once the WPA2-Personal security option has been selected, what type of encryption to use needs to be determined. The two options on this router include:
    • Temporal Key Integrity Protocol (TKIP)
    • Advanced Encryption Standard (AES)
    Wireless Encryption Options

    Once the encryption option is selected, a passphrase is entered which is also used by the wireless client devices; typically it is best that this passphrase is complex.

    Windows 7 Wireless Configuration

    When configuring a wireless connection on a Windows 7 machine, there are two different methods that can be used to set up the connection and choose an encrypting method. The first connection uses the parameters transmitted from an existing wireless router and the second connection is configured in preparation for a future connection to a wireless router and requires some additional configuration. Let’s take a look at both.

    Connecting to a Broadcasting Wireless Router

    When a wireless network is broadcast from a wireless router and within range of a Windows 7 computer it is shown as a System Tray option, as shown in Figure
    Available Wireless Networks

    As shown in Figure , there are two networks that are within range of this Windows 7 computer; when a specific wireless network is selected the option to connect is offered. If the connection is to be repeatedly used, a wireless network can also be set up to connect automatically.
    Once the connect button has been selected, a dialog will be shown indicating the device is getting information from the wireless router; this dialog is shown in Figure
    Getting Information Dialog

    In this example, the wireless router has already been configured with a passphrase (security key).  The dialog shown in Figure 6 will be displayed asking for this passphrase to verify permission to connect to the wireless network. When using this method of wireless network connection, the specific security mode is automatically gathered with the initial connection to the wireless router.
    Passphrase Entry Dialog

    Once the client has connected to a wireless network, it will be displayed in the System Tray; this is shown in Figure
    Connected Wireless Network

    Configuring a Non-Local/Not Broadcasting Wireless Network connection

    The second method that is used to configure a wireless network connection is to manually configure a device to connect to a specific wireless network that is either not local or is not broadcasting. The intial setup for this type of configuration is to goto the Network and Sharing Center; this is shown in Figure
    Network and Sharing Center

    From this screen, the Manage Wireless Networks option in the upper left corner needs to be selected; this will bring up the screen shown in Figure
    Manage Wireless Networks

    From this screen, a Windows 7 device can be configured to support a number of different wireless networks. To configure a new network select the Add option; once this is selected the screen shown in Figure 10 will be displayed.
    Add a Wireless Network

    Once this screen is displayed, select the option to Manually Create a Network Profile; once this is selected the screen shown in Figure 11 will be displayed.
    Manual Wireless Connection Options

    Once this screen is displayed, the wireless network name and security settings will be configured; the available security type options are shown in Figure
    Manual Wireless Connection Security Type Options

    The settings that are configured on this screen must match those already configured on the connecting wireless router or a connection will not be established. Windows 7 supports all of the available wireless security types and can be configured to connect to any standard router.

    Summary

    The configuration of a wireless connection with proper security can be daunting for the inexperienced user.  With modern standards, the use of a passphrase that can be entered rather simply on both the wireless router and the end device allows anyone the ability to properly set this up within a short period of time. Hopefully, the steps outlined in this article enable this process to be even easier and provide a more secure wireless option.

    Pageviews

    Followers

    Blog Archive

    Powered by Blogger.

    - Copyright © 2013 Selva Sharing -Selvasharing- Powered by Blogger - Designed by @ Access -