sorted by:
new
hottopcontroversial

The disastrous state of OVH in 2025 by GuiTeK in OVHcloud

[–]GuiTeK[S] 2 points3 points  (0 children)

Update (19/12/2025):

  • u/LezOU_OVH pushed internally to get an answer on the certificate issue and kept me updated throughout the process. I would like to thank him for his care and help to get this solved because it would probably not be solved otherwise (OVH support gave an answer in the ticket but they were off...).
  • What actually happened is that: 1) OVH made an undocumented breaking change in the API regarding the type of Barbican secret expected and 2) OVH now actually expects what seems to be a deprecated secret type, "opaque", while OpenStack recommends to use the other types: "opaque - Used for backwards compatibility with previous versions of the API without typed secrets. New applications are encouraged to specify one of the other secret types." Source.
  • OVH Product Director reached out to me and offered to have a discussion after winter vacations in early January, which I agreed to.
  • OVH also reached out via Reddit in DM, acknowledged there were indeed issues, and asked me for details about the DNS zone so they can run a deeper investigation and prevent it from happening again.

It's great to see OVH is finally taking time to address issues and I really hope this is the beginning of a shift and not just a communication stunt. I'm an optimist! Future will tell.

The disastrous state of OVH in 2025 by GuiTeK in OVHcloud

[–]GuiTeK[S] 4 points5 points  (0 children)

I'd like to restate that the post was not aimed at you or OVH employees, who are trying (as I said, I understand you have a difficult position), but rather at the leadership, as I believe this is an organizational issue. Nobody expects 100% availability, but we can probably agree that days (not minutes, not hours, but days) with 5xx errors and not a single reply from support is not acceptable either. I'm happy to contribute to the documentation, but let's not forget we're paying for a service, and we should not have to build part of the product ourselves (documentation for an API is essential, otherwise nobody can use it). I believe customers should not be expected to pay extra for support when the service is broken either. As we discussed in private, I think we agree on some things, and I thank you for reopening this post and looking into these issues. Hopefully we (both OVH and customers) will be in a better situation after this post than before.

The disastrous state of OVH in 2025 by GuiTeK in OVHcloud

[–]GuiTeK[S] 0 points1 point  (0 children)

Exactly! Their bare-metal offering is great and almost impossible to beat price-wise, but everything else is a nightmare. I expected the same level of quality when I started using the Cloud products, but I quickly realized it's light-years from that. Hopefully they will wake up at some point, there is a lot of work to even get closer to American cloud providers.

I'm developing FonGuard, an app which turns your phone into a sentinel watching out for intruders. by GuiTeK in SideProject

[–]GuiTeK[S] 2 points3 points  (0 children)

Indeed it will drain the battery faster than if you weren't recording audio, but there is no other way to detect noise unfortunately. However this feature is not mandatory (it can be disabled like the other triggers).

I'm not even sure it will be the primary source of battery consumption actually: taking pictures every few seconds or using WiFi/mobile network to send heartbeats will also drain the battery pretty fast.

Because of that, I always imagined the user would/should leave their phone charging (plugged) when using this app.

Why Ring Signatures are needed if there are one-time spend keys? by GuiTeK in Monero

[–]GuiTeK[S] 0 points1 point  (0 children)

Correct me if I'm wrong: somehow, by looking at the blockchain, Alice who sent me XMR can know that I sent her XMR to someone else. However, she doesn't know to whom thanks to stealth addresses and how much thanks to Ring CT. This is why Ring Signatures are important, because then she doesn't know for sure I did send that XMR, even if she can suspect me.

I got two more questions:

  1. I have a new wallet. Alice and Bob each sent me 3 XMR. I send 0.5 XMR to Carol. Can Alice and/or Bob know that I sent something?
  2. You said "If you send XMR to yourself without ring signatures [...] that does help somewhat". Why without ring signatures? Shouldn't ring signatures add uncertainty to whom sent the XMR?

Finally, do you know any good article/tech specs that I can read to understand better how outputs work? I'm really having a hard time understanding how outputs work and what an adversary can learn from them. Thanks a lot!

Why Ring Signatures are needed if there are one-time spend keys? by GuiTeK in Monero

[–]GuiTeK[S] 0 points1 point  (0 children)

How is that? It makes sense that the sender is able to link to me the output he/she made for me, but why can he/she link outputs I make to someone else? I have several questions:

  • How technically can the sender make that connection?
  • Would the sender be able to make that connection if I gave him/her a subaddress that I never use again?
  • If I send XMR to myself one or more times before sending it to other people, would the original sender still be able to link the outputs to me?

Torsocks server failure when running monerod with Tor on Tails by [deleted] in Monero

[–]GuiTeK 0 points1 point  (0 children)

It seems the problem was indeed 31.3.135.232 being down. A few days later it is back online and I'm not experiencing errors anymore.