Live data from Hacker News

Viewing profile — markuman123

markuman123

HN member
Joined
Sun, Sep 22, 2019, 3:28 PM UTC
HN karma
101
Public activity
30 items

About markuman123

No profile information was provided.

Recent public activity

  1. comment
    Comment #42747347

    Three layer of defense on default Port here. 1. ufw limit ssh. 2. Ansible devsec.hardening.ssh_hardening 3. fail2ban

  2. comment
    Comment #42675172

    Energyconsumption is a reason for a CPU update.

  3. comment
    Comment #42675165

    Energyconsumption is nowaday the reason for a CPU Update.

  4. story
  5. comment
    Comment #39508820

    I store my TOTP secrets in the Gnome Keyring totp() { TOKEN=$(keyring get totp $1) oathtool -b --totp $TOKEN | xclip } and my TOTP secrets are saved via ansible-vault - name: set T…

  6. comment
    Comment #36033472

    Surface Go

  7. comment
    Comment #35295402

    maybe the certificate crew is laid off?

  8. comment
    Comment #35295388

    expired two days ago (3/22/2023) and no one cares

  9. comment
    Comment #34515787

    russia? shut down a service and halt the productivity of most companies in the west...because most companies moved to azure ad and teams.

  10. comment
  11. comment
    Comment #34145494

    Passwords for nextcloud

  12. comment
    Comment #33504009

    no valid https ...

  13. comment
    Comment #33018105

    raspberry pi (some low energy home computer) serving nextcloud, offline wikipedia and OSM.

  14. comment
  15. comment
    Comment #29187927

    it's super easy to integrate in every ci/cd pipeline

  16. comment
    Comment #29091144

    I always wonder why people are investing so much energy and time to invent New tools instead oft using existing tools that already solve the same issues. Just use ansible for that.…

  17. comment
    Comment #27818177

    with ansible

  18. comment
    Comment #25843201

    using s3 as a cdn is a complete different thing than leaking intentionally credentials.

  19. comment
    Comment #25838592

    Sorry, I cannot follow. To be clear, I'm no aws advocate.

  20. comment
    Comment #25838250

    Nope, because you just get a 404, even on public buckets, because you have no access to the kms key.

  21. comment
    Comment #25837997

    that's the reason why should always use aws:kms encryption on s3.

  22. comment
    Comment #25837828

    but the budget alert is delayed...I bet you're ruined when you've noticed the alert.

  23. comment
    Comment #25837131

    AWS_PROFILE=broken aws s3 ls s3://deltars/simple/ 14kb in your bucket and you pay for outgoing traffic. means, while you're sleeping, I can ruin your aws bill. In any case, committ…

  24. story
  25. story