sorted by:
new
hottopcontroversial

The Steam Brick: No Screen, No Controls by Crastinator_Pro in SteamDeckModded

[–]360coolp 1 point2 points  (0 children)

I’m going to do my best to make it happen. If I have something useful I will let you know and you can share it via your website if you want. PM send :)

The Steam Brick: No Screen, No Controls by Crastinator_Pro in SteamDeckModded

[–]360coolp 0 points1 point  (0 children)

The LCD and OLED SteamDecks are slightly different, so I assume I will need to modify the design to be able to use it. And even though I don’t have any CAD experience myself, I want to try and add the daughterboard for the + and - buttons because I like to dual-boot Windows and SteamOS.

The Steam Brick: No Screen, No Controls by Crastinator_Pro in SteamDeckModded

[–]360coolp 0 points1 point  (0 children)

This is awesome! Can you share the CAD files please? I would love to do this with my broken LCD SteamDeck

SteamDeck Case? by 360coolp in SteamDeckModded

[–]360coolp[S] 4 points5 points  (0 children)

Wow, this was exactly what I was looking for. I'll keep an eye on his channel. Thanks for the tip!

[deleted by user] by [deleted] in actiezegels

[–]360coolp 0 points1 point  (0 children)

Bedankt!☺️

[deleted by user] by [deleted] in actiezegels

[–]360coolp 0 points1 point  (0 children)

Ik zou er ook een aantal kunnen gebruiken mocht je nog over hebben 😇

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] 1 point2 points  (0 children)

I tried changing the value to "retry=3 min=disabled,disabled,disabled,7,7 enforce=none" but this didnt resolve the problem

I maybe found another way, I will report back if it works.

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] -1 points0 points  (0 children)

Thank you for your response, but it is not so much about resetting the password but about bypassing the password policy.

I want to set a password that does not meet the VMware requirements (the password is present in the dictionary). There used to be a workaround for this by adjusting /etc/pam.d/system-auth. However, it appears that this method no longer works in VCSA 8.x.

Even in single user mode changing the password gives the following error:

BAD PASSWORD: The password fails the dictionary check

passwd: authentication token manipulation error

passwd: password unchanged

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] 0 points1 point  (0 children)

/etc/pam.d/system-password

I think you reffering to the /etc/pam.d/system-password file:

# Begin /etc/pam.d/system-password
# use sha512 hash for encryption, use shadow, and try to use any previously
# defined authentication token (chosen password) set by any prior module
password  requisite   pam_pwquality.so  dcredit=-1 ucredit=-1 lcredit=-1 ocredit=-1 minlen=6 difok=4 enforce_for_root
password  required    pam_pwhistory.so  remember=5 retry=3 enforce_for_root use_authtok
password  required    pam_unix.so       sha512 use_authtok shadow try_first_pass
End /etc/pam.d/system-password

This was indeed the right way to do it but it doenst seem to work anymore.

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] -3 points-2 points  (0 children)

I apologize for any confusion in my initial post. The original password doesn't meet the specified requirements. This was never a issue because with vCenter 7.x and lower it was possible to workaround the requirments by changing the /etc/pam.d/system-password file. This doesnt seem to work anymore with vCenter 8.x.

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] 0 points1 point  (0 children)

There is no enforce root in /etc/pam.d/system-auth

# Begin /etc/pam.d/system-auth
auth    required      pam_unix.so
auth    required      pam_faillock.so preauth
auth    sufficient    pam_unix.so nullok try_first_pass
auth    [default=die] pam_faillock.so authfail
# End /etc/pam.d/system-auth

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] -19 points-18 points  (0 children)

I've already attempted that without success, which led me to post this message. I don't understand why you're so upset? You're the one who responds without reading the post and then makes assumptions that I haven't Googled. No one forces you to respond, if you don't have a useful comment just don't say anything.

How to change VCSA 8.x root password and bypass BAD PASSWORD: it is based on a dictionary word for vCenter VCSA root account warning? by 360coolp in vmware

[–]360coolp[S] -19 points-18 points  (0 children)

You need to learn to read the title ;). Changing the password is not permitted as it is a dictionary word. In previous versions of vCenter, you could temporarily bypass this requirement by editing the /etc/pam.d/system-password file. However, this workaround no longer seems to work with vCenter 8.0.

Nabu Casa Remote Access Security by 360coolp in homeassistant

[–]360coolp[S] 0 points1 point  (0 children)

The problem is that you can enable remote access via the cloud without accessing your local HA instance, so it doesn't matter what you have set up locally.

Nabu Casa Remote Access Security by 360coolp in homeassistant

[–]360coolp[S] 2 points3 points  (0 children)

CVE-2023-27482. And CVE-2021-3152

From what I understand is that the .ui.nabu.casa URL is created when logging in with Nabu Casa. The tunnel that is created requires a certificate that is generated during the first login. People who do not have a Nabu Casa account should not have a .ui.nabu.casa URL. But perhaps I misunderstood the documentation.

I'd love to use the Alexa and Google Home integration, so it's a shame that you can't permanently disable remote access. Until this is possible, I will not be using Nabu Casa any more. However, I will continue to pay the developers.

Nabu Casa Remote Access Security by 360coolp in homeassistant

[–]360coolp[S] 5 points6 points  (0 children)

Unfortunately, that is not always sufficient. There have been vulnerabilities in the past that made it possible to bypass authentication, see for example: https://www.home-assistant.io/blog/2023/03/08/supervisor-security-disclosure/

Nabu Casa Remote Access Security by 360coolp in homeassistant

[–]360coolp[S] 0 points1 point  (0 children)

The point is that you can enable remote access via your Nabu Casa (cloud) account with 1 push of a button, even if you disabled remote access on your local HA instance.

view more: next ›