freenode #monero-dev

11 Dec 2019

Official repo: github.com/monero-project/monero || Don’t ask to ask, just ask:) || Non-dev questions -> #monero, please || Next dev meeting is detailed on the Monero meeting issue on Github: github.com/monero-project/meta/issues

• 06:11
  Masari45
  thank you all for your advice
• 11:12
  naughtyfox
  Hi guys! Does monero support working with ledger nano x via bluetooth at the moment?
• 11:14
  Inge-
  no
• 11:14
  Inge-
  only cabled
• 11:15
  naughtyfox
  thanks!
• 11:26
  Inge-
  also, bluetooth is a bit of a security nightmare
• 14:20
  hyc
  keep an eye out for Unbound bugfixes ostif.org/our-audit-of-unbound-dns-by-x41-d-sec-full-results
• 15:33
  Guest78835
  moneromooo: gitlab needs an update. Git had some vulnerabilities that got fixed
• 15:34
  Guest78835
  for the curious: CVE-2019-1348 CVE-2019-1349 CVE-2019-1352 CVE-2019-1353 CVE-2019-1387 CVE-2019-19604
• 15:40
  moneromooo
  Done, thanks.
• 16:05
  gingeropolous
  despite the erroneous conclusion, an "un-prune" would be a healthy option for a node. Though i guess you could just resync? : old.reddit.com/r/Monero/comments/e98hhu/reverse_database_prune
• 19:34
  dEBRUYNE
  gingeropolous: Potentially a lot of work for little benefit, imo
• 19:34
  selsta
  unprune = resync, yes
• 20:24
  hyc
  yes, since unprune requires you to obtain the 7/8ths of the data that you're missing
• 20:24
  hyc
  or whatever the proportion is