What's the difference between the HTTP and the HTTPS Protocol?
• HTTP transmits your Data from your Client to the Webserver without encrypton.
What does this mean? A Hacker could intercept your Data and could then read the message that you've sent to the Webserver.
• HTTPS transmits your Data from your Client to the Webserver with encrypton so you're messages can't be read from People that want to Intercept them and read them without the encrypton key(session key).
Summarized: The HTTPS Protocol is the Secure Version of the HTTP Protocol, HTTPS runs with a TLS(Transport Layer Secure) protocol formerly called SSL (certificate) so the Messages that get intercepted that someone sees are Way harder to decode.
my company got breached
the attacker had access for 11 days
on day 3 he emailed our IT helpdesk
complained that the VPN was slow
our helpdesk reset his password
upgraded his access tier to fix the "connectivity issue"
and closed the ticket as resolved
CSAT score: 5 stars
we found this in the logs during forensics
the attacker had rated our IT support
excellent
I have just completed the Intro to Academy module on HTB Academy! https://t.co/wI9wnKyFOD #hackthebox#htbacademy#cybersecurity
I will start a new Journey and let's see were i'll go with it, i wish everyone much success and a great Day.
Keep going | Keep improving
> be John Ternus
> 1997. engineering degree. nobody cares
> first job: VR headsets at a dead startup
> join Apple in 2001. first project: a monitor
> spend 25 years in the shadows
> iPad. AirPods. iPhone 12. Apple Silicon. all him
> never had the corner office. refused it twice
> Tim Cook took Apple from $350B to $4 TRILLION
> today Apple named you CEO
> engineer who made your stuff just became the boss
Tim Cook turned $350B into $4T. now it's Ternus's turn.
what does a guy who actually builds things do with the most valuable company on earth?
Hacking the #EU#AgeVerification app in under 2 minutes.
During setup, the app asks you to create a PIN. After entry, the app *encrypts* it and saves it in the shared_prefs directory.
1. It shouldn't be encrypted at all - that's a really poor design.
2. It's not cryptographically tied to the vault which contains the identity data.
So, an attacker can simply remove the PinEnc/PinIV values from the shared_prefs file and restart the app.
After choosing a different PIN, the app presents credentials created under the old profile and let's the attacker present them as valid.
Other issues:
1. Rate limiting is an incrementing number in the same config file. Just reset it to 0 and keep trying.
2. "UseBiometricAuth" is a boolean, also in the same file. Set it to false and it just skips that step.
Seriously @vonderleyen - this product will be the catalyst for an enormous breach at some point. It's just a matter of time.
“If I put $100 in Bitcoin in 2010 I’d have $2.8B now.”
No.
If you bought $100 of Bitcoin in 2010 and watched it go to:
$1k → $100k → $1.7M
and did nothing
Then watched $1.7M go to $170k
and still did nothing
Then watched $170k go to $110M
and still did nothing
Then watched $110M wither to $18M
and still did nothing
Then watched $18M surge to $390M
and still did nothing
Then watched $390M deteriorate to $85M
Then watched $85M climb to $1.6B
and still did nothing
Then watched $1.6B shrink to $390M
and still did nothing
Then watched $390M surge to $2.8B
and then for some reason finally decided to do something…
Then yes, $100 in 2010 would be worth $2.8B today.