RPC Authentication Constant


i am working on an api use the rpc_c_authn_level_pkt_privacy windows constant secure tcp/ip data/connections. description follows:"

"includes previous levels, , ensures clear test data can seen sender , receiver. in local case, involves using secure channels. in remote case, involves encrypting argument value of each remote procedure call."

this brings many questions such as:

1) considered local , remote connections? based off of domain?

2) how "secure" a channel? encrypt data well? secure data or pipe?

3) if encryption used, local or remote, type of encryption being used.

this rpc connection needs secure , know details on how secure be.

hi,

for first question, point of view, local connection means rpc server , client same machine, means rpc message not travel on network.

for reset of questions, please check if following link helpful:

https://msdn.microsoft.com/en-us/library/windows/desktop/aa378642(v=vs.85).aspx

https://technet.microsoft.com/en-us/library/cc738291(v=ws.10).aspx

besides, coding related questions, msdn forum might more suitable. suggest post questions on msdn forum better help.

best regards,


steven lee please remember mark replies answers if , unmark them if provide no help. if have feedback technet support, contact tnmff@microsoft.com.



Windows Server  >  Security



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group