02:13:03 hello need a lil help on hackerone anyone active? 02:13:24 what kind of help? 02:13:54 I am submitting a report there I donot know which weakness or type of weakness to choose 02:14:46 I dont get these computer terms can anyone help+ 02:15:53 ?? 02:16:05 it's a little hard to give specific advice - an important part of the vulnerability response process is not telling anyone outside that process what the vulnerabilities are 02:16:24 have you tried looking up the confusing terms? 02:16:57 well if the vulnerabilities consist of making it traceable then what should I choose 02:17:20 moreover if i donot have any screenshots or video to show so is that okay? 02:19:18 I don't know what options you have to select fro 02:19:49 from*. You don't need evidence as long as you can clearly explain the vulnerability. 02:23:54 okok thanks 06:27:38 DanishHassan[m]: is that you who filed 1955468 ? 06:29:15 Well, for whoever did, because I am not going to assume it's you just now: Hackerone is for vulnerability reports, not hanwavy bullshit, especially around known issues. The goal of H1 is to improve monero, and such reports don't. I suggest you actually look at monero first. 06:29:23 Bloody time wasters. 06:32:21 Why am I not surprised 06:36:00 Odd though, the initial questions seemed sane. Oh well. 06:37:00 At least it was easily assessed. I remember some horrendous asshole before who managed to move goalposts with bullshit for quite some time. 08:06:54 hello 08:08:22 Hi. If you have a question related to monero development, just ask it and wait. 08:09:56 I wanted to complain about monero-javascript, I am running an old version that has vulnerabilities so I am trying to migrate but there is nothing in the doc about exception handling and for example I have noticed that things chaanged with createTx() method and relay = true so this migration is pissing me off 08:11:06 Sorry sir. The link didnt come through. Monero Community Dev is the correct room for monero javascript 08:13:42 sorry I will post there 13:12:32 moneromooo: does this mean corrupted db? https://github.com/monero-project/monero/issues/8826#issue-1675840108 13:12:35 or bug in pruning code? 13:38:15 hyc: if I call mdb_cursor_get on values k and v while in a write txn, then commit that txn and reopen another txn, are the k and v values still valid, as the cursor is gone ? The doc doesn't say. 13:38:47 I do that to resize the db while pruning, and I suspect it might be the reason for 8826. 13:41:33 And by k and v I mean also the mv_data they point to. 15:44:22 moneromooo: once the txn commits all bets are off 15:45:34 http://www.lmdb.tech/doc/group__mdb.html#ga8bf10cd91d3f3a83a34d04ce6b07992d 15:45:45 "Values returned from the database are valid only until a subsequent update operation, or the end of the transaction. " 15:48:00 ty 15:53:30 I was wrong anyway, it's another txn that was committed. Reading old code. 21:47:11 Hello monero people 21:47:40 I have a question, i was trying to find news, updates and roadmap where monero is heading 21:51:18 I apologize i've just read the title (should do it before) i'll join monero channel