Hacker News new | past | comments | ask | show | jobs | submit | markuman123's comments login

Three layer of defense on default Port here.

1. ufw limit ssh.

2. Ansible devsec.hardening.ssh_hardening

3. fail2ban


Energyconsumption is a reason for a CPU update.


(FYI: You've posted this comment twice, some seconds apart. I've responded to the older one)


Not really. The era of "modern efficient CPUs" started some 10-15 years ago. Under light loads, Ivy Bridge or Haswell is going to have a similar thermal profile to modern machines.

Many of the new machines are actually worse, e.g. 3770K @77W vs. 14900K @125W/253W. That isn't to say they're not also faster, but if you actually use it you're burning more watts.


Energyconsumption is nowaday the reason for a CPU Update.


Unless you have a CPU from 2000, probably it's not worth the energy savings to have a new one produced:

> The report about the cost of planned obsolescence by the European Environmental Bureau [7] makes the scale of the problem very clear. For laptops and similar computers, manufacturing, distribution and disposal account for 52% of their Global Warming Potential (i.e. the amount of CO₂-equivalent emissions caused). For mobile phones, this is 72%. The report calculates that the lifetime of these devices should be at least 25 years to limit their Global Warming Potential.

https://wimvanderbauwhede.codeberg.page/articles/frugal-comp...

This is for consumer devices btw, probably not if you operate some server farm with high occupancy (steady load on all hardware)


When I upgraded 5 years ago, general mechanical failure without available replacement parts was the driving factor, but energy consumption was high on my list. A light laptop with a long battery life is something that never used to exist, and it definitely improves my quality of life. If battery life at a low weight cost doubles in the next 5-10 yrs I'll probably upgrade again even if the machine is usable.


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 TOTP in keyring
      with_items: "{{ TOTP }}"
      community.general.keyring:
        service: totp
        username: "{{ item }}"
        password: "{{ TOTP[item] }}"
        keyring_password: "{{ keyring_password }}"


Beware: That shell function will use the secret on a command line, leaking the secret to the process list, available to every user on the system. The oathtool manual page even warns about this.

I would instead recommend something like:

  totp() {
    oathtool --base32 --totp -- @<(keyring get totp "$1") | xclip
  }
(Bash required.)


Surface Go


maybe the certificate crew is laid off?


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


i think they added the wrong cert. it was working earlier today.


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


> russia?

Oh please. Azure is plenty capable of taking themselves offline on their own.


I'm not sure Russia is as capable as you've all spent the last few decades making out....


No.


Passwords for nextcloud


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: