Bitcoin Forum
November 15, 2018, 12:55:24 AM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: bitcoind spam  (Read 531 times)
p2pbucks
Hero Member
*****
Offline Offline

Activity: 652
Merit: 500


Evolution is the only way to survive


View Profile
December 29, 2014, 11:03:57 AM
 #1

hey guys,

If someone maliciously sends tons of  json-rpc command thru a website interface . (eg , bitcoind->getinfo() or bitcoind->getnewaddress() ..etc)
Does the backend bitcoind exit automatically ?
how many json-rpc commands one bitcoind(core) server could handle ? I wanna know the capacity .

Thanks  : )
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1542243324
Hero Member
*
Offline Offline

Posts: 1542243324

View Profile Personal Message (Offline)

Ignore
1542243324
Reply with quote  #2

1542243324
Report to moderator
1542243324
Hero Member
*
Offline Offline

Posts: 1542243324

View Profile Personal Message (Offline)

Ignore
1542243324
Reply with quote  #2

1542243324
Report to moderator
mstfck
Member
**
Offline Offline

Activity: 79
Merit: 10

I was hacked. Sorry for any scam that occured.


View Profile
December 29, 2014, 11:44:30 AM
 #2

No, it doesn't.
If you are integrating bitcoind calls into your service it should only be accessible by localhost/127.0.0.1 so only the site can make rpc calls. If you are worried that someone will be making alot of requests, you can make a custom spam blocker server side.

EDIT: Not sure if it crashes if enough requests is made though, I believe it depends on the machine it runs on.

I was inactive on this forum and apparently someone got my credentials and used my account in scams.
I have changed the password and I am sorry for any scam that occured.
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!