I Need To Know About RDP

KevinBro

Carder
Messages
32
Reaction score
5
Points
8
I NEED TO KNOW ABOUT RDP...
  • How Many Times We Can Use RDP ?
  • RDP Valid Time ?
  • Can We Use RDP Without Proxy ?
  • Can We Use RDP + FREE VPN
  • Can We Bypass Anti Fraud System And Change Location Correctly By Only Using RDP
  • Can We Buy RDP For Cc Owner Zip
  • As A Example Can We Use RDP For 10 + CC's For Different Cc Owners In Same Zip





 
Please note, if you want to make a deal with this user, that it is blocked.
1. You can only one RDP user session at a time.
2. Yes you can use RDP without proxy.
3. no you can't use RDP plus free VPN. If you add vpn you carding wont be successful
4. Yes you can bypass anti fraud with RDP.
5.
 
Can We Buy RDP For Cc Owner Zip
As A Example Can We Use RDP For 10 + CC's For Different Cc Owners In Same Zip
 
RDP. The three letter game.
As you know, the Remote Desktop Protocol (RDP) allows you to connect remotely to computers running Windows and is available to any Windows user, as long as they do not have the Home version, where there is only an RDP client, but not a host. It is a convenient, efficient and practical tool for remote access for administration purposes or everyday work. Recently, it has caught the eye of miners who use RDP for remote access to their farms. RDP support It has been included in Windows since NT 4.0 and XP, but not everyone knows how to use it. Meanwhile, you can open the Microsoft Remote Desktop from Windows or Mac OS X computers, as well as from Android mobile devices or from iPhone and iPad.

If you properly understand the settings, then RDP will be a good means of remote access. It allows you not only to see the remote desktop, but also to use the resources of the remote computer, connect local disks or peripherals to it. In this case, the computer must have an external IP (static or dynamic), or it must be possible to "forward" the port from the router with an external IP address.

RDP servers are often used for collaboration in the 1C system, or users ' jobs are deployed on them, allowing them to connect to their workplace remotely. The RDP client allows you to work with text and image applications, and remotely receive some data from your home PC. To do this, you need to forward port 3389 on the router in order to access the home network via NAT. This also applies to setting up an RDP server in your organization.

RDP is considered by many to be an insecure method of remote access compared to using special programs such as RAdmin, TeamViewer, VNC, etc. Another prejudice is high RDP traffic. However, today RDP is no less secure than any other remote access solution (we will return to the security issue later), and with the help of settings, you can achieve high response speed and low bandwidth requirements.

How to protect RDP and configure its performance
Encryption and SecurityYou need to open gpedit. msc, in "Computer Configuration-Administrative Templates-Windows Components-Remote Desktop Services-Security" set the parameter "Require using a special security level for remote connections using the RDP method "and in" Security level "select" SSL TLS". In "Set encryption level for client connections", select "High". To enable the use of FIPS 140-1, go to "Computer Configuration-Windows Configuration-Security Settings-Local Policies — Security Settings "and select" System Cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing". The "Computer Configuration-Windows Settings-Security Settings-Local Policies — Security Settings" option the "Accounts: Allow empty passwords only for console login" option must be enabled. Check the list of users who can connect via RDP.
OptimizationOpen "Computer Configuration-Administrative Templates-Windows Components-Remote Desktop Services — Remote Session Environment". In "Maximum color depth", select 16 bits, this is enough. Uncheck "Force cancellation of remote desktop background". In "Setting an RDP compression algorithm", select " Optimize bandwidth usage. In Optimize Visual Effects for Remote Desktop Services Sessions, set the value to Text. Disable "Font Smoothing".
Basic configuration is completed. How do I connect to a remote desktop?

Connecting to a remote desktop
To connect via RDP, you must have an account with a password on the remote computer, remote connections must be allowed in the system, and in order not to change access data with a constantly changing dynamic IP address, you can assign a static IP address in the network settings. Remote access is only possible on Windows Pro, Enterprise, or Ultimate computers.

To connect remotely to a computer, you need to allow the connection in "System Properties" and set a password for the current user, or create a new user for RDP. Users of regular accounts do not have the right to provide their own computer for remote management. The administrator can grant them this right. An obstacle to using the RDP protocol may be its blocking by antivirus programs. In this case, RDP should be allowed in the settings of antivirus programs.

It is worth noting the peculiarity of some server operating systems: if the same user tries to log in to the server locally and remotely, the local session is closed and the remote one opens in the same place. Conversely, logging in locally will close the remote session. If you log in locally under one user and remotely under another, the system will terminate the local session.

An RDP connection is made between computers located on the same local network or over the Internet, but this requires additional actions – forwarding port 3389 on the router, or connecting to a remote computer via VPN.

To connect to a remote desktop in Windows 10, you can allow remote connection in Settings-System-Remote Desktop and specify the users to grant access to, or create a separate user to connect to. By default, the current user and administrator have access. On the remote system, run the connection utility.

Press Win+R, type MSTSC, and press Enter. In the window, enter the IP address or computer name, select "Connect", enter the user name and password. The remote computer screen appears.

When connecting to a remote desktop via the Command line (MSTSC), you can set additional RDP parameters:
ParameterMeaning
/v:<server [: port]>The remote computer that you are connecting to.
/adminConnecting to a session for server administration.
/editEditing the RDP file.
/fLaunch remote Desktop in full screen mode.
/w:<width>Width of the remote desktop window.
/h:<height>Height of the remote desktop window.
/publicStart the remote desktop in general mode.
/spanMap the width and height of the remote desktop to the local virtual desktop and deploy to multiple monitors.
/multimonConfigures the placement of RDP session monitors according to the current client-side configuration.
/migrateMigrating connection files from previous versions to new RDP files.

For Mac OS, Microsoft has released an official RDP client that works stably when connected to any version of Windows. On Mac OS X, to connect to a Windows computer, you need to download the Microsoft Remote Desktop app from the App Store. You can use the "Plus" button to add a remote computer: enter its IP address, user name, and password. Double-click on the remote desktop name in the list to connect to opens the Windows desktop.

On smartphones and tablets running Android and iOS, you need to install the Microsoft Remote Desktop application ("Microsoft Remote Desktop") and run it. Select " Add " and enter the connection parameters — the computer's IP address, login and password to log in to Windows. Another way is to forward port 3389 on the router to the computer's IP address and connect to the router's public address with this port specified. This is done using the Port Forwarding option of the router. Select Add and enter:
Code:
Name: RDP
Type: TCP & UDP
Start port: 3389
End port: 3389
Server IP: The IP address of the computer to connect to.

What about Linux? RDP is a closed protocol of Microsoft, it does not release RDP clients for Linux, but you can use the Remmina client. For Ubuntu users, there are special repositories with Remmina and RDP.

The RDP protocol is also used for connecting to Hyper-V VMs. Unlike the hypervisor connection window, when connecting via RDP, the VM sees various devices connected to the physical computer, supports working with sound, gives a better image of the guest OS desktop, and so on.

For virtual hosting providers Windows VPS servers are usually also available for connecting via the standard RDP protocol by default. When using the standard Windows operating system to connect to the server, just select: "Start-Programs-Accessories-Remote Desktop connection" or press Win+R and type MSTSC in the window that opens. Enter the IP address of the VPS server in the window.

By clicking the "Connect" button, you will see a window with authorization fields.

To make sure that the server has access to USB devices and network printers connected to your PC, select "Show Settings" in the lower-left corner when connecting to the server for the first time. In the window, open the "Local Resources" tab and select the required parameters.

Using the option to save authorization data on a remote computer, you can save the connection parameters (IP address, username, and password) in a separate RDP file and use it on another computer.

You can also use RDP to connect to Azure VMs.

Configuring other remote access functionality
In the Remote computer connection window, there are tabs with configurable parameters.
TabAppointment
"Screen"Sets the screen resolution of the remote computer, i.e. the utility window after connection. You can set a low resolution and sacrifice color depth.
"Local resources"To save system resources, you can disable audio playback on the remote computer. In the Local devices and section, you can select the printer and other devices of the main computer that will be available on the remote PC, such as USB devices, memory cards, and external disks.

Learn more about configuring remote desktop in Windows 10 in this video. Now back to RDP security.

How to hijack an RDP session?
Can I intercept RDS sessions? And how to protect yourself from this? The possibility of hijacking an RDP session in Microsoft Windows has been known since 2011, and a year ago the researcher Alexander Korznikov in his blog described in detail the methods of theft. It turns out that it is possible to connect to any running session in Windows (with any rights), being logged in under some other one.

Some techniques allow you to intercept a session without a username and password. You only need access to the NT AUTHORITY/SYSTEM command line. If you run tscon.exe As a SYSTEM user, you can connect to any session without a password. RDP doesn't ask for a password, it just connects you to the user's desktop. You can, for example, dump the server's memory and get user passwords. By simply launching it tscon.exe with the session number, you can get the desktop of the specified user — without external tools. Thus, with a single command, we have a hacked RDP session. You can also use the utility psexec.exe, if it was pre-installed:
Code:
psexec -s \\localhost cmd

Alternatively, you can create a service that will connect the attacked account and launch it, after which your session will be replaced by the target one. Here are some notes on how far this allows you to go:
  • You can connect to disconnected sessions. So if someone logged out a couple of days ago, you can just connect directly to their session and start using it.
  • You can unblock blocked sessions. So while the user is away from their workplace, you log in to their session and they are unblocked without any credentials. For example, an employee logs in to their account, then leaves after blocking the account (but not logging out). The session is active and all applications will remain in the same state. If the system administrator logs in to his own account on the same computer, he gets access to the employee's account, and therefore to all running applications.
  • If you have local administrator rights, you can attack an account with domain administrator rights, i.e. higher than the attacker's rights.
  • You can connect to any session. If, for example, this is Helpdesk, you can connect to it without any authentication. If this is a domain administrator, you will become an administrator. With the ability to connect to disconnected sessions, you get an easy way to move around the network. Thus, attackers can use these methods both for penetration and for further promotion within the company's network.
  • You can use win32k exploits to get SYSTEM permissions, and then use this feature. If patches are not applied properly, this is available even to the average user.
  • If you don't know what to track, you won't know what's going on at all.
  • This method works remotely. You can run sessions on remote computers even if you are not logged in to the server.
Many server operating systems are affected by this threat, and the number of servers using RDP is constantly increasing. Windows 2012 R2, Windows 2008, Windows 10, and Windows 7 were found to be vulnerable. To prevent RDP sessions from being hijacked, we recommend using two-factor authentication. The updated Sysmon Framework for ArcSight and Sysmon Integration Framework for Splunk warn the administrator about running malicious commands to hijack the RDP session. You can also use the Windows Security Monitor utility to monitor security events.

Finally, let's look at how to delete a remote desktop connection. This is a useful measure if you no longer need remote access, or if you want to prevent unauthorized users from connecting to the remote desktop. Open "Control Panel-System and Security-System". In the left column, click "Configure Remote access". In the "Remote Desktop" section, select "Do not allow connections to this computer". Now no one will be able to connect to you via remote desktop.

In conclusion, here are some more life hacks that can be useful when working with the remote desktop of Windows 10, and just for remote access.
  1. You can use OneDrive to access files on a remote computer:
  2. How to restart a remote PC in Win10? Press Alt+F4. A window opens:
    An alternative option is the command line and the shutdown command.
    If you specify the /i parameter in the shutdown command, a window will appear:
  3. In Windows 10 Creators Update, the "System" section has become richer for another subsection, where you can activate remote access to your computer from other operating systems, in particular, from mobile devices using the Microsoft Remote Desktop application.:
  4. For various reasons, the RDP connection to the Windows Azure VM may not work. The problem may be with the remote desktop service on the VM, the network connection, or the client's remote desktop client on your computer. Some of the most common methods for solving the RDP connection problem are listed here.
  5. From the regular version of Windows 10, it is quite possible to make a terminal server, and then several users can connect to a regular computer via RDP and simultaneously work with it. As noted above, it is now popular for multiple users to work with the 1C file database. A tool that has proven itself well in Windows 7 — RDP Wrapper Library by Stas ' - will help turn Windows 10 into a terminal server.
  6. You can use Parallels Remote Application Server (RAS) as a" human-facing RDP", but some of its features must be configured on the Windows Server side (or in the virtual machines that you use).
As you can see, there are many solutions and opportunities that open up remote access to a computer. It is no coincidence that most businesses, organizations, institutions, and offices use it. This tool is useful not only for system administrators, but also for managers of organizations, and remote access is also very useful for ordinary users. You can help a person who doesn't know how to fix or optimize the system without getting up from his chair, transfer data or get access to the necessary files while on a business trip or vacation anywhere in the world, work at an office computer from home, manage your virtual server, etc.

Good luck!
 
The Remote Desktop protocol. Architecture and features.
This article opens a series of articles on the design and security of the RDP protocol. The first article in this series analyzes the device, usage, and core technologies embedded in this protocol.

This article opens a series of articles on the design and security of the RDP protocol. The first article in this series analyzes the device, usage, and core technologies embedded in this protocol.

The following articles will address the following issues in detail:
  • Operation of the Remote Desktop security subsystem
  • Service information exchange format in RDP
  • Terminal server vulnerabilities and solutions
  • Selection of user accounts using the RDP protocol (developed by Positive Technologies in this area)

History of RDP implementation
The Remote Desktop protocol was created by Microsoft to provide remote access to Windows servers and workstations. The RDP protocol is designed to use the resources of a high-performance terminal server by many less productive workstations. For the first time, the terminal server (version 4.0) appeared in 1998 as part of the Windows NT 4.0 Terminal Server. At the time of writing (January 2009), the latest version of the terminal server is version 6.1, included in the distributions of Windows 2008 Server and Windows Vista SP1. Currently, RDP is the main remote access protocol for Windows family systems, and client applications exist for both Microsoft's OC and Linux, FreeBSD, MAC OS X, etc.

Speaking about the history of RDP, Citrix should be mentioned. Citrix Systems in the 1990s specialized in multi-user systems and remote access technologies. After acquiring the Windows NT 3.51 source code license in 1995, the company released a multi-user version of Windows NT, known as WinFrame. In 1997, Citrix Systems and Microsoft signed an agreement under which the multi-user Windows NT 4.0 environment was based on Citrix's technological developments. In turn, Citrix Systems refused to distribute a full-fledged operating system and received the right to develop and implement extensions for Microsoft products. These extensions were originally called MetaFrame. The rights to ICA (Independent Computing Architecture), an application protocol for interacting thin clients with the Citrix application server, remained with Citrix Systems, and the Microsoft RDP protocol was built on the basis of ITU T. 120.

Currently, the main competition between Citrix and Microsoft has flared up in the field of application servers for small and medium-sized businesses. Traditionally, solutions based on Terminal Services win in systems with a small number of servers of the same type and similar configurations, while Citrix Systems is firmly established in the market of complex and high-performance systems. Competition is fueled by the release of lightweight solutions for small systems by Citrix and the constant expansion of Terminal Services functionality by Microsoft.
Consider the advantages of these solutions.

Strengths of Terminal Services:
  • Easy installation of applications for the client side of the application server
  • Centralized maintenance of user sessions
  • Need to have a license only for Terminal Services

Strengths of Citrix solutions:
  • Easy to scale
  • Ease of administration and monitoring
  • Access Control Policy
  • Support for third-party enterprise products (IBM WebSphere, BEA WebLogic)

Network device that uses Terminal Services
Microsoft assumes two modes of using the RDP protocol:
  • for administration (Remote administration mode)
  • to access the application server (Terminal Server mode)

RDP in administration mode
This type of connection is used by all modern Microsoft operating systems. Server versions of Windows support two remote connections and one local login at the same time, while client versions only support one login (local or remote). To allow remote connections, you must enable remote desktop access in the workstation properties.

RDP in terminal server access mode
This mode is only available in server versions of Windows. The number of remote connections is not limited in this case, but you need to configure the License server and then activate it. The license server can be installed either on a terminal server or on a separate network node. Remote access to the terminal server is available only after the corresponding licenses are installed on the License server.
When using a cluster of terminal servers and load balancers, you need to install a dedicated connection server (Session Directory Service). This server indexes user sessions, which allows you to log in and re-log in to terminal servers running in a distributed environment.

How RDP works
Remote Desktop is an application protocol based on TCP. After the connection is established, an RDP session is initialized at the transport layer, where various data transfer parameters are agreed upon. After successful completion of the initialization phase, the terminal server starts transmitting graphical output to the client and waits for input data from the keyboard and mouse. The graphic output can be either an exact copy of the graphic screen, transmitted as an image, or commands for drawing graphic primitives ( rectangle, line, ellipse, text, etc.). Transmitting output using primitives is a priority for the RDP protocol, as it significantly saves traffic; and the image is transmitted only if otherwise it is impossible for some reason (it was not possible to agree on the parameters for transmitting primitives when installing an RDP session). The RDP client processes the received commands and outputs images using its graphics subsystem. By default, user input is transmitted using keyboard scan codes. The key press and release signal is transmitted separately using a special flag.

RDP supports multiple virtual channels within a single connection, which can be used to provide additional functionality:
  • using a printer or serial port
  • file system redirection
  • support for working with the clipboard
  • using the audio subsystem
The characteristics of virtual channels are agreed upon at the connection setup stage.

Ensuring security when using RDP
The RDP protocol specification provides for one of two security approaches:
  • Standard RDP Security (built-in security subsystem)
  • Enhanced RDP Security (external security subsystem)

Standard RDP Security
With this approach, authentication, encryption,and integrity assurance are implemented using the RDP protocol.

Authentication
Server authentication is performed as follows:
  1. At system startup, a pair of RSA keys is generated
  2. A Proprietary Certificate of the public key is created
  3. The certificate is signed with an RSA key embedded in the operating system (any RDP client contains the public key of this embedded RSA key).
  4. The client connects to the terminal server and receives a Proprietary Certificate
  5. The client verifies the certificate and receives the server's public key (this key is used later to negotiate encryption parameters).
The client is authenticated by entering a username and password.

Encryption
The RC4 stream cipher is chosen as the encryption algorithm. Depending on the operating system version, different key lengths are available, from 40 to 168 bits.
Maximum key length for Windows operating systems:
  • Windows 2000 Server – 56 bits
  • Windows XP, Windows 2003 Server – 128 bits
  • Windows Vista, Windows 2008 Server – 168 bits
When a connection is established, after matching the length, two different keys are generated: for encrypting data from the client and from the server.

Integrity
Message integrity is achieved by using the MAC (Message Authentication Code) generation algorithm based on the MD5 and SHA1 algorithms.
Starting with Windows 2003 Server, to ensure compatibility with the requirements of the Federal Information Processing Standard (FIPS) 140-1, it is possible to use the 3DES algorithm for message encryption and the SHA1-only MAC generation algorithm for integrity.

Enhanced RDP Security
This approach uses external security modules:
  • TLS 1.0
  • CredSSP
The TLS protocol can be used starting with the Windows 2003 Server version, but only if the RDP client supports it. TLS support is added starting with the RDP client version 6.0.
When using TLS, you can generate a server certificate using Terminal Services or select an existing certificate from the Windows store.
The CredSSP protocol is a combination of TLS, Kerberos, and NTLM functionality.

Consider the main advantages of the CredSSP protocol:
  • Checking permission to log in to the remote system before setting up a full-fledged RDP connection, which saves terminal server resources with a large number of connections
  • Strong authentication and TLS encryption
  • Using Single Sign On using Kerberos or NTLM
CredSSP features can only be used on Windows Vista and Windows 2008 Server operating systems. This protocol is enabled by using the Use Network Level Authentication flag in the terminal server settings (Windows 2008 Server) or in the remote access settings (Windows Vista).

Terminal Services Licensing Scheme
When using RDP to access applications in thin client mode, you need to configure a dedicated license server.
Permanent client licenses can be installed on the server only after the activation procedure is completed.Temporary licenses can be issued with a limited validity period before the activation procedure is completed. After activation, the license server is provided with a digital certificate confirming its ownership and authenticity. Using this certificate, the license server can perform subsequent transactions with the Microsoft Clearinghouse database and accept permanent client licenses for the terminal server.

Types of client licenses:
  • temporary license (Temporary Terminal Server CAL)
  • Device Terminal Server CAL license
  • per-user license (User Terminal Server CAL)
  • license for external users (External Terminal Server Connector)

Temporary license
This type of license is issued to the client when they first connect to the terminal server. The license is valid for 90 days. Upon successful login, the client continues to work with the temporary license, and the next time it connects, the terminal server tries to replace the temporary license with a permanent one, if it is available in the storage.

Per-device license
This license is issued for each physical device that connects to the application server. The license validity period is set randomly between 52 and 89 days. 7 days before the expiration date, the terminal server tries to update the license from the license server every time the client connects again.

Per-user license
Per-user licensing provides additional flexibility by allowing users to connect from a variety of devices. The current implementation of Terminal Services does not have any user license usage controls, i.e. the number of available licenses on the license server does not decrease when new users are added. Using an insufficient number of licenses for client connections violates the license agreement with Microsoft. To use both device and user client licenses on the same terminal server at the same time, the server must be configured to operate in per-user licensing mode.

License for external users
This is a special type of license intended for connecting external users to a corporate terminal server. This license does not impose restrictions on the number of connections, however, according to the user agreement( EULA), the terminal server for external connections must be dedicated, which does not allow it to be used for servicing sessions from corporate users. Due to the high price, this type of license is not widely used.

One of two roles can be set for the license server:
  • Domain or Workgroup License server
  • Entire Enterprise License Server
Roles differ in the way they detect the license server: when using the Enterprise role, the terminal server searches for the license server in the ActiveDirectory directory, otherwise the search is performed using a NetBIOS broadcast request. Each server found is checked for correctness using an RPC request.

Advanced Terminal Services technologies
Solutions for application servers are actively promoted by Microsoft, the functionality is being expanded, and additional modules are being introduced. Technologies that simplify the installation of applications and components responsible for the operation of the terminal server in global networks have received the greatest development.

Terminal Services for Windows 2008 Server introduces the following features:
  • Terminal Services Printing-allows you to use the client's printer to print from applications on the terminal server.
  • Terminal Services RemoteApp-provides access to any applications through the terminal service. In this case, the terminal server becomes completely transparent to the user.
  • Terminal Services Web Access-allows clients to connect to RemoteApp applications using a regular browser. The Web server acts as a link for RemoteApp.
  • Terminal Services Gateway-this technology organizes RDP operation over an established HTTPS connection. TS Gateway allows remote users to connect to the application server via regional networks or the Internet using a secure SSL tunnel and with minimal configuration of network devices.
  • Terminal Services Session Broker - allows you to organize user connections to server platforms that use network load balancing.
 
How Many Times We Can Use RDP?
You can use the RDP as many times as you like while it is alive.
It is practically advisable to use RDP for 1 session, that is, 1 RDP = 1 CC or more.

RDP Valid Time?
RDP lives until an illegal connection is detected by the server owner.

Can We Use RDP Without Proxy?
You can use RDP both in conjunction with a proxy and without a proxy, if the RDP matches the cardholder address.
It is advisable to work with home RDPs if you have a regular card and a business RDP if you have a corporate card.

Can We Use RDP + FREE VPN
Yes, it is quite possible to link the RDP with both free and paid VPN.

Can We Bypass Anti Fraud System And Change Location Correctly By Only Using RDP
RDP exists in order to bypass the anti-fraud system. If the anti-fraud system does not notice that you are connected through the RDP, then the card payment will be successful.

Can We Buy RDP For Cc Owner Zip
Yes, you can choose the RDP for the cardholder's address. If the seller of the RDP of the city you need, then you can try to buy the RDP, which corresponds to the region (district) or country of the cardholder.

As A Example Can We Use RDP For 10 + CC's For Different Cc Owners In Same Zip
Yes, you can use 1 RDP for any number of CCs, if they match the address.
But at the same time, you must work on DIFFERENT sites and a DIFFERENT antifraud system, since if you work on 1 site, but the antifraud system will record a fingerprint of your device and when you try to pay with 2 cards, a payment rejection may be caused.
 
Top