stellar-slack1 has quit [Remote host closed the connection]
stellar-slack has joined #stellar-dev
<stellar-slack> <dzham> It looks easy enough to “add TLS support”, but then you need to be able to configure it also… cipher suite, protocols, caching, stapling
bittrex-richie has quit [Ping timeout: 246 seconds]
bittrex-richie has joined #stellar-dev
bittrex-richie is now known as Guest97201
koolhead17 has joined #stellar-dev
de_henne has joined #stellar-dev
de_henne_ has quit [Ping timeout: 260 seconds]
koolhead17 has quit [Remote host closed the connection]
<stellar-slack> <sacarlson> I got the proxy working on apache without to much trouble should be up now at https://api.equid.co/federation
TheSeven has quit [Ping timeout: 250 seconds]
TheSeven has joined #stellar-dev
bit2017 has quit [Ping timeout: 272 seconds]
de_henne has quit [Remote host closed the connection]
de_henne has joined #stellar-dev
bit2017 has joined #stellar-dev
nivah has joined #stellar-dev
nivah has quit [Read error: Connection reset by peer]
bit2017 has quit [Ping timeout: 255 seconds]
<stellar-slack> <sacarlson> I think I've found a bug in https://github.com/stellar/federation that doesn't permit changing username to user_login in db search
<stellar-slack> <sacarlson> federation = "SELECT user_login, account_id FROM wp_users WHERE user_login = ?" won't work
<stellar-slack> <sacarlson> federation = "SELECT username, account_id FROM wp_users WHERE username = ?" but this does even if the colum user_login exists
<stellar-slack> <sacarlson> created issue https://github.com/stellar/federation/issues/4
DomKM has quit [Quit: Connection closed for inactivity]
<stellar-slack> <sacarlson> @bartek so your saying that the colum names in the federation lookup are hardcoded? strange you can change the table name but not the colum names
<stellar-slack> <bartek> you can change the order of the fields in the result set. it's better to name the fields rather than depend on the order.
<stellar-slack> <sacarlson> I had planed to just point them to values that wordpress already used. but that's ok I'll do the work around then
<stellar-slack> <sacarlson> also did you fix the bug it has in not puting out the header value for cors Access-Control-Allow-Origin: *
<stellar-slack> <sacarlson> I already fixed that in my version
<stellar-slack> <bartek> yeap, it will be included in 0.0.3 that I will release today
<stellar-slack> <sacarlson> very good. I might make a branch that allows changing the colum values at some point
Guest97201 is now known as bittrex-richie
<stellar-slack> <sacarlson> and thanks for your feedback @bartek
<stellar-slack> <bartek> @sacarlson: federation 0.0.3 released: https://github.com/stellar/federation/releases/tag/0.0.3
<stellar-slack> <sacarlson> thanks @bartek
<stellar-slack> <bartek> damn, the tool we use for building `gb` has changed recently and this build is broken. fixing.
<stellar-slack> <sacarlson> ha ha ok
<stellar-slack> <bartek> ok, fixed
<stellar-slack> <sacarlson> and if anyone has a wallet with the new standard stellar federation I would like you to try lookup of both sacarlson*http://equid.co|equid.co and zipperhead*http://equid.co|equid.co they should work to the standard forward and reverse
<stellar-slack> <sacarlson> my present prototype wallet does do federation lookup of sacarlson*http://equid.co|equid.co , but presently doesn't follow the stellar standard on stellar.toml yet http://sacarlson.github.io/transaction_tools.html. it also defaults to http://equid.co|equid.co if no @ or * is seen in the address
<stellar-slack> <jed> sacarlson: you don't need a work around. You just need to change your SQL command in the config
<stellar-slack> <jed> use `SELECT blah as name` <- note the *as name* part
<stellar-slack> <jed> I know
<stellar-slack> <jed> did seem like he understood judging from the chat here though.
<stellar-slack> <sacarlson> so do I take it we do have a but then as that's what I thought I did try that failed
<stellar-slack> <sacarlson> I provided the example sql database file to duplicate
<stellar-slack> <sacarlson> I'm personally looking at the code and fail to see why it doesn't work
<stellar-slack> <sacarlson> but when I'm fresh tomaro I'll take another look
<stellar-slack> <bartek> does this configuration work for you (take from your issue and fixed): ``` [queries] federation = "SELECT account_id as id FROM wp_users WHERE user_login = ?" reverse-federation = "SELECT user_login as name FROM wp_users WHERE account_id = ?" ``` does it return any errors?
<stellar-slack> <sacarlson> yes
<stellar-slack> <sacarlson> as noted
<stellar-slack> <bartek> what errors?
<stellar-slack> <sacarlson> I get error: Server error: missing destination name user_login
<stellar-slack> <bartek> did you restart the server after changing config.toml file?
<stellar-slack> <sacarlson> yes
<stellar-slack> <sacarlson> the database as you can see in the example proved also has info at that colum location
<stellar-slack> <bartek> can you run `cat config.toml` before starting federation server and copy console output here?
<stellar-slack> <sacarlson> sure I can probly do that
<stellar-slack> <bartek> (don't forget to obscure your passwords from that file)
<stellar-slack> <sacarlson> good to tell me that as it's late here now and I'm not to clear
<stellar-slack> <sacarlson> so I will put it in the broken state as it is working now in the know working state with the colum names as it wants them
<stellar-slack> <sacarlson> or so you want to verify it now works first?
<stellar-slack> <bartek> I just want to make sure it loads the correct config file
<stellar-slack> <sacarlson> ok so broken to start it is
<stellar-slack> <bartek> it doesn't start?
<stellar-slack> <sacarlson> it works perfect at now now it does start in the broken state also just error when fed data with expected results
<stellar-slack> <bartek> what do you mean by the broken state?
<stellar-slack> <sacarlson> broken state being that error above returns instead of the expected results of a reverse or forward federation
<stellar-slack> <bartek> ok, can you `cat config.toml`?
<stellar-slack> <sacarlson> give me a movent to put it in broken state
<stellar-slack> <sacarlson> yes I can cat both broken and none broken
<stellar-slack> <jed> you didn't put the `as name` part
<stellar-slack> <jed> you can change what the columns are returned as as part of the SQL statement
<stellar-slack> <bartek> looking at your SQL schema (the one you added to the github issue), your queries section has to be like this: ``` [queries] federation = "SELECT account_id as id FROM wp_users WHERE user_login = ?" reverse-federation = "SELECT user_login as name FROM wp_users WHERE account_id = ?" ```
<stellar-slack> <bartek> change it, restart the server and it should work
<stellar-slack> <sacarlson> the example of sql I'm using is in the report
<stellar-slack> <sacarlson> oh cool I'll try your above queries see if they work
<stellar-slack> <sacarlson> nope looks like same results
<stellar-slack> <jed> you sure you change the config and restarted?
<stellar-slack> <sacarlson> yes I can demonstrate again
<stellar-slack> <bartek> some questions: - why are you `killall federation`? how do you send this server to the background? - can you execute this commands in this order and send us your console output? ``` cat config.toml ./federation ```
<stellar-slack> <sacarlson> ok
<stellar-slack> <sacarlson> if you want to remote in and see I'll provide you ssh login
<stellar-slack> <bartek> ok, it's a progress. now you have `missing destination name name`. my guess is you are using 0.0.1, switch to 0.0.3
<stellar-slack> <bartek> we changed field names in 0.0.2
<stellar-slack> <sacarlson> oh ok I should have tried that but I was afraid I would brake the other fix I added
<stellar-slack> <sacarlson> I'll give 0.0.3 a try
<stellar-slack> <bartek> btw. you don't have to compile it, you can download it from: https://github.com/stellar/federation/releases
<stellar-slack> <sacarlson> ok cool will do
<stellar-slack> <sacarlson> I should have added the commit code I was working from sorry
<stellar-slack> <sacarlson> holly crap it works now with 0.0.3
<stellar-slack> <sacarlson> I'll move it to point at wordpres
<stellar-slack> <sacarlson> yup works now when I point it at wordpress database also thanks @bartek and the rest of you all
<stellar-slack> <bartek> cool
<stellar-slack> <sacarlson> but I guess I have the only wallet that can do federation?
<stellar-slack> <sacarlson> I would like to hear that some other wallet can test federation for sacarlson*http://equid.co|equid.co that should now be active
<stellar-slack> <bartek> ``` {"stellar_address":"sacarlson*http://equid.co|equid.co","account_id":"GAMB56CPYXJZUM2QSWXTUFSFIWMNHB6GZBUFJ2YJQJRGW6WH223NRLND"} ``` works for me ;)
<stellar-slack> <sacarlson> cool thanks again @bartek
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Read error: Connection reset by peer]
koolhead17 has joined #stellar-dev
koolhead17 has quit [Remote host closed the connection]
koolhead17 has joined #stellar-dev
ggherdov` has quit [K-Lined]
termos has quit [K-Lined]
olinkl has quit [K-Lined]
sdehaan has quit [K-Lined]
etrepum has quit [K-Lined]
jbenet has quit [K-Lined]
termos has joined #stellar-dev
etrepum has joined #stellar-dev
jbenet has joined #stellar-dev
sdehaan has joined #stellar-dev
olinkl has joined #stellar-dev
ggherdov` has joined #stellar-dev
TheSeven has quit [Remote host closed the connection]
koolhead17 has quit [Remote host closed the connection]
<stellar-slack> <jed> bartek ^
<stellar-slack> <jed> https://api.equid.co/federation?type=name&q=sacarlson*equid.co works
<stellar-slack> <jed> powderfan you are on the latest js-sdk ?
<stellar-slack> <powderfan> yes 0.3.4
<stellar-slack> <powderfan> same result with 1EGeCvza3PuBo5hSGiG8fqidGY4iAMVYre*http://naobtc.com|naobtc.com. works if I type the url, but FederationServer.resolve returns an error
<stellar-slack> <bartek> for http://naobtc.com|naobtc.com there is a problem with SSL certificate for www subdomain: https://www.naobtc.com/ I'm checking what's wrong with http://equid.co|equid.co
<stellar-slack> <powderfan> maybe use http and without www? At least this one works in the browser `http://naobtc.com/.well-known/stellar.toml`
<stellar-slack> <bartek> it would be insecure. someone in the middle could change the FEDERATION_SERVER value and for example: change destination of a payment
<stellar-slack> <powderfan> yeah true
<stellar-slack> <bartek> for http://equid.co|equid.co the problem is also with a certificate: https://www.sslshopper.com/ssl-checker.html#hostname=equid.co it doesn't have intermediate certificates. it can be fixed by a domain operator by merging intermediate certificates from certificates provider
<stellar-slack> <bartek> for example: https://api.equid.co/federation doesn't work in Firefox
<stellar-slack> <powderfan> Ok, thx @bartek! Any working example I can use to test my code? Preferredly returning a memo as well.