12:01:43 <mj-xmr> moneromooo> In any case, I'm not sure it's worth wasting time just to make github servers happy. <--- After taking a deeper though about it, what I'm doing is actually providing more error margin, IN CASE somebody overloads the Github servers one way or another. Then the mining process is not to be blamed for this, and thus should not be canceled, just because it took too much CPU time (which had to be shared at that moment).
12:24:17 <selsta> anyone have an idea about https://github.com/monero-project/monero/issues/7386 ?
12:28:28 <sech1> he can try to download the same old version monero-wallet-cli and restore it there, then use the v0.17.1.9
12:36:45 <selsta> ok suggested that in a comment
14:29:30 <Inge-> How is the monero wallet encrypted with password? ChaCha8 something?
14:40:42 <moneromooo> chacha20
14:41:02 <moneromooo> It used to be chacha8 until... maybe two years ago.
14:48:16 <Inge-> Someone got their parents into monero, and they lost both their password and image of seed ... looking at options for retrieving wallet - hashcat supports ChaCha20 but more for hashes than for decrypting a wallet
14:56:47 <wfaressuissia[m]> How much space size of password are you going to brute force ?
14:57:32 <wfaressuissia[m]>  * What alphabet and how many characters are you going to brute force ?
14:57:50 <Inge-> If I could leverage hashcat with wordlists and masks, my chances are pretty good
14:58:23 <wfaressuissia[m]> There is default lang for masks with english lower/upper/both case alphabets
15:03:41 <moneromooo> I wonder if a Cryptonight ASIC could be used for that. It might be much slower if you change the input all the time...
15:09:07 <wfaressuissia[m]> "If I could leverage hashcat with wordlists and masks, my chances are pretty good" You don't work size for brute force and don't know speed of your GPUs, right ?
15:09:34 <wfaressuissia[m]> also didn't extract hash of password from wallet file
15:28:53 <Inge-> I don't know if it is chacha8 or 20 even
15:29:11 <Inge-> speed of GPUs is easy enough to check - at least if it is chacha20
15:30:43 <Inge-> looks like a single vega64 can do 5.6GH/s chacha20 (synthetic, so only realistic for a mask attack)
15:31:36 <wfaressuissia[m]> I need the same script that accept wallet file path and return hashcat args to brute force
15:31:41 <wfaressuissia[m]> writing ...
15:31:54 <Inge-> chacha20 was checked in on Dec25th 2017. moneromooo: You don't do holidays, do you :P
15:39:16 <Inge-> Is there some good way to determine if a file is a valid monero wallet? I guess that is the only way to validate the decryption being "correct"
16:22:34 <moneromooo> The plaintext should be valid JSON. So test whether the first few characters are... hmmm... {" maybe. Log your own wallet's decrypted contents, see the first few bytes.
16:22:46 <moneromooo> If it passes that, parse with an actual JSON parser.
16:42:24 <wfaressuissia[m]> "https://github.com/ph4r05/py-cryptonight" this doesn't produce valid cn_slow_hash(...) hashes
16:42:30 <wfaressuissia[m]>  * "https://github.com/ph4r05/py-cryptonight" this module doesn't produce valid cn_slow_hash(...) hashes
16:50:50 * moneromooo grumbles at the build suddenly spamming warnings about pointless stuff, hiding interesting stuff
17:00:18 <wfaressuissia[m]> "I wonder if a Cryptonight ASIC ..." if these devices support only fixed offset for nonces then they are useless
17:23:09 <wfaressuissia[m]> "looks like a single vega64 can do 5.6GH/s chacha20"  password -> [cryptonight (original)] -> chacha key -> [chacha20(<constant prefix from wallet.bin.keys>, <chacha key>, <chacha initialization vector from wallet.bin.keys>)] -> decrypted prefix of account data -> [memcmp(<...>, {"key_data":)] -> true / false
17:23:46 <wfaressuissia[m]> If there is no availabel ASIC then you take cn/0 implementation from xmrig and add support of this scheme into hashcat since xmrig doesn't have sophisticated pw generator
17:23:55 <wfaressuissia[m]>  * If there is no available ASIC then you take cn/0 implementation from xmrig and add support of this scheme into hashcat since xmrig doesn't have sophisticated pw generator
17:24:22 <wfaressuissia[m]> cn/0 will be bottleneck of this brute force
17:24:40 <wfaressuissia[m]> you need at most 12 bytes of chacha so it isn't important
17:40:06 <wfaressuissia[m]> "looks like a single vega64 can do 5.6GH/s chacha20" 2kH/s for cryptonight (cn/0, you can check with xmrig)
17:40:22 <wfaressuissia[m]> Is it feasible to brute force forgotten characters with this speed ?
17:42:01 <wfaressuissia[m]> it should be easy to add support, e.g. https://github.com/hashcat/hashcat/pull/2559/files, only 2 major files are need adopted OpenCL code from xmrig and input/output processing
17:42:10 <wfaressuissia[m]> but the speed will be slow
18:07:53 <mj-xmr> moneromooo, I believe the warning spam will be solver with:
18:07:54 <mj-xmr> https://github.com/monero-project/monero/pull/7394
18:07:59 <mj-xmr> Which you already approved.
18:59:24 <dEBRUYNE> .merges
19:00:19 <selsta> dsc bot got k-lined
19:06:12 <hyc> how sad
19:50:01 <gingeropolous> is it known that submodules are are borked?
19:50:43 <gingeropolous> "Fetched in submodule path 'external/miniupnp', but it did not contain 544e6fcc73c5ad9af48a8985c94f0f1d742ef2e0. Direct fetching of that commit failed.
19:50:43 <gingeropolous> "
19:50:51 <gingeropolous> on master
19:51:13 <moneromooo> No. AFAIK they're not.
19:51:14 <iDunk> git submodule sync
19:51:32 <iDunk> git submodule update
19:51:45 <moneromooo> git submodule unbork
19:51:51 <iDunk> ^
19:52:06 <moneromooo> (but if they're not borked, would it actually bork them...)
19:52:33 <gingeropolous> danke schon
19:53:47 <iDunk> https://github.com/monero-project/monero/pull/7311
19:53:56 <gingeropolous> gonna see if master has any new tricks to deal with my public node eventually just dieing on wallet connections
19:54:09 <iDunk> It actually builds the whole thing now, not just libminiupnpc.
19:56:39 <gingeropolous> lets see if xmrchain.net breaks it too
20:03:01 * gingeropolous grumbles about not compiling debug. ponders if he should compile debug
20:21:12 <ttaynsgurpp> Remember kids. If you call project coral reef for what it is - fluffypony embezzling half a mil usd from the monero fund for a website with smaller adoption than monero woo plugin, you will get excommunicated. Why do you think charities need Teslas? They don't and Elon won't support Monero 150k will sure buy a lot of party time for those that actually do get it.
20:37:41 <ndorf> what the heck just happened to #monero
20:37:50 <moneromooo> Hilarious :D
20:38:20 <sethsimmons> uhhh
20:38:22 <sethsimmons> Did our channel get taken down?
20:39:11 <ndorf> 13:35 -!- mode/#monero [+b *!*@*] by ChanServ
20:39:19 <ndorf> seems excessive.
20:40:02 <luigi1111w> moneromooo we dying here
20:40:41 <sethsimmons> How did our channels get dropped?
20:40:57 <Nebraskka> chanserv hijack of some sort?
20:41:04 <ndorf> looks like it
20:41:09 <sethsimmons> Anyone else from Core around to help figure it out?
20:41:17 <sethsimmons> fluffypony maybe?
20:41:35 <sethsimmons> Heard Core has some special access to #monero* channels
20:41:48 <sethsimmons> Never a dull moment in Monero...
20:43:34 <Nebraskka> yesterday there were strange PMs on freenode from random nicknames, some windows batch commands or whatever, maybe someone got compromised who had access to chanserv
20:44:50 <moneromooo> fluffy running windows ? :D
20:45:04 <moneromooo> Oh wait, I should not, I'm fluffy...
20:45:08 <moneromooo> *know
20:45:26 <hyc> strange selection of targeted channels
20:46:05 <ndorf> one of those spam messages yesterday did say "attn: freenode is moving to irc.crimeircd.net" so it does seem like it could be related
20:46:14 <moneromooo> Freenode ops are fixing.
20:46:26 <Nebraskka> thx
20:46:30 <Nebraskka> good to hear
20:46:45 <hyc> I wonder if someone saw that msg and actually tried to login with their IRC passwd to that server
20:47:44 <marmulak> was the channel hacked or something
20:48:38 * marmulak scrolls up
20:48:55 <ndorf> hyc: yikes, if true
20:51:22 <marmulak> wait so this is not #monero, but #monero-dev right?
20:51:29 <ndorf> yes
20:51:38 <marmulak> ahh this all makes sense now
20:52:48 <moneromooo> Yes, seems like pony indeed.
20:53:06 <moneromooo> Channels seem joinable now fwiw.
20:53:08 <marmulak> on purpose? >_>
20:55:08 <selsta> 20:54 <iDunk> It actually builds the whole thing now, not just libminiupnpc. <-- why?
20:55:34 <selsta> was something wrong in my PR or change in miniupnp repo?
20:55:54 <moneromooo> I think it refers to miniupnpc being only part of the repo IIRC.
21:07:05 <iDunk> monero branch in our repo was set up to only build libminiupnpc, IIRC.
22:07:13 <rogu> Hello! Where can I find what the monero block template consists of (field blocktemplate_blob of getblocktemplate response)?