Yeh, exactly. "You have the ip to work with"
one.one.one.one isnt an http/ request, its a dns lookup.
If it was an http/s request to 1.1.1.1 then it could be blocked. Also, super cheap/easy to proxy
Yeh, exactly. "You have the ip to work with"
one.one.one.one isnt an http/ request, its a dns lookup.
If it was an http/s request to 1.1.1.1 then it could be blocked. Also, super cheap/easy to proxy
You have the destination IP to work with, thats it. Otherwise it just looks like any other HTTPS traffic.
I guess if you uplpaded your own root CA cert tgen you could man-in-the-middle for deeper packet inspection.
Or, i guess, try using eMudhra's compromised private keys and hope the clients havent been updated yet
The ghost expected them there because of unfinished business
What do you mean "ExpirationDate = CurrentDate.Year + 1" doesnt work? Why shouldnt i sign certs that rely on this? What do you mean the VM orchestrator has spread these probkem VMs to all hosts and everything is fucked?
Datetimes are HARD. Just use a library
There are issues with AI involving licensing and peoples IP and crediting sources and all that.
It has also massively reduced the barrier of entry for both finding and patching bugs, and producing realistic looking bug reports.
My biggest issue (other than enviromental and social impacts) is the load it puts on developers. They pretty much HAVE to use LLMs to triage and test bug reports... because it takes very little skill to use an LLM to "deep dive this area of the linux kernel and find a bug or RCE/CVE", and the LLM probably will. But the unskilled user might not understand what the exploit/bug actually is. But they get some sort of POC and some sort of write up, and then they dump it on someone elses plate.
If that bug is actually patched/impossible because of something outside of the scope/context that the LLM used, or if its only a bug because of bad config... yeh, its a bug, but it isnt an important one. And it eats up developer resources to confirm/triage/fix that bug.
Also, LLMs are an averaging engine. They work on "most likely" probability evaluations. So, you get average code.
There has to be a human in the loop
Id say it probably is.
For single user backing up, archiving, cloud access for binary files... yeh, sharepoint/onedrive probably IS better than git.
BUT, i say that with 0 experience of using either for that. I use git for text, and i havent had the "pleasure" of onedrive/sharepoint.
But i have a feeling that onedrive/sharepoint will have an edge over git as a cloud drive system. Even if its just from a tooling/integration standpoint
Yeh, there are workarounds for large & binary files.
Git-LFS stores a pointer to the file that is stored elsewhere.
So... you have a git repo of files that point to somewhere that stores the actual files.
Great if your graphics/assets pipeline or whatever stores the files somewhere, and your codebase uses those assets.
Not great as the primary system to replace google/microsoft drive.
Might as well just have/use something that stores the actual files.
This has to be a joke.
GitHub is owned by microsoft. So just use onedrive, a system actually designed for storing files.
Git is terrible for binary files and karge files. So even if you self host a git repo, you are probably going to have a bad time.
Reform UK’s Robert Jenrick said the UK was “going down the pan and our prime minister is faffing around tweaking parking tickets” – despite trying to implement the policy himself when he was a Conservative minister.
Brilliant, honest, genuine and constructive criticism from the foreign interest UK party.
I have no issues with the prime minister setting task forces up to deal with issues people encounter every day.
Its not like that is all he is doing. Our government is - in fact - able to do more than 1 thing at once
There really is an XKCD for everything. Even if it was drawn years before what its applicable to
Purr I do not alter it furrier.
Hmm, maybe thats too much
Its a valid rant.