Notices tagged with security, page 10
-
!security #php5 my improved #ctracker version does now also log and block (mostly) unwanted request methods such as CONNECT. This one for example can be (ab-)used for sending bulk mails out and wasting your bandwidth for their spam.
-
Oh boy. When a Certificate Authority acquires a MITM SSL spoofer, HTTPS becomes pretty useless http://www.theregister.co.uk/2016/06/14/symantec_blue_coat_analysis/ !security
-
Homebrew tells users to curl to bash without HTTPS. Complains on browser plugin changing to HTTPS... !security http://qttr.at/1ff7
-
@ghostdancer also really interesting: https://www.oreilly.com/learning/injecting-security-into-continuous-delivery cc !security
-
!security should read about my easy success with the SCR331 smartcard reader: https://social.umeahackerspace.se/notice/598483
-
♻ @thegrugq !Tor hidden services are mostly deanonymised by configuration errors, not breaks in Tor or encryption. OpSec isn’t about tech ¶ via #Twitter !security
-
Qubes !Security Bulletin #24 (for a critical bug in Xen) #QubesOS https://github.com/QubesOS/qubes-secpack/blob/master/QSBs/qsb-024-2016.txt
-
^- !security
-
Announcing updated requirements for Qubes-certified hardware: #QubesOS !security !privacy http://qttr.at/1etb
-
Fix your server from an old bug dated back to #2001: https://httpoxy.org/ #httpoxy out-going traffic from your server is maybe affected (API calls). cc !security
-
UofW Centre for Applied Cryptographic Research is having a seminar on "Security analysis of Brazilian voting machines" with @dfaranha https://calendar.google.com/calendar/event?eid=ZWQwMm9odjRuNzB2anRwOWp2YWZiaW45MnMgbmxrYzM5anQ0cDBuYmM0cGs5cGo3cDVmaDBAZw&ctz=America/New_York !Crypto !Security !ElectoralReform
-
@kevie Have you tried a phone with @CopperheadOS? Designed for !security! https://copperhead.co/blog/ #TuxJam
-
@lnxw48 @lanodan_frndk +1 for password databases. I want @KWLUG to have a night of PW DB comparisons !security
-
@lanodan_frndk @bobjonkman Using longer passwords also serves a second purpose: I know I cannot remember them, so I must always use a password database for generation, storage, and entering passwords, which greatly improves !security. I've been trying to convince family members to likewise use the longest-possible randomly-generated passwords for exactly that reason.
-
@lanodan_frndk @bobjonkman It is difficult for users to know whether a particular service uses a bad hashing algorithm. Also difficult to know whether the service uses a poor implementation of a better algorithm. !security.
-
72 character passwords! I thought I was doing well at 25 characters! !security
-
Now that the sn.jonkman.ca instance is back, the following !Fedgroups hosted here should be back too: !crypto !database !electoralreform !fdroid !food !fs !gnewsense !gnupg !googlefree !grap !hug !kwlug !lazyweb !mint !opendata !openhardware !osm !owncloud !replicant !scifi !security !sriracha !wasabi !sfd !ubuntu !ubuntuca !selfhost !sysadmin !weather !trisquel Welcome back, everybody!
-
I think @ln5 was on there if I'm not mistaken. !security #tor
-
Now that the sn.jonkman.ca instance is back, the following !Fedgroups hosted here should be back too: !crypto !database !electoralreform !fdroid !food !fs !gnewsense !gnupg !googlefree !grap !hug !kwlug !lazyweb !mint !opendata !openhardware !osm !owncloud !replicant !scifi !security !sriracha !wasabi !sfd !ubuntu !ubuntuca !selfhost !sysadmin !weather !trisquel Welcome back, everybody!
-
!security Hm, I thought employed e2e encryption? While I guess it might still be bad and made up on their own, I at least assumed cleartext wasn't available on the server! http://www.dailydot.com/politics/telegram-isis-encryption-cryptography/
(not that I've been using the centralised pile of crap anyway, but I just yesterday said I believe Telegram uses e2e comms)
Roland Häder
Former Bob Jonkman -- Please use the new server at https://gs.jonkman.ca
Markus Kilås
MMN-o ✅⃠
lnxw48 (Linux Walt)
All Hacker Poesy content and data are available under the