Cwhat's the full launch args you're trying to use?
C
DI tried the end and I tried before token last time as well
DOH before the tunnel command? :monkaHmm:
DAYO
DSMH MY HEAD
Dit works lmao
DThank you for that
DLast time I tried it after the run/before token. Apparently it needs to be before tunnel :help:
Dbrb calling my eye doctor :facepalm:
Ahi all, I imported a bunch of zones into Cloudflare via API. While I can resolve TXT, CNAME, and MX records... I am not able to resolve A records unless I go into the UI and manually update e.g. the TTL on the record. Is there some kind of zone reload or refresh I need to do to get the A records resolving?
Dauto seemed to work too, but I'm hesitant to use it if it's "broken". Then again, I'm doing this to drop my IPv4 so I'm not charged for it so 6 should be fine lmao
DDepends on the previous record and its TTL, if it existed. Did you move your domain to Cloudflare recently or is this new or?
Ai moved them yesterday
Aprevious record TTLs were short. like 5 minutes
DYeah it should be well past expired but depends on the TTL of the previous host.
DYeah so it should've been done with a trip to the restroom lol
Ait's not that they're resolving to old IPs. The nslookup respone is saying that it can't resolve an IP at all
Dmight be a bad record then
DDid you put it in as just
{sub} {IP} or did you do {sub}.{domain}.{TLD} {IP}?Dor are you just talking about the root domain
Ai put sub. root domain as well as subs
Athe strange thing is that when I edit the record and change the TTL and save it, I can then resolve it
WWhat is the point in MFA if it's in your browser
WIt's supposed to be on a separate device isn't it?
WKinda like a Yubi Key
DI mean technically it helps mitigate user/password use, but there's no way in hell I'd put that on some random browser extension lmao
TI don't even use it
Vmeeting MFA requirements in a way that isn't laughably inconvenient :p
VPasskeys are really good for that reason
Tit's your browser, so anyone else on the planet wouldn't have access to that
IExtensions sync between Chrome profiles on different computers (that's Chrome pictured there) and extension data would include TOTP data from that extension so if someone got your Google account they'd have your 2FA as well... unlikely but very much possible.
TI would imagine that if someone owned your Google account you would have much larger problems to be honest
TGiven most companies let you reset 2fa via email........
IQuite possibly yes - but imagine if you had a work account that had a corporate email (non-gmail)
IIf you had it in an extension they'd be able to see—but they wouldn't be able to reset 2FA
Twhich in theory compromises passkey as well if it's software based.
Tso 1password, bitwarden, etc are hardware based?
RPassword managers still have to sync the private key, surely malware could dump it
Vand many TPM impls actually don't perform crypto within them iirc
RThen how do you think the syncing works
Tlol
R
Vnothing is going to be both convenient enough for the average user, and secure against malware
RConvenience vs security is a trade off
I1Password's encryption is quite up-to-spec. They use a dual method - your password plus a random 64-char token that you must have to sync to a new device.
VI'm not managing a million passwords, plus a million totp codes on some terrible totp app, plus a million passkeys
Tfeels like an opinion. the FIDO Alliance has spoken fairly highly of 1passwords passkey implementation
RPasskeys in 1Password are still a step ahead of passwords imo, regardless of whether malware can steal them or not
IAnd if you really want security then use a Yubikey or something... that's what CF does.