Wonder if you can zip up the source code for just pdcurses.dll and send them in together.
Their GUI only seems to allow for detected files to be submitted. It doesn't detect the original ZIP file that I downloaded as containing anything malicious.
I have sent it in already... though in my experience they usually don't do much without contact from someone involved in the production or compilation of the software. :/
Quote
AVG Research Lab has analyzed the file(s) you have sent from your AVG Virus Vault. Below you can find the results for each file. The final verdict on the file is either a correct detection or a false positive detection.
After extracting the Windows binaries, AVG detects "PSW.KeyLogger.AVU" in pdcurses.dll. Since the functionality of pdcurses is to read keystrokes, this doesn't surprise me terribly, but it is a bit disconcerting. Can this be resolved somehow?
Report it to your AVG as a false positive?
I have sent it in already... though in my experience they usually don't do much without contact from someone involved in the production or compilation of the software. :/
After extracting the Windows binaries, AVG detects "PSW.KeyLogger.AVU" in pdcurses.dll. Since the functionality of pdcurses is to read keystrokes, this doesn't surprise me terribly, but it is a bit disconcerting. Can this be resolved somehow?
Post
Topic
BoardGoods
Re: Selling TF2 items for BTC
by
cdhowie
on 16/07/2012, 14:26:26 UTC
Bump.
Post
Topic
BoardGoods
Re: ► Buying ALL Team Fortress 2 TF2 Items ◄► Bitcoin, Liberty Reserve, Mt. Gox ◄
I am selling TF2 items in exchange for BTC anchored in USD, dictated by the following conversion rates:
2.66 refined metal = 1 key
1 key = 2 USD
USD value converted to BTC by current Mt. Gox bid.
This comes down to: 1 ref is $0.75 and 1 scrap metal is $0.0833. I sell most items as 1 scrap each ("retail" price) but may be willing to do a bulk discount. If you want, have a look at my inventory. I don't list keys on that page; right now I have 4.
Post
Topic
BoardGoods
Re: ► Buying ALL Team Fortress 2 TF2 Items ◄► Bitcoin, Liberty Reserve, Mt. Gox ◄
by
cdhowie
on 03/07/2012, 15:20:22 UTC
Are you buying keys? I will sell them for 2 USD equivalency in BTC.
I also have a pretty large stock of items. I treat keys as 2.66 refined, so... 1 ref = $0.75, 1 scrap = $0.0833. I sell most items as 1 scrap each ("retail" price) but may be willing to do a bulk discount. If you want, have a look at my inventory.
Post
Topic
BoardGoods
Re: ► Buying ALL Team Fortress 2 TF2 Items ◄ ✔ ► Bitcoin, Liberty Reserve, Mt. Gox ◄
After watching tshark, poclbm.py output, and tailing the access log for the proxy, I have determined that a low KeepAliveTimeout setting in the Apache config was the culprit.
The KeepAliveTimeout on my server was 3 seconds, and the ask rate was 5. This caused the miner to try to use a KeepAlive session, only to find it timed out. Then it had to establish a new connection. This was giving the connection issues I was seeing.
Essentially what this means is the KeepAliveTimeout setting has to be higher than the ask rate. I would suggest adding a few seconds on top to make sure there's a little wiggle room.
Thanks for the info! I'll add this to the readme, and perhaps to the .htaccess file.
I been doing some research into the Long Polling issue, wouldn't be possible to just let the miner connect to the LP address directly instead of going through the proxy?
No. The LP request will return work, and if the work doesn't pass through the proxy then it can't be recorded in the database. And if it can't be recorded in the database, then work submissions against that work cannot be routed to their source pool, and the work the miner has done will have been for nothing.
Further, the LP specification implies that the X-Long-Polling header must return a host-relative URI. (Though some pools do not follow this.)
Is there any way to login with worker credentials inside the web page using a Web Browser? It's all http protocol and I shuold get some JSON response if I understand.
Well, you need to send a POST request with the appropriate JSON-RPC method call to get a JSON response. But you can still point your browser at the proxy (just remove "/admin/..." from the URL) and authenticate as a worker. If you successfully authenticate, you'll get back a 400 Bad Request ("I don't understand what you said") response.
Thanks for the proxy. Seems to work pretty well so far.
I did have to make one change to fix a problem with the proxy out of the box. Whenever I submitted a form, I'd be redirected to some other web site (localhost) which has no server running. It appears you're reading SERVER_NAME, which may or may not be correct. It's more reliable to read HTTP_HOST:
Hey, you still haven't included this fix, as far as I can tell. I just pulled master and it isn't there.
Sorry, I must have missed or forgotten about the original bug report. The Github issue tracker is where I track bug reports and patches, so if it's not there then there's a good chance I won't remember it.
Can you maybe try to tell me what the problem is or what other info i need to figure the problem out?
Response 401 is "unauthorized." Your command does not appear to include any authentication information. You need to add the username and password of one of the proxy's worker accounts.
If on a LAMP server, Java probably won't be installed by default. If on a desktop, Java still probably won't be installed by default (unless it's GNU classpath) and in some cases Mono will be installed too, for Banshee/Tomboy/F-Spot.
Honestly, I'd rather focus my energy on adding support for PostgreSQL, which I should have done in the first place...