Join today and have your say! It’s FREE!

Become a member today, It's free!

We will not release or resell your information to third parties without your permission.
Please Try Again
{{ error }}
By providing my email, I consent to receiving investment related electronic messages from Stockhouse.

or

Sign In

Please Try Again
{{ error }}
Password Hint : {{passwordHint}}
Forgot Password?

or

Please Try Again {{ error }}

Send my password

SUCCESS
An email was sent with password retrieval instructions. Please go to the link in the email message to retrieve your password.

Become a member today, It's free!

We will not release or resell your information to third parties without your permission.

Cyberark Software Ltd CYBR

CyberArk Software Ltd is an Israel-based provider of information technology (IT) security solutions that protect organizations from cyber-attacks. The Company's software solutions are focused on protecting privileged accounts, which have become a critical target in the lifecycle of cyber-attacks. The Company's Privileged Account Security Solution consists of various products, such as Shares Technology Platform, Enterprise Password Vault, SSH Key Manager, Privileged Session Manager, Privileged Threat Analytics, Application Identity Manager, CyberArk-Conjur, Endpoint Privilege Manager and On-Demand Privileges Manager. The Company's products protect against external and internal cyber threats and enable detection and neutralization of attacks. The Company's Enterprise Password Vault provides customers with a tool to manage and protect all privileged accounts across an entire organization, including physical, virtual, or cloud-based assets.


NDAQ:CYBR - Post by User

Bullboard Posts
Post by elenakretova23on Mar 31, 2018 6:06am
157 Views
Post# 27809884

Preventing duplicate blockchain attack

Preventing duplicate blockchain attack
Trusting somebody can enable me to answer an inquiry in regards to a potential assault that could happen with a blockchain. 
 
Assume Alice is attempting to assault Bob by sending him false blockchains. In this situation, assume Alice needs to over and again send a blockchain that records that Bob owes Alice $10, and she has effectively discovered a proof of work that makes a fitting hash. 
 
What is there to prevent Alice from taking this square, and broadcasting it more than once to Bob so that on his side, he sees a developing Blochchain, each with a record that he owes Alice? 
 
From what I comprehend, the way that the "genuine" blockchain is resolved is by a matter of size. So as long as Alice communicates her phony square to Bob rapidly enough, wouldn't her records give off an impression of being the right blockchain that Bob would then need to acknowledge?
Bullboard Posts