Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - karnal

Pages: 1 ... 53 54 55 56 57 58 59 [60] 61 62 63 64 65 66 67 ... 72
886
General Discussion / Re: POLONIEX now KYC compliant
« on: May 22, 2015, 03:43:04 pm »
WARNING: Have seen several people on IRC confirm that their new accounts are not receiving the email necessary to confirm disabling withdrawal notification by email.

The facts: There is a newspost from May 19 that claims they are having issues with "sending withdrawal emails to some ISPs"

The speculation: They are enticing people to transact under the $2000/day limit without factual verification, only to fsck them over when it's time to withdraw and the email never arrives. Presumably at this point Poloniex would hold your funds until further verification can be done.



Their tech support says it's "a problem with the receiver ISP". However, the emails to register the account arrived minutes earlier, no problem.
That does not look like a smtp problem, at all.



887
Technical Support / Re: DDoSing the BitShares network
« on: May 22, 2015, 03:37:51 pm »
Quote from: xeroc ¯\_(ツ)_/¯ on May 22, 2015, 09:13:41 am
Quote from: karnal on May 22, 2015, 08:44:32 am
- I thought the delegate *was* the signing machine?
- What exactly does --incoming-connections 0 (besides the obvious)?
- How would the setup you describe (proxy clients, signer machine) work ?
  - And if incoming-connections=0, how do "proxy clients connect to the server" ?
the delegate is the signing machine .. it can be hidde behind a proxy full node that does hand over the signed block to the rest of the P2P network ..
the delegate is not connected to the P2P network directly ..
in essence it is the same as

http://digitalgaia.io/backbone.html

How would you go about setting this up? By having the delegate connect only to certain nodes in the config file?

888
General Discussion / Re: Bitshares Infographic
« on: May 22, 2015, 11:37:10 am »
Quote from: Ander on May 21, 2015, 10:28:13 pm
This is an excellent presentation!  We need to use it more.  I hope this will be a significant part of future marketing efforts.

+5% +5% +5% +5% +5% +5%

889
General Discussion / Re: bitsharesblocks.com often won't load when accessed over Tor
« on: May 22, 2015, 11:33:53 am »
Still having the same issue. Tried to load the site 5 times with tor, 0% success rate (stuck @ "Loading" with blue thing spinning)

Tried 5 times without tor, 100% success rate.


Either I'm the most unlucky guy in the galaxy, or something is up :P

890
Technical Support / Re: DDoSing the BitShares network
« on: May 22, 2015, 08:46:38 am »
Quote from: DataSecurityNode on May 22, 2015, 03:05:17 am
There is a delegate for that! :)

http://digitalgaia.io/backbone.html

Support him to have this further developed.

Looks good, will vote.

891
Technical Support / Re: DDoSing the BitShares network
« on: May 22, 2015, 08:44:32 am »
Quote from: xeroc ¯\_(ツ)_/¯ on May 22, 2015, 06:27:43 am
Quote from: DataSecurityNode on May 22, 2015, 03:05:17 am
There is a delegate for that! :)

http://digitalgaia.io/backbone.html

Support him to have this further developed.
This.

also, you can run the delegate with "--incoming-connections 0" .. than the only connections open to the server are those you defined on your own .. e.g. proxy clients to hide the signer machine

I can't quite visualize this, having not dabbled with running a delegate yet. Would you clarify these ?

- I thought the delegate *was* the signing machine?
- What exactly does --incoming-connections 0 (besides the obvious)?
- How would the setup you describe (proxy clients, signer machine) work ?
  - And if incoming-connections=0, how do "proxy clients connect to the server" ?

892
Technical Support / Re: Minimum requirements for delegate nodes and source code portability
« on: May 21, 2015, 10:45:30 pm »
xeroc, I lost this thread in the mean time.

I have looked into chain servers, nice concept but there seem to be some up already and since it needs manual editing of the config file, I suppose >95% users are not using them now.

I'll revisit the idea of running one if their discovery by clients becomes automatic.

893
Technical Support / Re: DDoSing the BitShares network
« on: May 21, 2015, 10:36:32 pm »
Quote from: testz on May 21, 2015, 10:08:52 pm
Quote from: karnal on May 21, 2015, 10:01:25 pm
They will at least have the bitshares port open. And most likely SSH as well.

There are way (, way) more than 101 bitcoin miners. I would guess the specs for a bitcoin miner will tend to be much more buffed too.

Why BitShares port open? They operate as network clients and connect to other nodes only. SSH port, yes, if it's VPS but SSH ports has custom number and usually protected from DDoS by VPS provider.
How you will get delegates IP, if blocks propagated by network and your client usually get it from other clients and not directly from delegate?

Delegates are clients too, I really haven't thouroughly checked what the client is doing at the network level, but:

BitShares 986 $user   54u  IPv4  34849      0t0  TCP xxx:48096->216.146.143.195:1776 (ESTABLISHED)
BitShares 986 $user   66u  IPv4  45237      0t0  TCP xxx:54789->185.82.200.187:1776 (ESTABLISHED)
BitShares 986 $user   82u  IPv4  76344      0t0  TCP xxx:54849->104.131.185.84:1776 (ESTABLISHED)
BitShares 986 $user  139u  IPv4  78859      0t0  TCP xxx:40946->cpc3-cmbg14-2-0-cust343.5-4.cable.virginm.net:1776 (ESTABLISHED)
BitShares 986 $user  143u  IPv4  33992      0t0  TCP xxx:60337->185.82.200.106:40027 (ESTABLISHED)
BitShares 986 $user  144u  IPv4  31742      0t0  TCP xxx:37187->216.146.143.206:1776 (ESTABLISHED)
BitShares 986 $user  145u  IPv4  31743      0t0  TCP xxx:51099->www2.minebitshares.com:1776 (ESTABLISHED)
BitShares 986 $user  146u  IPv4  33643      0t0  TCP xxx:47911->vmi34425.contabo.host:35453 (ESTABLISHED)
BitShares 986 $user  147u  IPv4  34011      0t0  TCP xxx:53679->42.96.186.61:1776 (ESTABLISHED)
BitShares 986 $user  148u  IPv4  34014      0t0  TCP xxx:41496->delegate.dposhub.org:1776 (ESTABLISHED)
BitShares 986 $user  149u  IPv4  35335      0t0  TCP xxx:37978->bitsharesnode:1776 (ESTABLISHED)
BitShares 986 $user  150u  IPv4  34029      0t0  TCP xxx:54079->colo.hostirian.com:42990 (ESTABLISHED)
BitShares 986 $user  151u  IPv4  75755      0t0  TCP xxx:38961->67.4.107.92.dynamic.wline.res.cust.swisscom.ch:1776 (ESTABLISHED)
BitShares 986 $user  152u  IPv4  34031      0t0  TCP xxx:53362->li699-30.members.linode.com:1776 (ESTABLISHED)
BitShares 986 $user  153u  IPv4  34032      0t0  TCP xxx:45142->178.62.30.153:1776 (ESTABLISHED)
BitShares 986 $user  154u  IPv4  34033      0t0  TCP xxx:56829->104.131.134.181:1776 (ESTABLISHED)
BitShares 986 $user  157u  IPv4  34034      0t0  TCP xxx:57893->198.199.106.13:1776 (ESTABLISHED)
BitShares 986 $user  158u  IPv4  34933      0t0  TCP xxx:52255->95.215.47.201:42315 (ESTABLISHED)
BitShares 986 $user  160u  IPv4  36981      0t0  TCP xxx:60288->li424-154.members.linode.com:1776 (ESTABLISHED)
BitShares 986 $user  161u  IPv4  35399      0t0  TCP xxx:58871->li430-37.members.linode.com:1877 (ESTABLISHED)


I'm willing to bet the bold ones are delegates. If so, this means clients also connect to them.

If so, then it is trivial to isolate them. They will be the nodes that are constantly running. Simple network analysis spread over a few days will give you the full list.

894
Technical Support / Re: DDoSing the BitShares network
« on: May 21, 2015, 10:01:25 pm »
They will at least have the bitshares port open. And most likely SSH as well.

There are way (, way) more than 101 bitcoin miners. I would guess the specs for a bitcoin miner will tend to be much more buffed too.

895
Stakeholder Proposals / Re: Argentina Team Updates
« on: May 21, 2015, 09:48:25 pm »
Cool, guys. Are the people extra receptive about crypto in Argentina? Given the track record of the currency in the last decade there..

896
Technical Support / DDoSing the BitShares network
« on: May 21, 2015, 09:42:40 pm »
If my understanding is correct, it would be possible to disable the network by DDoSing the 101 (virtual)machines signing blocks.

101 targets is not that much, and most of our delegates are probably running on virtual machines with little resources to spare against attack.

Heck, even a simple SYN flood will probably knock most delegates offline (out of ethical concerns, I have not put this theory to the test).


Has this angle been covered? Have we as community considered the impact of a DDoS on the delegates? Finding all of their IPs to target seems trivial.

Perhaps present delegates can comment on this? Have you seen such attempts against your machines ? Or perhaps increased frequency of (e.g) SSH bruteforce attempts?

897
General Discussion / Re: Understanding BitAsset Limitations
« on: May 21, 2015, 09:28:04 pm »
Quote from: Ander on May 21, 2015, 09:12:05 pm
Quote from: karnal on May 21, 2015, 09:05:45 pm
More new rules?

Hopefully simpler and better rules, replacing the old rules that didnt work well.

Hopefully. But it does make one wonder. Will the new new rules be replaced by new new new rules as well?


898
General Discussion / Re: Why I think BitShares will succeed. Do competitors have all our features?
« on: May 21, 2015, 09:25:55 pm »
Quote from: bytemaster on May 21, 2015, 07:31:46 pm
This is a great post and hits on so many points.

I would say that success depends on more than just having the best technology, it depends upon having the best community and being easiest to use.

I think we are growing as a community and working on our weak spots.

We are indeed! We're building something important here. Soon the rest of the world needs to know about it!

899
General Discussion / Re: Understanding BitAsset Limitations
« on: May 21, 2015, 09:05:45 pm »
More new rules?

900
General Discussion / Re: BitAsset 2.0 Requirements & Implied Design
« on: May 20, 2015, 09:17:08 pm »
Quote from: mindphlux on May 20, 2015, 01:07:39 pm
they'd leave the BitShares space if that yield would no longer exist. A "bond market" where one can earn interest is not the same, it is too complicated for someone without a financial background to grasp, all the passive investors care about is a simple yield on bitUSD.

Fully agree. BitAssets providing interest is one of the most appealing features.

Also I'm with the others who say - KISS. All these rule changes, mad complex rules.. I would be surprised if someone who is not a core dev could properly explain in a simple way all the little rules and their interactions.

Pages: 1 ... 53 54 55 56 57 58 59 [60] 61 62 63 64 65 66 67 ... 72

Page created in 0.174 seconds with 20 queries.