United States (English)

Home Library Learn Samples Downloads Support Community Forums

MSDN Library

Windows Desktop App Development

Develop

Desktop App Technologies

Networking and Internet

Remote Procedure Call (RPC)

Best RPC Programming Practices

Writing a Secure RPC Client or Server

Which Security Provider to Use

Controlling Client Authentication

Choosing an Authentication Level

Choosing Security QOS Options

Common Mistake: Assuming RpcServerRegisterAuthInfo Prevents Unauthorized Users from Calling your Server

Callbacks

Null Sessions

Use the /robust Flag

Strict and Type Strict Context Handles

Do Not Trust Your Peer

Do Not Use Endpoint Security

Be Wary of Other RPC Endpoints Running in the Same Process

Verify the Server is Who it Claims to Be

Use Mainstream Protocol Sequences

How Secure is My RPC Server Now?

IDL Techniques for Better Interface and Method Design

Minimize

This topic has not yet been rated - Rate this topic

How Secure is My RPC Server Now?

Following the security outlined in this section, provided elsewhere in the RPC SDK, and generally accepted as proper security practices, will result in a server that is very secure. Such servers are protected from penetration attacks or privacy breaches.

If state is kept between RPC calls, make sure a single client does not cause the allocation of excessive resources, which could potentially deny service to other clients.

Send comments about this topic to Microsoft

Build date: 11/23/2012

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

© 2013 Microsoft. All rights reserved.