Search
Items tagged with: cloud
Black Weeks at @Tutanota Save 62% On Our Legend Plan! 💎 tuta.com/blog/black-weeks-at-t…
#Encrypt #privacy #BlackFriday #Email #Calendar #FLOSS #OSS #OpenSource
Not endorsing the #degoogle hashtag here just because a hell of a lot of spackle is needed for a comparable experience, but if you're interested in #cloud email servoces, this is one of the better ones in this space.
Black Weeks at Tuta: Save 62% On Our Legend Plan! 💎 | Tuta
Get the deal from November 15 to December 4, 2024.Tuta
Vercel v dubnu updatoval ceniky. Misto tradicniho pomaleho utahovani sroubu to fakt napalil a zavedl "Edge Requests", za timto kryptickym popiskem se skryva jakykoli request. (cti: assety)
V EU za to platime $2.60/1M requestu.
Zjistil jsem to, kdyz nam Volebni Kalkulacka vesele napocitava 5.6M Edge Requestu za den. Jeste, ze nejsou prezidentske volby a senatori dodali odpovedi tak pozde!
Cas z Vercelu odejit.
Pro predstavu porovnani jednoho dne senatu a prezidenta.
This morning, I took my wife to the hospital for routine blood tests that had been scheduled for some time. Everything was going smoothly: check-in, number, waiting room. Suddenly, everything came to a halt and shut down. I was connected to the hospital’s public Wi-Fi and noticed that my connection also went down.
Having managed a couple of similar facilities, I immediately understood what had happened. I saw the staff panicking and calling the technicians, but they quickly reorganized within 10 minutes. They managed to process everyone who already had a number and then proceeded with the others in the order of their arrival. Despite the ten-minute delay (even though people started complaining right away), they were extremely efficient.
I later confirmed that the entire booking, check-in, and queue system is “in the cloud.” The hospital experienced a connectivity interruption, and all related services stopped. The staff no longer had access to anything, so a technician sent the lists to a manager via another channel, and everything resumed manually.
For years, I’ve insisted that certain things MUST be local. The healthcare facilities I manage have all the necessary systems for the operation of the facility internally, including patient records. External services like websites, emails, etc., are secondary.
Everything essential must always be accessible locally and, in special cases, it should be possible to physically access the servers and connect directly to them, bypassing any network/switch failures.
There has been only one interruption in the past, due to human error. Today, we have redundant servers (not HA on virtualizers, but two machines running the same software with replicated databases - on separate power lines) so such an issue shouldn’t happen anymore.
Not everything can be anticipated, but history is a great teacher. The Internet connection will eventually be interrupted 
When it comes to the health and survival of people, there are no compromises.
#IT #Internet #Networking #Outage #Health #HA #Cloud #CloudComputing #OwnYourData
And I **need** an **accessible** client. Also a reason why I don't go to some provider who hosts nextcloud for me, the client is not 100% accessible, and I don't like this.
Would appriciate your recommendations.
I really like the idea of, instead of collaborating on a document via (for example) Google's servers and Google Docs, being able to have collaborators' computers talk to each other directly and share edits that way.
I really hope that "local-first" gains at least the sort of steam the FOSS movement has — as I've seen people comment, FOSS doesn't help if your computation is happening on someone else's computer.
What on earth?! Amazon S3 charges you for unauthorised requests to S3?!
That's just absolutely insane! I better check my AWS account and delete any unused buckets I have in there …
medium.com/@maciej.pocwierz/ho…
#aws #s3 #infosec #webdev #cloud
How an empty S3 bucket can make your AWS bill explode
Imagine you create an empty, private AWS S3 bucket in a region of your preference. What will your AWS bill be the next morning?Maciej Pocwierz (Medium)
AI App Builder
Build and deploy your custom AI application in minutes with AI App Builder. Choose cutting-edge models, ensure security, and empower developers effortlessly. Register now!OVHcloud
Nextcloud jako osobní cloud
Už 7 let používám Nextcloud pro osobní potřeby. V článku jsem sepsal, na jaké věci jej používám a jaké s nimi mám zkušenosti.
#caldav #carddav #chat #cloud #Collabora #dokumenty #Dropbox #fotky #kalendáře #kontakty #libreoffice #Nextcloud #RSS #úkoly
blog.eischmann.cz/2023/11/16/n…
Wer es immer noch nicht glaubt: eine mit Passwort versehene ZIP Datei darf man nicht als "sicher verschlüsselt" betrachten! Schon gar nicht in der #Microsoft #Cloud
Malware detected: Microsoft-Cloud hebelt ZIP-Passwortschutz aus
tarnkappe.info/artikel/it-sich…
Malware detected: Microsoft-Cloud hebelt ZIP-Passwortschutz aus
Wer glaubt, die Inhalte seiner ZIP-Dateien seien durch ihren Passwortschutz sicher, der irrt. Selbst Microsoft schaut da mittlerweile rein.Marc Stöckel (Tarnkappe.info)
Es ist ja nicht so, dass wir nicht schon länger vom Vendor-Lock-In gewarnt hätten. Nun hat Microsoft ihren Cloud-Kunden am 1. April ganz unironisch ein Preiserhöhung-Ei gelegt.
«EU-Cloud-Wettbewerber: Microsofts Preissteigerungen reichen an Erpressung»
🥚 heise.de/news/EU-Cloud-Wettbew…
--
#microsoft #cloud #vendorlockin #eu #erpressung #IToldYouSo
EU-Cloud-Wettbewerber: Microsofts Preissteigerungen reichen an Erpressung
Zum 1. April hat Microsoft die Preise für Cloud-Produkte um elf Prozent erhöht. Betroffenen und Konkurrenten stößt die Teuerung verstärkt äußerst übel auf.Stefan Krempl (heise online)
Hledám infra experta do banky. Bez kódování, jen vrtání se v systémech.
#infrastructureascode #devops #automation
#cloud #k8s #terraform #ansible
Hybrid #job #Praha, 1x týdně on-site.
Technický pohovor online ihned.
*MD doplním.
Díky,
Honza
I recently wrote a post detailing the recent #LastPass breach from a #password cracker's perspective, and for the most part it was well-received and widely boosted. However, a good number of people questioned why I recommend ditching LastPass and expressed concern with me recommending people jump ship simply because they suffered a breach. Even more are questioning why I recommend #Bitwarden and #1Password, what advantages they hold over LastPass, and why would I dare recommend yet another cloud-based password manager (because obviously the problem is the entire #cloud, not a particular company.)
So, here are my responses to all of these concerns!
Let me start by saying I used to support LastPass. I recommended it for years and defended it publicly in the media. If you search Google for "jeremi gosney" + "lastpass" you'll find hundreds of articles where I've defended and/or pimped LastPass (including in Consumer Reports magazine). I defended it even in the face of vulnerabilities and breaches, because it had superior UX and still seemed like the best option for the masses despite its glaring flaws. And it still has a somewhat special place in my heart, being the password manager that actually turned me on to password managers. It set the bar for what I required from a password manager, and for a while it was unrivaled.
But things change, and in recent years I found myself unable to defend LastPass. I can't recall if there was a particular straw that broke the camel's back, but I do know that I stopped recommending it in 2017 and fully migrated away from it in 2019. Below is an unordered list of the reasons why I lost all faith in LastPass:
- LastPass's claim of "zero knowledge" is a bald-faced lie. They have about as much knowledge as a password manager can possibly get away with. Every time you login to a site, an event is generated and sent to LastPass for the sole purpose of tracking what sites you are logging into. You can disable telemetry, except disabling it doesn't do anything - it still phones home to LastPass every time you authenticate somewhere. Moreover, nearly everything in your LastPass vault is unencrypted. I think most people envision their vault as a sort of encrypted database where the entire file is protected, but no -- with LastPass, your vault is a plaintext file and only a few select fields are encrypted. The only thing that would be worse is if...
- LastPass uses shit #encryption (or "encraption", as @sc00bz calls it). Padding oracle vulnerabilities, use of ECB mode (leaks information about password length and which passwords in the vault are similar/the same. recently switched to unauthenticated CBC, which isn't much better, plus old entries will still be encrypted with ECB mode), vault key uses AES256 but key is derived from only 128 bits of entropy, encryption key leaked through webui, silent KDF downgrade, KDF hash leaked in log files, they even roll their own version of AES - they essentially commit every "crypto 101" sin. All of these are trivial to identify (and fix!) by anyone with even basic familiarity with cryptography, and it's frankly appalling that an alleged security company whose product hinges on cryptography would have such glaring errors. The only thing that would be worse is if...
- LastPass has terrible secrets management. Your vault encryption key always resident in memory and never wiped, and not only that, but the entire vault is decrypted once and stored entirely in memory. If that wasn't enough, the vault recovery key and dOTP are stored on each device in plain text and can be read without root/admin access, rendering the master password rather useless. The only thing that would be worse is if...
- LastPass's browser extensions are garbage. Just pure, unadulterated garbage. Tavis Ormandy went on a hunting spree a few years back and found just about every possible bug -- including credential theft and RCE -- present in LastPass's browser extensions. They also render your browser's sandbox mostly ineffective. Again, for an alleged security company, the sheer amount of high and critical severity bugs was beyond unconscionable. All easy to identify, all easy to fix. Their presence can only be explained by apathy and negligence. The only thing that would be worse is if...
- LastPass's API is also garbage. Server-can-attack-client vulns (server can request encryption key from the client, server can instruct client to inject any javascript it wants on every web page, including code to steal plaintext credentials), JWT issues, HTTP verb confusion, account recovery links can be easily forged, the list goes on. Most of these are possibly low-risk, except in the event that LastPass loses control of its servers. The only thing that would be worse is if...
- LastPass has suffered 7 major #security breaches (malicious actors active on the internal network) in the last 10 years. I don't know what the threshold of "number of major breaches users should tolerate before they lose all faith in the service" is, but surely it's less than 7. So all those "this is only an issue if LastPass loses control of its servers" vulns are actually pretty damn plausible. The only thing that would be worse is if...
- LastPass has a history of ignoring security researchers and vuln reports, and does not participate in the infosec community nor the password cracking community. Vuln reports go unacknowledged and unresolved for months, if not years, if not ever. For a while, they even had an incorrect contact listed for their security team. Bugcrowd fields vulns for them now, and most if not all vuln reports are handled directly by Bugcrowd and not by LastPass. If you try to report a vulnerability to LastPass support, they will pretend they do not understand and will not escalate your ticket to the security team. Now, Tavis Ormandy has praised LastPass for their rapid response to vuln reports, but I have a feeling this is simply because it's Tavis / Project Zero reporting them as this is not the experience that most researchers have had.
You see, I'm not simply recommending that users bail on LastPass because of this latest breach. I'm recommending you run as far way as possible from LastPass due to its long history of incompetence, apathy, and negligence. It's abundantly clear that they do not care about their own security, and much less about your security.
So, why do I recommend Bitwarden and 1Password? It's quite simple:
- I personally know the people who architect 1Password and I can attest that not only are they extremely competent and very talented, but they also actively engage with the password cracking community and have a deep, *deep* desire to do everything in the most correct manner possible. Do they still get some things wrong? Sure. But they strive for continuous improvement and sincerely care about security. Also, their secret key feature ensures that if anyone does obtain a copy of your vault, they simply cannot access it with the master password alone, making it uncrackable.
- Bitwarden is 100% open source. I have not done a thorough code review, but I have taken a fairly long glance at the code and I am mostly pleased with what I've seen. I'm less thrilled about it being written in a garbage collected language and there are some tradeoffs that are made there, but overall Bitwarden is a solid product. I also prefer Bitwarden's UX. I've also considered crowdfunding a formal audit of Bitwarden, much in the way the Open Crypto Audit Project raised the funds to properly audit TrueCrypt. The community would greatly benefit from this.
Is the cloud the problem? No. The vast majority of issues LastPass has had have nothing to do with the fact that it is a cloud-based solution. Further, consider the fact that the threat model for a cloud-based password management solution should *start* with the vault being compromised. In fact, if password management is done correctly, I should be able to host my vault anywhere, even openly downloadable (open S3 bucket, unauthenticated HTTPS, etc.) without concern. I wouldn't do that, of course, but the point is the vault should be just that -- a vault, not a lockbox.
I hope this clarifies things! As always, if you found this useful, please boost for reach and give me a follow for more password insights!
"LfDI expects schools to offer pupils alternatives to the MS365 #cloud service for #school operations by the summer vacations in 2022.
From the coming school year, the use of MS 365 at schools must be terminated or its data protection-compliant operation must be clearly demonstrated by the responsible schools."
This is how the SA of Baden-Württemberg starts its press release stating that M365 is not #GDPR compliant and it must be discontinued.
baden-wuerttemberg.datenschutz…
Nutzung von MS 365 an Schulen - Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit
LfDI erwartet von Schulen, dass sie Schüler_innen bis zu den Sommerferien 2022 Alternativen zum Cloud-Dienst MS 365 für den Schulbetrieb anbietenPressestelle (Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg)
I'd like to find a community of other people in #tech, maybe people who are interested in talking about things like #cloud alternatives, #cryptography, or #softwaredev processes (like #agile, I guess), #programming. I haven't found too much of that on here. Point me at the good discussions and knowledge sharing, if you know where it is!
Look, software isn't everything, and I'm sure I'll get into some other stuff on here, but the above is what I haven't found yet.
#introductions #introduction