Author Topic: Possible log in to this forum with BTS id?  (Read 5878 times)

0 Members and 1 Guest are viewing this topic.

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
Actually the reason I didn't find that is because you linked me to C code.  My code is the standard php curl lib that you get when you install php5-curl or whatever it is.

It uses easybitcoin which is a real simple php lib that uses __call or whatever it is to overload the class into rpc calls.  You can google and find it.  If I remember I'll grep through file system for that port #, but.. its just a random port.
« Last Edit: January 24, 2015, 02:01:38 am by gamey »
I speak for myself and only myself.

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
I do have one problem where apache is binding to localhost at the same port and preventing the wallet from connecting.  So it took me shutting down apache and waiting and then starting them up in order.  I have no clue why using a curl-php5  would do this.  I guess I don't understand tcpip ?  Regardless it isn't really acceptable because if the wallet dies, a wallet restart won't work because it fails to bind to that port.  I've read all the curl lib options etc and nothing makes sense except that I don't understand tcpip as well as I thought.  I doubt it'd be a problem if everything wasn't using localhost.
I'm not sure if it's a curl-php5 problem.. Maybe set different ports for apache and the wallet will work.
Could you post your apache config files here?
And the command line you starting your wallet, and the config.json of your wallet?
And the code how you're using curl-php?
Reminder: don't set CURLOPT_LOCALPORT or set it to a different value in curl-php.

There are no ports for apache.  Just database settings that are fed into curl.  I'm not going to go through basic IT support but I will look at that setting.
...
Ahh wow.  I went through full list of curl options looking for that because my theory is that the local port is defaulting to the destination port which would match up the 4tuple if ports/ips. So I looked through settings and for whatever reason didn't see it.  I made a list of possible curl options to inspect but I missed the one I needed.  I suspect the above option will fix it as it was what I was looking for to begin with, so thank you for your input !
I speak for myself and only myself.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
I do have one problem where apache is binding to localhost at the same port and preventing the wallet from connecting.  So it took me shutting down apache and waiting and then starting them up in order.  I have no clue why using a curl-php5  would do this.  I guess I don't understand tcpip ?  Regardless it isn't really acceptable because if the wallet dies, a wallet restart won't work because it fails to bind to that port.  I've read all the curl lib options etc and nothing makes sense except that I don't understand tcpip as well as I thought.  I doubt it'd be a problem if everything wasn't using localhost.
I'm not sure if it's a curl-php5 problem.. Maybe set different ports for apache and the wallet will work.
Could you post your apache config files here?
And the command line you starting your wallet, and the config.json of your wallet?
And the code how you're using curl-php?
Reminder: don't set CURLOPT_LOCALPORT or set it to a different value in curl-php.
BitShares committee member: abit
BitShares witness: in.abit

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
I've done most of the research for last few issues so I'll be finishing it up in the next few days (end of weekend). (It already is finished).. but..then last round of testing when it is code complete.

It was updated/tested for the latest wallet.

I do have one problem where apache is binding to localhost at the same port and preventing the wallet from connecting.  So it took me shutting down apache and waiting and then starting them up in order.  I have no clue why using a curl-php5  would do this.  I guess I don't understand tcpip ?  Regardless it isn't really acceptable because if the wallet dies, a wallet restart won't work because it fails to bind to that port.  I've read all the curl lib options etc and nothing makes sense except that I don't understand tcpip as well as I thought.  I doubt it'd be a problem if everything wasn't using localhost.

what's the number of the port ?

57133.
I speak for myself and only myself.

Offline btswildpig

  • Hero Member
  • *****
  • Posts: 1424
    • View Profile
I've done most of the research for last few issues so I'll be finishing it up in the next few days (end of weekend). (It already is finished).. but..then last round of testing when it is code complete.

It was updated/tested for the latest wallet.

I do have one problem where apache is binding to localhost at the same port and preventing the wallet from connecting.  So it took me shutting down apache and waiting and then starting them up in order.  I have no clue why using a curl-php5  would do this.  I guess I don't understand tcpip ?  Regardless it isn't really acceptable because if the wallet dies, a wallet restart won't work because it fails to bind to that port.  I've read all the curl lib options etc and nothing makes sense except that I don't understand tcpip as well as I thought.  I doubt it'd be a problem if everything wasn't using localhost.

what's the number of the port ?
这个是私人账号,表达的一切言论均不代表任何团队和任何人。This is my personal account , anything I said with this account will be my opinion alone and has nothing to do with any group.

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
I've done most of the research for last few issues so I'll be finishing it up in the next few days (end of weekend). (It already is finished).. but..then last round of testing when it is code complete.

It was updated/tested for the latest wallet.

I do have one problem where apache is binding to localhost at the same port and preventing the wallet from connecting.  So it took me shutting down apache and waiting and then starting them up in order.  I have no clue why using a curl-php5  would do this.  I guess I don't understand tcpip ?  Regardless it isn't really acceptable because if the wallet dies, a wallet restart won't work because it fails to bind to that port.  I've read all the curl lib options etc and nothing makes sense except that I don't understand tcpip as well as I thought.  I doubt it'd be a problem if everything wasn't using localhost. 
I speak for myself and only myself.

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
It is pretty much done but the plugin included a work-around for a bug that was in the wallet.  I am waiting for a new release of the wallet.  (or I could test the site off devshares I suppose.. ).  I wanted to remove that work-around in the plugin and have it as polished as possible.  I'll be messing with it over the next few days too as I want to wrap that project up but I'm waiting on a fixed wallet.  I also posted on the simplemachines forum for advice a couple days ago ..

So it is more or less completed, but it is a security plugin that does authentication so I've been quite slow and deliberate.  It sounds cool and all to throw it up but then if it was to start messing with people's SMF experience then that would not be good.  Also security breaches of the authentication type can't be rewound like a blockchain fix.  IMO always delete sensitive messages on the forum.
@gamey any update? New wallet has been released.  :)
Thanks.
BitShares committee member: abit
BitShares witness: in.abit

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
It is pretty much done but the plugin included a work-around for a bug that was in the wallet.  I am waiting for a new release of the wallet.  (or I could test the site off devshares I suppose.. ).  I wanted to remove that work-around in the plugin and have it as polished as possible.  I'll be messing with it over the next few days too as I want to wrap that project up but I'm waiting on a fixed wallet.  I also posted on the simplemachines forum for advice a couple days ago ..

So it is more or less completed, but it is a security plugin that does authentication so I've been quite slow and deliberate.  It sounds cool and all to throw it up but then if it was to start messing with people's SMF experience then that would not be good.  Also security breaches of the authentication type can't be rewound like a blockchain fix.  IMO always delete sensitive messages on the forum.
« Last Edit: January 14, 2015, 04:18:58 pm by gamey »
I speak for myself and only myself.

Offline islandking

  • Sr. Member
  • ****
  • Posts: 378
  • The king of the island
    • View Profile
You could always ask bitsapphire if they can add it to the forum. Gamey already has a plugin.
I've been working on a new electronic cash system that's fully peer-to-peer, with no trusted third party. - Satoshi

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Gamey has a working plugin running at bitnation.org or so ...


//edit: url: http://bitsharesnation.org/
« Last Edit: January 14, 2015, 02:52:11 pm by xeroc »

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Just an idea, don't know whether others asked yet.
BitShares committee member: abit
BitShares witness: in.abit