You have a search ability, I'm not wasting my time. That is the specific reason I was questioning what the vetting process of the new RPC and why I have been stating there is no reason for a fucking WRAPPER!!!! Losing the rpc on local wallets would have removed that vulnerability dammit. Why do you think I have been arguing to release a wallet with direct access and no middleware?
What does "direct access" mean? If you mean libwallet_api, well that's precisely what Ilya has been building out, so that conversation is pointless. As to "new RPC" there is no new RPC. There is a new IPC, which would have made this problem irrelevant, but tewinget simply didn't finish enough of it in time for the 0.10.0 release. Local wallets are not at risk, unless you choose to allow remote access, which may lead to remote access (basically what that disclosure highlights). |
|
|
|
|
I've read through the constitution, and whilst some of it goes over my head (I'm just a pony, after all) I'm broadly in agreement of it, and I think that it will provide a good framework for the game to move forward. Thank you for your work and effort on it, Risto!
|
|
|
|
You dont get the point even when its so obvious. We discuss about the price development here and this is also connected to an easy, working and official GUI. So its NOT about the GUI, it IS about the price related with the GUI. When you say Tesla needs a better battery technologie to have a better coverage which makes them selling more cars and raising their shares it is you who says "then develope new battery". You got it  ? Please explain how people buying Monero on Poloniex enriches me, or hyc, or any of the other developers? I'm certainly not selling my small stash of Monero, neither is anybody else. It's absurd that you think this is like a company - buying Monero on Poloniex only enriches two people: yourself and Poloniex. To everyone that has worked on the project your purchase is entirely inconsequential, and it is downright insulting that you compare a rise in Tesla's share price to this situation. You have no idea how open-source development works. |
|
|
|
It's hard not to be disconcerted about the lack of a GUI after more than two years. I know it's coming "soonish", as it has been for 1+ years. However, at this point it's certainly holding back adoption at a time when adoption is poised to explode.
Where do you get 1+ years from? We'd never have said it's "coming soon" until Ilya started working on it, and at ~10 hours a week for 28 weeks nobody was going to suggest that Ilya would have anything remotely workable earlier this year. People have a horrible habit of misreading, or inferring their own hopes, and then you end up with skewed expectations. |
|
|
|
You still don't get the point...maybe you dont understand or you dont want. NVM. Still the fact that a GUI by the core dev. is still missing. They only provide a simplewallet without a gui. You can ignore it, doesnt matter, as long as i know the facts for myself  What do you mean "the core dev"? Which of the 127 developers is "the core dev"? https://www.openhub.net/p/monero/contributorsAlso, the lightWallet2 developer *is* a Monero developer, here's his most recent pull request: https://github.com/monero-project/monero/pull/1053 |
|
|
|
I mean i could do this with java in 2 days. I dont unterstand whats their problem here...they have had now 2 years.
Great stuff, looking forward to seeing your work:) First release on Wednesday evening, shall we say? Java is not setup per default in every OS. So it should be written in c++ -what still doesnt need 2 years. i2p's router uses Java, seems to be just fine. Also I'll make your life easier, here's a Monero GUI already written in Java: https://github.com/jwinterm/LightWallet2So just take that and add to it - looking forward to your release of the massively improved version on Wednesday evening! |
|
|
|
I mean i could do this with java in 2 days. I dont unterstand whats their problem here...they have had now 2 years.
Great stuff, looking forward to seeing your work:) First release on Wednesday evening, shall we say? |
|
|
|
My bank had me choose one image (out of several dozen) and thereafter displays that image on the login screen, giving me confidence that it is really my bank's website I'm logging into. Would something like that work with MyMonero? Also, of course, two-factor authentication would be fantastic. I think Trezor now can be used as a login token.
Anything we add can be incorporated on an impersonator site, especially something trivial like that. 2FA is good and well, but either it needs to be a token that is used to encrypt the spend key (ie. you lose access to your 2FA device there's no recovery), or I have to be custodial (ie. store the spend key so you can recover it). Given MyMonero's use-case neither of those options are desirable to me. A form of 2FA is on the cards for development, but we have other urgent priorities like RingCT compatibility, so it's hard to balance everything. |
|
|
|
Every time I looked at mymonero I kept saying I've seen this image before but from where? https://mymonero.com/#/ Not the fake scam site. http://www.stargazercastiron.com/ Great cast iron skillet if you are into cooking with one by the way. I had ordered one of these several months ago and kept getting that "why does this look familiar" feeling when I would log into mymonero. Finally this morning the synaptic pathways linked up and I knew why. Scammers are smart and will do anything to get over on someone or steal, but they can all rot in hell as far as I'm concerned. lol I had no idea, it was just a stock image that looked cool:) Sorry to hear the bad news birr. It sucks man, I've been a victim of thief's before I can empathize. For what it might be worth I will say a little prayer for you. What goes around comes around and these assh*^$ will get what is coming to them.
Agreed - it's seriously upsetting and damaging both for the victim, and for me as the site operator. I can only hope that other people take heed and move their funds into cold storage, the web wallet is just for convenience / playing around / smaller amounts. Maybe Fluffypony could put a warning up on the home page to check the URL before logging in.
Did that the minute I found out about the fake site: It unfortunately doesn't help if people visit the .co first:/ |
|
|
|
Much of this research is done by the Monero Classic Research Lab. Congrats on forming your own research lab! Please note, though, that you will need to correctly attribute publications from the Monero Research Lab to them, you cannot reattribute them to yourself. Edit: just to be clear, this post was facetious, meant to highlight the copy-paste content. I do not endorse cryptocurrency crowdsales, as they end up as scams 99.9% of the time. In addition, part of the reason that Monero has become at all successful is because we had no crowdsale, no premine, no instamine. We've spent 2.5 years slowly working on it, without pay. |
|
|
|
fluffypony's StackExchange thread of the week (or whatever period since I last did this, which is never, first time doing this) - What are some ways I can disguise my mnemonic seed?fluffypony sez: "always disguise your mnemonic seed, kids, and don't trust new-fangled cryptography primitives that aren't peer reviewed for like 10+ years" |
|
|
|
More like the substance of the post, along with the post itself bringing it all to light. Nice job RYS
Yeah this part of his turned out to be pretty spot-on: Nobody working behind these cryptocurrencies is known in the cryptocurrency community, and that alone should be a big fucking red flag. Monero is streets ahead, partly because of the way they're developing the currency, but mostly because the "core devs" or whatever they're called are made up of reasonably well-known people. That there are a bunch of them (6 or 7?) plus a bunch of other people contributing code means that they're sanity checking each other.
|
|
|
|
I installed a antivirus sophos last night, scanned hours, No malware Found,
I know this does not mean my PC is not compromised,
I wonder, is there anyone deposited big amount XMR on mymonero, and the fund still safe ?
Antivirus wouldn't detect rootkits or any sort of APT, and you can bet that any malware already on the computer would hide from an antivirus scanner. In addition, if the keys were compromised months or years ago it's entirely possible the malware no longer exists on that computer. I have several MyMonero honeypot accounts that have (fake) balances of varying size in them, and I play fast and loose with the logins in order to catch any compromises. |
|
|
|
Our aim is to replace lots of components (eg. the web server used for JSON RPC API access) with standard, well-known, secure libraries.
Why?
Because epee is *not* known-good, *not* well-reviewed, *not* used anywhere except Monero. It is much higher risk to keep epee around, or to roll our own stuff, than to replace it with stuff that is widely reviewed.
Rolling your own can be better if you are talking about complexity getting dragged in with the standard component. If you need something simple, it is often possible to achieve exceptional levels of confidence in the correctness if the component when you control it. You can use declarative systems which are provable, and compile into c++, for example. The upstream being uncontrolled adds a maintenance issue, but it is a much lower-order factor. What is the preferred venue for such threads? We're talking about components that require some complexity and extensibility. We're currently so heavily reliant on the Boost libraries that we literally can't get more complex by using other components. We're also not talking about components used by one project - issues in something like Boost or 0MQ or netcpplib would affect thousands and tens-of-thousands of projects, and so they handle their efforts with care. We take similar precautions by statically compiling these in, and not updating to potentially broken versions until they're reasonable to consider safe. There's no fixed venue, if you have a concern about a choice that the dev community has made then open a GitHub issue. That said, the contributors (ie. those that have actually submitted pull requests) are generally in the best position to know the code, so if you want your opinion to matter and not be discarded then you need to start pushing code;) Attending the dev meetings every second week would also go a long way towards that. Opinions on design decisions from non-contributors are not discarded, but they typically won't be considered as strongly precisely to prevent interference by the sort of third-parties you'd be worried about. It's much easier for someone to make a lot of noise about a decision than to push code, which leads to loud-voices-from-non-contributors simply not being enough to affect design and architectural decisions. |
|
|
|
The bottom of this web page says it's funded by the "NWO"  DUN DUN DUN DUN:) |
|
|
|
bad Tor exit nodes
 How could a bad tor exit node learn your private key? mymonero.com is https encrypted. No DANE support in browsers, and no wide DNSSEC support, means that downgrade attacks are trivial. Even then, you should only ever use Tor exit nodes if you happen to have the TLS fingerprints saved somewhere to verify your connection. MyMonero has HSTS on, but even if we were in the HSTS preload list it's a half-baked solution and is just a band aid till the next POODLE comes along. |
|
|
|
Perhaps implementing 2 factor would mitigate some of this. Is the code on github?
Not entirely feasible - everything is client-side, MyMonero never knows your spend key. Ostensibly the spend key could be encrypted with some 2FA, but I'd be very wary about the ability to recover the actual key in the event of a 2FA failure or lost device or some such. It also doesn't solve the problem of an MITM attack. |
|
|
|
And I thought that this was replacing remote communication as well. Which is a VERY BIG DEAL. But after listening to the Podcast you linked I see that it is intended for interprocess communication currently but Fluffy did say it can be extended for wiring protocol replacement.
In terms of "dev notes", a lot of this stuff goes down on IRC in #monero-dev and sometimes even #monero. The bi-weekly dev meetings are the culmination of these discussions that span thousands of lines of text over many days. Could you post those logs on pastebin? 0MQ is a trivial decision to make, because it's a backend change as you've observed. Our only option is either a messaging system (of which 0MQ is unequivocally the most battle-tested, with the largest number of implementations) or replacing the current HTTP server with something far more performant. Obviously, short of forking nginx, the latter is not really an option. I don't quite understand why there needs to be any wrapper at all for local communication, why not use direct input and add the daemon functionality to say the gui? Is there any reason these need to be separate for end users? I just see this as a injection point where one doesn't need to be. To speak to your other concern: we are definitely looking at replacing the wire protocol. Since we'll have 0MQ in already, and since we want to enable developers to build consensus-compatible implementations in whatever language they'd like, the logical choice is ZMTP ( http://zmtp.org). This is, again, something that is battle-hardened and has implementations in tons of languages. Our other option is picking one of the Tor pluggable transports, something like obfs4, but that's somewhat less desirable for cross-implementation purposes. I do remember this discussion being touched on in this thread I think but I don't remember a decision being announced. Making the product more accessible to a larger is base is laudable as I said I just want to make sure it is not at the cost of security. Especially with the vultures hovering looking for any attack vector they can find. The current home-grown Boost::ASIO wire protocol is significantly more risky than switching to something that is standard. It's entirely possible that there's some weirdness under the hood that we haven't uncovered yet, so swapping it out for something that is well-known and widely used in FOSS projects is extremely desirable. Complexity is the enemy of good security, and in this case custom protocols way worse than well-known standards.
Perhaps more importantly, though, the wire protocol is hardly an attack surface. The major risk it represents is an MITM attack revealing what transactions you were the first to broadcast (mitigated by end-to-end encryption in ZMTP), and fingerprinting attacks being able to correlate your clearnet IP with your i2p address (mitigated by introducing some execution randomness to the i2p connectivity, and completely separating the information shared with nodes on both interfaces). Beyond that, a compromised or poisoned wire protocol won't be able to "do" anything particularly bad. The daemon has no idea what your private keys are. It has some information about your transactions you send out, and the ones you're interested in, but if it were revealing that it would be spotted very quickly.
This is actually my top concern, I want to see how this has been vetted. Call me paranoid but changing a core protocol with off hand remarks is worrisome and I just want to verify that we are not just taking anyone's word on the fact that the crypto in 0MQ is sound and safe when it comes to a currency that cannot be checked for manipulation. http://arstechnica.com/security/2014/01/how-the-nsa-may-have-put-a-backdoor-in-rsas-cryptography-a-technical-primer/BTW we are very close to losing beta status correct? How long will this be tested within the beta phase? I don't know anything about this so I wanted to see a peer review or a word from our scientists that they have verified this is bulletproof. Looking into ZeroMq I see it uses Curve25519 correct? http://zeromq.org/topics:encryptionZeroMQ 4.x has extensible encryption, and comes with CurveZMQ as a built-in security mechanism. Pieter Hintjens has some articles that explain how this works. The only extra dependency is libsodium, which provides the Curve25519 security functions. https://www.reddit.com/r/programming/comments/1ms5fu/new_zeromq_4_does_strong_encryption_and_perfect/https://en.wikipedia.org/wiki/Curve25519
I no longer trust the constants. I believe the NSA has manipulated them through their relationships with industry
— Bruce Schneier, The NSA Is Breaking Most Encryption on the Internet (2013)
*********************************************************************************************************** Will Monero pitch to Anchor into Factom blockchain after they do Ethereum?
Ethereum is for smart contracts Factom is for data and Dash or Monero is for privacy.
Actually I don't know who's better between Dash or Monero and I know there is heated debate about this so not opening that pandoras box because I don't have a horse in the race. Anyway both are experimental technologies in field worthy of pursuit.
Well just looking at XMR's rich list should tell you something. http://moneroblocks.info/richlistIt could be worse, but there's a hint of smugness to the writing on that page. As there should be, this project is headed by some of the smartest and capable people I've ever seen, they are so advanced they take for granted that we as a community know the things I ask in this thread. I feel like the kid in class that asked the question because others are lost and afraid to. Not to say I don't get lost, my brain is on life support these days. Lol This project gets the hardest scrutiny and has never to my knowledge lied, misled or deceived the community, how many other ones can you say that about? Sorry I never got to answering this - extreme lack of time atm. Bottom line: 0MQ, and in future ZMTP, are extremely well-known, well-used, and well-reviewed software libraries. Our aim is to replace lots of components (eg. the web server used for JSON RPC API access) with standard, well-known, secure libraries. Why? Because epee is *not* known-good, *not* well-reviewed, *not* used anywhere except Monero. It is much higher risk to keep epee around, or to roll our own stuff, than to replace it with stuff that is widely reviewed. PS. Curve25519 / Ed25519 is an integral part of Monero's cryptography. If it's broken we are in a much bigger toilet bowl than just 0MQ. Thankfully, Curve25519 is likely the most secure curve we have today, as Peter Gutmann begrudgingly affirmed recently: http://www.metzdowd.com/pipermail/cryptography/2016-March/028824.htmlEdit: btw, the Bruce Schneier quote you include is him explaining why the NIST's P curve constants were purposely broken by the NSA, which is what has led to such an uptake in Curve25519 use. See SafeCurves for details: https://safecurves.cr.yp.to |
|
|
|
https://mymonero.com/ ever compromised? I deposited more than 10K xmr on mymonero last year, I forgot the last time I logged-in my wallet, it's been a long time. but today, I logged-in and found all xmr was stolen on yesterday, I have no idea how the hacker steal my xmr... Any advice for me? Please lay out screenshots, for without them, little hard to believe. vphen is in contact with me, can confirm that it appears his Monero was swiped. This is not the first time this has happened, previous instances have resulted from bad Tor exit nodes, rootkits, private keys stored in Word documents, and other malware that targets Monero. Suffice it to say, if the DNMs are waking up to Monero's usefulness now, malware authors have been aware of it for a while (see: the botnets that have been mining Monero for a couple of years already). PLEASE treat MyMonero as you would a normal wallet. If you would only carry $150 comfortably in cash in your actual wallet, then you should only keep like 40 XMR in your MyMonero wallet. For cold storage, use MoneroAddress or simplewallet offline on an air-gapped computer, and follow the instructions that have been detailed before. |
|
|
|
|
Show Posts
