There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

MonkCanatella OP , (edited )

I found something that says (removed bunch of random identification shit from url vars)

Failed to exec curl command, with url: https://update7.synology.com/autoupdate/v2/getList , with reason: error setting certificate file: /etc/ssl/certs/ca-certificates.crt

I SSHed into /etc/ssl/certs and that doesn’t exist. What does exist is a bunch of files like “b23h893.0” "“fb3j58d.0”, etc. using ls -l I see that they have lrwxrwxrwx permissions on all of them and they point to stuff like affirmtrust, comodo cert, amazon_root, etc. nothing that makes any sense to me.

checking certificates from the control panel, all certificates are assigened to the cert generated by my quick connect url. I have 3 in total, one with my quick connect url, one with .direct.synology.me, and and that’s just ‘synology’. They all have a lock with a green checkmark, assuming that means they’re legit but idk. What may be causing issues is that I can’t use my quick connect. It’s glitchy - I can’t enable it because I get a connection error, but I’m wondering if that’s cause of some certificate or maybe it’s due to the error I showed above - that setting up the quick connect is throwing an error because it wants to write to some certificate that doesn’t exist.

EDIT:

I found a (with the single quote around it) ‘NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt’ in my /usr/shares/ca-certificates/mozilla . So ca-certificates exists but not where this updater thing is looking.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines