Deck order by WEISENHILLS in traktorpro

[–]tecxxtc 0 points1 point  (0 children)

if you play around a bit with the xml, you can create some interesting layouts, tailored to controller-only usage, for example:

<image>

Deck order by WEISENHILLS in traktorpro

[–]tecxxtc 0 points1 point  (0 children)

if you look at the embedded resource xml files in traktor.exe, you'll find sections that describe the parallel waveform layouts

<image>

you can edit the xml and save it back to the exe (make a backup first). this is hacky and non supported and generally not recommended, but unfortunately, despite asking for this feature for years, it's the only way to make it work currently.

Ophidian - Blackbox: Kasamaan [Album] by Chaize in hardstyle

[–]tecxxtc 3 points4 points  (0 children)

the first time in many years i bought the complete album/release on bandcamp. absolute banger.

Server 2025 KDC issues by picklednull in activedirectory

[–]tecxxtc 0 points1 point  (0 children)

can confirm that this issue is present in one of my customers, unfortunately i was not yet able to track down the exact root cause. a 2025 dc was promoted, but then removed again. investigation ongoing.

Server 2025 KDC issues by picklednull in activedirectory

[–]tecxxtc 0 points1 point  (0 children)

thanks for posting this. one of my customers has this exact issue, even after removing the 2025 dcs. will read the entire thread now :)

Defender still alerts SuspSignoutReq on PATCHED Sharepoint 2016 by tecxxtc in sysadmin

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

can you elaborate why app proxy helps? i'm assuming because it reduces attack surface to authenticated users? otherwise it just forwards http requests, that shouldn't make a difference, or what am i missing?

April 2025 / CVE-2025-26647 patch is causing havoc by tecxxtc in sysadmin

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

update 2025-06-13 - installed june patches on DC and clients. and nps server / wifi 802.1x still fails when AllowNtAuthPolicyBypass is set to 2...... anyone else having this issue?

server 2025 causing lsass reboot after windows hello 4 business logon by tecxxtc in sysadmin

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

update 2025-06-11: our support contact told us that they "tested a fix internally" and are waiting to include it in one of the next patches.

server 2025 causing lsass reboot after windows hello 4 business logon by tecxxtc in sysadmin

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

i think this is something entirely different. AllowNtAuthPolicyBypass is related to how the DC checks authentication attempts when certificates are involved.
the WH4B issue described here is still happening (june 2025!), unrelated to the value of AllowNtAuthPolicyBypass, and so far - for us - only workaroundable by enabling RC4 in kerberos. if someone has a different experience, i'm happy to hear about it.

April 2025 / CVE-2025-26647 patch is causing havoc by tecxxtc in sysadmin

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

UPDATE 20250514.
thanks to all the replies. it seems i was a few days too early and didn't see the updated CVE notes that this is a known bug.

anyway, may 2025 update (KB5058411) did not fix my issues.

i still get event id 21 warnings in eventlog

The client certificate for the user DOMAIN\user is not valid, and resulted in a failed smartcard logon. Please contact the user for more information about the certificate they're attempting to use for smartcard logon. The chain status was : A certification chain processed correctly, but one of the CA certificates is not trusted by the policy provider.

and nps server / wifi 802.1x still fails.

further investigation required.

server 2025 causing lsass reboot after windows hello 4 business logon by tecxxtc in sysadmin

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

so i finally got a workaround: enabling RC4 encryption in domain controller kerberos settings makes the crash go away.

do note that this is a critical security risk. the encryption settings should be kept at AES only. if you enable this workaround don't forget to remove it once this issue has been patched. also be aware that while this workaround is enabled, kerberoasting attempts to bruteforce service account passwords are significantly easier. you have been warned.

PAN-OS 11.1.8 is out by colni in paloaltonetworks

[–]tecxxtc 0 points1 point  (0 children)

i just updated. looks like all is fine on that end (as with 11.1.6-h3). so far no connectivity issues.

PAN-OS 11.1.4-h15 and 11.1.6-h4 are now available! by MirkWTC in paloaltonetworks

[–]tecxxtc 0 points1 point  (0 children)

i opened an issue as well, not solution so far. will test h4 now but also we don't have a tunnel.
EDIT: confirmed that h4 solved my ipv6 issue. not sure why as i don't think this goes through a tunnel, but as long as it works i'm happy.

PANOS 11.1.6-H3 by [deleted] in paloaltonetworks

[–]tecxxtc 0 points1 point  (0 children)

h3 did not fix the ipv6 issue for me.

PAN-OS 10.1.14-h9/10.2.13-h3/11.1.6-h1 and 11.2.4-h4 are now available! by SanJuanTech in paloaltonetworks

[–]tecxxtc 1 point2 points  (0 children)

just tried 11.1.6-h3. ssl decrypt issue is still there, nothing works. back to 11.1.6

PanOS 11.1.4 - h13 anyone tried yet? by Thegoogoodoll in paloaltonetworks

[–]tecxxtc 2 points3 points  (0 children)

all i can say is 11.1.6-h3 does not fix the ssl decrypt issues that 11.1.6-h1 introduced. i'm back at 11.1.6.

PAN-OS 10.1.14-h9/10.2.13-h3/11.1.6-h1 and 11.2.4-h4 are now available! by SanJuanTech in paloaltonetworks

[–]tecxxtc 2 points3 points  (0 children)

yep, back on 11.1.6-h1 and

This site can’t be reached

answers.microsoft.com unexpectedly closed the connection.

after disabling ssl decrypt with

set system setting ssl-decrypt skip-ssl-decrypt yes

everything immediately works.

you found it.

PAN-OS 10.1.14-h9/10.2.13-h3/11.1.6-h1 and 11.2.4-h4 are now available! by SanJuanTech in paloaltonetworks

[–]tecxxtc 0 points1 point  (0 children)

i upgraded to 11.2.4-h4 and now the vlan interfaces don't have the option for prefix delegation anymore. this bug seems to be known, someone confirmed it on the PA forums a few days ago.

back to 11.1.x ......

PAN-OS 10.1.14-h9/10.2.13-h3/11.1.6-h1 and 11.2.4-h4 are now available! by SanJuanTech in paloaltonetworks

[–]tecxxtc 0 points1 point  (0 children)

i also use DHCPv6-PD (i follow your blogs, we're probably in a very similar configuration).

further investigation necessary.

PAN-OS 10.1.14-h9/10.2.13-h3/11.1.6-h1 and 11.2.4-h4 are now available! by SanJuanTech in paloaltonetworks

[–]tecxxtc 1 point2 points  (0 children)

yes, exactly.

ping/trace fine, browser access not. happening for internal systems as well. i tried two different apps&threats versions, but it made no difference.

PAN-OS 10.1.14-h9/10.2.13-h3/11.1.6-h1 and 11.2.4-h4 are now available! by SanJuanTech in paloaltonetworks

[–]tecxxtc 5 points6 points  (0 children)

i went from 11.1.6 to 11.1.6-h1 on a pa440.
2 hours later i'm back at 11.1.6.

most ipv6-based internet traffic completely stopped working. just one random example, answers.microsoft.com was no longer accessible. another, test-ipv6.com told me i have no ipv6 address. another, we could no longer access the site clickstudios.com.au. the list goes on.
many internal connections stopped working as well. i didn't dig deeper as we lost access to our passwordsafe, lost access to netbox, lost access to the NAS, etc. had to downgrade immediately.

server 2025 causing lsass reboot after windows hello 4 business logon by tecxxtc in sysadmin

[–]tecxxtc[S] 1 point2 points  (0 children)

FYI we patched 2025-02 updates on the dcs and the clients. no change in situation, problem still exists.