Bitcoin RPC connection
RPC (remote procere call) is a kind of remote procere call. It is a protocol that requests service from remote computer program through network without knowing the underlying network technology
RPC assumes the existence of some transport protocols, such as TCP or UDP, to carry information and data between communication programs. In the OSI network communication model, RPC spans the transport layer and application layer. RPC makes it easier to develop applications including network distributed multiprogrammingRPC adopts client / server mode. The requester is a client and the service provider is a server. First, the client calls the process, sends a call information with process parameters to the service process, and then waits for the response information
extended data:
specific application operation
1. Inter process communication of distributed operating system
is one of the basic facilities that the operating system must provide. Distributed operating system must provide communication mechanism between processes distributed on heterogeneous node computers, RPC is one of the means to realize distributed interprocess communication in message transfer mode
Because of the geographical distribution of distributed software environment itself, there are a lot of interaction and communication among its components, and RPC is one of its basic implementation methods. Two popular distributed computing software environments, onc + and DCE, are constructed by RPC, and some other distributed software environments also use RPC In the distributed database system, the database generally resides on the server, and the client accesses the database server through the remote database service function. The existing remote database service uses RPC mode. For example, both Sybase and Oracle provide stored procere mechanism. The system and user-defined stored procere are stored on the database server, and the user calls the stored procere in RPC mode on the clientRPC is the abbreviation of remote procere call. In fact, the principle of RPC call in SAP system is very simple. There are some C / s systems similar to three-tier architecture. The third-party client program calls SAP internal standard or user-defined functions through the interface to obtain the data returned by the functions and display or print them after processing
Interprocess communication (IPC) is a communication technology used by programs and processes running between multitasking operating systems or networked computers. There are two types of interprocess communication (IPC)local procere call (LPC) LPC is used in a multitasking operating system to enable simultaneous tasks to talk to each other. These tasks share memory space to synchronize tasks and send information to each other. Remote procere call (RPC) RPC is similar to LPC, only works on the Internet. RPC began to appear in Sun Microsystems and HP's computers running UN IX operating system
extended data
through IPC and RPC, programs can use other programs or computer processing processes. The client / server computing model takes remote procere call as a mechanism of inter system communication together with other technologies (such as message passing). Clients perform their own tasks, but rely on the server to provide back-end file services
RPC provides a communication mechanism for clients to apply for services from back-end servers, as shown in figure R-4. If you think of the client / server application as a separate program, the server can run the data access part because it is closest to the data, and the client can run the front-end part of data representation and user interaction. In this way, remote procere call can be regarded as a component to reorganize the divided program through the network. LPC is sometimes called coupling mechanism
in this way, when users want to access data, they don't need to the whole database or most of its programs to the user system each time. In fact, the server only processes requests, even performs some data calculations, and sends the results to users. Because when the data is stored in one place, database synchronization is easy to achieve, so multiple users can access the same data at the same time
Distributed computing environment is composed of a communication system network connected computer cluster. It's easy to see the network as a computing platform. If it's peer-to-peer, any computer can be a client or serversome processing tasks can be divided into independent programs running in parallel on different network computers, and independent programs are handed over to the most suitable computer for this task. This strategy can make use of computer idle resources and improve the efficiency of the network. A typical enterprise network includes many heterogeneous computer systems running different operating systems
I hope my answer can help you. If you don't understand anything, you can ask.
method 1: modify the registry method
click "start → run", type "regedit" to open the "Registry Editor", and expand the branch "HKEY"_ LOCAL_ MACHINE\ SYSTEM\ CurrentControlSet\ Services\ Method 2: use the sc.exe command
click "start → run", type "CMD" to enter the "command prompt" window, type "SC config RPCs start = Auto" command, and the system will display "[SC] changeserviceconfig success", This enables the RPC service to start successfully
note: if you want to use the "SC" command, you must install the windows 2000 / 2003 Resource Kit (Resource Kit), otherwise it is invalid to use this command
method 3: use the recovery console
take Windows XP system as an example, put the installation CD in the CD-ROM drive, and set the BIOS parameters to boot from CD-ROM; After starting the computer, the system will enter the Windows XP installation interface, press the "R" key to log in to the recovery console. In the recovery console, type "enable RPCs service"_ auto_ After that, you can restart the system and log in in the normal mode to start the RPC service successfully
note: "enable" is a command provided by the recovery console to start system services and device drivers. It can only be used in the recovery console
SC command
"SC" command is a command provided by Windows 2000 resource kit to communicate with system services, and "SC config" is one of its subcommands, which is used to modify service items in the configuration registry or service database. The command format is as follows:
SC < server > config [service name] < option1 > < option2 >...
parameter options: start = < boot system auto demand disabled >
where "server" is the name of the server, which is used on the local machine. This option can be omitted, and the command is executed on the local machine by default“ The parameter options of "start" include "boot, system, auto, demand and disabled", and the latter three correspond to "automatic, manual and disabled".
there is a flaw in the part of RPC dealing with message exchange over TCP / IP. Incorrectly handling malformed messages can cause errors. This particular error affects the underlying DCOM interface, which listens on TCP / IP port 135. By sending a malformed RPC message, an attacker can cause a problem with the RPC service on a computer, and then enable arbitrary code to be executed
remote procere call (RPC) is a protocol used by Windows operating system. RPC provides an interprocess communication mechanism, through which programs running on a computer can smoothly execute the code on a remote system. The protocol itself is derived from OSF (Open Software Foundation) RPC Protocol, only adding some Microsoft specific extensions
there is a vulnerability in the part of RPC that handles message exchange over TCP / IP. This problem is caused by incorrect handling of malformed messages. This particular vulnerability affects an interface between distributed component object model (DCOM) and RPC that listens on TCP / IP port 135. This interface handles DCOM object activation requests (such as universal naming convention (UNC) paths) sent by client computers to servers
to exploit this vulnerability, an attacker may need to send a special format request to port 135 on a remote computer<
mitigating factors:
to exploit this vulnerability, an attacker may need to have the ability to send a crafted request to port 135 on a remote computer. For Intranet environment, this port is usually accessible; But for computers connected through Internet, firewall usually blocks port 135. If the port is not blocked, or in an intranet environment, the attacker does not need any other privileges
the best practice is to block all actually unused TCP / IP ports. Therefore, most computers connected to the Internet should block port 135. RPC over TCP is not suitable for use in dangerous environment such as Internet. More robust protocols like RPC over HTTP are suitable for potentially dangerous environments
this is a buffer overflow vulnerability. An attacker who successfully exploits this vulnerability may gain full control of the remote computer. This may allow an attacker to perform arbitrary operations on the server, including changing the web page, reformatting the hard disk, or adding new users to the local Administrators group
to launch such an attack, an attacker needs to be able to send a malformed message to the RPC service, thus causing the target computer to be controlled by others, and the attacker can execute arbitrary code on it
the best way to prevent remote RPC attacks from the Internet is to configure the firewall to block port 135. RPC over TCP is not suitable for use in dangerous environment such as Internet
this vulnerability is caused by the failure of windows RPC service to check message input correctly in some cases. If an attacker sends some type of RPC message with incorrect format after establishing a connection with RPC, it will cause problems in the basic distributed component object model (DCOM) interface between the remote computer and RPC, and then enable arbitrary code to be executed.
