Today, Oplane is public.
Continuous threat modeling, live with your codebase. Every change modeled the moment it lands.
A thread on why I built it, after years on the security side of the wall:
@StackOverflow Is there any plan to rethink that reputation leagues only list the top 400 users? An idea is to rank everyone that is in the top 1% or that has gained 1000 reputation instead of the old 200. A lot of users don't think this is a small change
https://t.co/xzK8tahgpf
Last chance for #cybersecurity startups at #RSAC! 7yrs building Security Journey, now sharing insights & advice w/ founders. DM to chat 🗓️ Appreciate RTs to boost this opp. 🔄 #CyberStartupWisdom#AppSecStartups
I'm trying to send an email using SMTP AUTH with XOAUTH2 SASL. Accessing via Azure AD Service Principal with client credentials grant. I get this error: 535: 5.7.3 Authentication unsuccessful accessing https://t.co/6t8nE5eCg4. Full example:
https://t.co/XqUQTNmH7Z
@MicrosoftHelps
@dakire@Bindertech Absolutely, but you can branch from a tag as well. However if you do have continues improvement on release 2.3 I surely see why you would have a branch for it. I would probably name it as your link with "2-3-stable" and then tag every release we sent out.
https://t.co/lAck1W0XWX
@dakire@Bindertech Nice but I would look into tags as well/instead. Given your solution release 2.3 could run on two different code bases. Using a tag instead means a shipped versions code doesn't change and you could then add tag 2.3.1, 2.3.2 etc. for hotfixes.
https://t.co/5ucQ4XmfgO
@Bindertech@dakire Looks good! My general preference is GitHub flow for projects where deployments are made regularly and Gitflow for more scheduled release cycles. Faster onboarding when you follow a set standard would be my only comment. :)
https://t.co/dutn2xHSXn
https://t.co/fbouyFvoe6
@VisualStudio Thanks! Yes the problem is located but neither I nor the community has found a good solution yet so it would be perfect if someone on your side could have a look as well.
Hello @Facebook,
Page "it looks like your account was sending out spam. We would like to help you secure your account" leads to "Sorry, something went wrong"- page and response code is HTTP 500. Is this being looked at? Further details here:
https://t.co/lRPJOYmlA4