API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jun 1st, 2016
939
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 24.23 KB | None | 0 0
raw download clone embed print report
  1. bsides calgary / yyc drama - enjoy
  2.  
  3.  
  4.  
  5. email threads
  6.  
  7. -------------
  8.  
  9. Hi Jay,
  10.  
  11.  
  12.  
  13. What is this about? We will be using twitter and Gmail for for bsides communications . That is the direction from the security bsides management.
  14.  
  15.  
  16.  
  17. Please revoke the invites and I'll be sending out info for the twitter and Gmail shortly.
  18.  
  19.  
  20.  
  21. Regards,
  22.  
  23.  
  24.  
  25. Steve Porter, CISSP, QSA, GPEN, GWAPT, GMOB, GICSP
  26.  
  27. President
  28.  
  29. Secured Net Solutions Inc.
  30.  
  31. P: (403) 714-1801
  32.  
  33.  
  34.  
  35. ---
  36.  
  37.  
  38.  
  39. Jay,
  40.  
  41.  
  42.  
  43. I don’t have the time nor desire to respond to your poor attempt at trying to apologize and this will be the last email that you receive from me. The group has decided that we are sticking with the original planning team that was put together and that extra people will not help at this time.
  44.  
  45.  
  46.  
  47. Regarding the credentials that you have (that should have been sent to BSides team) you can securely send them to us using the link below or continue to hold them. It doesn’t matter, we have created new accounts to use and will not be held hostage by somebody attempting to force the team to use a specific tool because that one person wants to use it.
  48.  
  49.  
  50.  
  51. https://transfer.securednet.ca/filedrop/sporter
  52.  
  53.  
  54.  
  55. Perhaps one day you will understand what it means to be part of a team and how teams work, until then, good luck to you.
  56.  
  57.  
  58.  
  59. Regards,
  60.  
  61.  
  62.  
  63. Steve Porter, CISSP, QSA, GPEN, GWAPT, GMOB, GICSP
  64.  
  65. President
  66.  
  67. Secured Net Solutions Inc.
  68.  
  69. 4th Floor, 909 17 Ave SW
  70.  
  71. Calgary, AB T2T 0A4
  72.  
  73. P: (403) 714-1801
  74.  
  75. E: sporter@securednet.ca
  76.  
  77.  
  78.  
  79. Secure File Drop (Direct): https://transfer.securednet.ca/filedrop/sporter
  80.  
  81. Secure File Drop (PCI): https://transfer.securednet.ca/filedrop/pci
  82.  
  83.  
  84.  
  85. From: Jay Heidecker [mailto:jheidecker@seekintoo.com]
  86.  
  87. Sent: Thursday, November 12, 2015 3:31 PM
  88.  
  89. To: Steve Porter <SPorter@securednet.ca>
  90.  
  91. Subject: RE: BSides Update
  92.  
  93.  
  94.  
  95. Steve,
  96.  
  97.  
  98.  
  99. I’m sorry you’ve become so upset with me. In retrospect, I should not have been so rash. I contemplated calling you back after you hung up on me to explain further, but I reasoned that you were uninterested in discussing it further. Hopefully, email will be better received.
  100.  
  101.  
  102.  
  103. Putting myself in your position, I understand how you might perceive me as attempting to usurp your position as lead organizer of this conference. Pointedly: that’s just not true. If it were, I would have simply said so. After your explaining the planning committed, I became instantly and perhaps overly concerned with is a serious lack of representation from the on-set.
  104.  
  105.  
  106.  
  107. You can’t declare yourself leader of a planning committee for a community event, and not reach out to the broader community first. What did you think was going to happen? Notwithstanding that, you can’t simply deny members of that community from using a <any> tool just because you don’t like them, or it. To disguise this behind noble intentions is as passive aggressive as it gets. Very unbecoming.
  108.  
  109.  
  110.  
  111. I remain deeply concerned that BSides will NOT be representative of Calgary’s InfoSec community if you proceed without my involvement, however, I can’t stand by and let you drag my reputation through the mud over such a silly thing. I have far more to lose than you have to gain by continuing such a dispute.
  112.  
  113.  
  114.  
  115. Call me for the twitter password, and we can also exchange domain registrar details. Let’s get the process started of making sure you are happily in control of whatever you want, so that this conference stands a chance. I’ll make sure everyone on slack knows how subversive and unofficial it is, and to contact you directly if they want to help out.
  116.  
  117.  
  118.  
  119. Unfortunately, I suspect your attitude will be “he brought this on himself,” and that’s to be expected, but that is, by definition, victim shaming. Know that I never have, and never will speak of you or your company in a negative light. I wish we could have worked together or mediated this properly.
  120.  
  121.  
  122.  
  123. -J
  124.  
  125.  
  126.  
  127. From: Steve Porter [mailto:SPorter@securednet.ca]
  128.  
  129. Sent: Wednesday, November 11, 2015 5:46 PM
  130.  
  131. To: Jay Heidecker <jheidecker@seekintoo.com>; Henri St. Louis <HSTLouis@securednet.ca>; Kenneth Inkster <KInkster@securednet.ca>; Doug Leece <DLeece@securednet.ca>; Kramer, Quinn <qfk@sentinelgrp.ca>; Najo Ifield <nifield@cimation.com>; dallas.young@imperativesecurity.com; jude.naidoo@scalar.ca; jay.heidecker@gmail.com; Mcprimeau@gmail.com; Paul Brodeur <paul.brodeur@gmail.com>; altercation@gmail.com
  132.  
  133. Subject: Re: BSides Update
  134.  
  135.  
  136.  
  137. Hi Jay,
  138.  
  139.  
  140.  
  141. I appreciate your eagerness and wanting to help, but if everybody on this list went out and starting doing stuff for BSides then we still wouldn't be any further ahead because everybody would be working on their own conference.
  142.  
  143.  
  144.  
  145. To put together any event, there always has to be a lead person who is ensuring that everybody involved is informed and to make sure that we aren't duplicating efforts. Collaboration tools shouldn't be necessary for a small group of volunteers. Regarding rounding up sponsors, we already have a large list of companies, partners and vendors who are wanting to sponsor, so we have no shortage there.
  146.  
  147.  
  148.  
  149. The SecurityBsides committee has also requested that any accounts created for this conference be done by me and that all credentials will be passed over to the next organizer (should I not want to lead again or don't have the time to continue). This has been a problem in the past with other BSides events and going forward, I don't want it to be an issue in Calgary.
  150.  
  151.  
  152.  
  153. As I said in my previous email, the venue is THE single most important thing that we need to sort out right now. We have a number of good leads and I hope to have a list of options to put out to everybody by next Monday. After the venue has been secured then we can start working on sponsors, CFP, contests, etc.
  154.  
  155.  
  156.  
  157. Going forward, any actions taken on behalf of BSides Calgary must be reviewed and approved by the planning committee first.
  158.  
  159.  
  160.  
  161. Besides, are we really practicing what we preach by using platforms that were recently hacked?
  162.  
  163. http://venturebeat.com/2015/03/27/slack-launches-two-factor-authentication-and-reveals-it-was-hacked-last-month/
  164.  
  165. http://techcrunch.com/2015/03/27/slack-got-hacked/#.pxfvqbu:VkGB
  166.  
  167. http://www.makeuseof.com/tag/slack-hack-need-know-collaboration-tool-security-breach/
  168.  
  169.  
  170.  
  171. Regards,
  172.  
  173.  
  174.  
  175. Steve Porter, CISSP, QSA, GPEN, GWAPT, GMOB
  176.  
  177. President
  178.  
  179. Secured Net Solutions Inc.
  180.  
  181. 4th Floor, 909 17 Ave SW
  182.  
  183. Calgary, AB T2T 0A4
  184.  
  185. P: (403) 714-1801
  186.  
  187. E: sporter@securednet.ca
  188.  
  189.  
  190.  
  191. Secure File Drop: https://transfer.securednet.ca/filedrop/sporter
  192.  
  193.  
  194.  
  195. ________________________________________
  196.  
  197. From: Jay Heidecker <jheidecker@seekintoo.com>
  198.  
  199. Sent: Wednesday, November 11, 2015 4:50 PM
  200.  
  201. To: Steve Porter; Henri St. Louis; Kenneth Inkster; Doug Leece; Kramer, Quinn; Najo Ifield; dallas.young@imperativesecurity.com; jude.naidoo@scalar.ca; jay.heidecker@gmail.com; Mcprimeau@gmail.com; Paul Brodeur; altercation@gmail.com
  202.  
  203. Subject: RE: BSides Update
  204.  
  205.  
  206.  
  207. Steve,
  208.  
  209.  
  210.  
  211. Thanks so much for taking initiative on this! I’ve talked to Jeremy K, Chris T, and Alex D. in the past about making this happen, but nothing has ever materialized. Like you said last Thursday, life gets in the way! I am happy to help in any way possible, and to kick things off I registered a Slack collaboration space for us and invited everyone who was at the meeting, as well as a few others who have expressed interest being involved in either the organization, or selection process. If someone else can host a better collaboration platform, that’s great! Slack is just the most well endorsed. As far as I know, the “security bsides wiki” is mostly for posting event details to the greater public, and (IMHO) using e-mail for consensus gathering might not be fast enough for the timeline we’ve proposed. As a bonus, I have also asked Slack-actual about sponsorship opportunities, even if it means a paid-tier setup, or access to paid integrations (i.e. tools that might help round up sponsors!)
  212.  
  213.  
  214.  
  215. As far as venue goes: Matt is currently looking at the Danish Canadian club, and I know that Dallas has said he is looking into Dickens pub.
  216.  
  217.  
  218.  
  219. Looking forward to the next meetup.
  220.  
  221.  
  222.  
  223. Thanks,
  224.  
  225.  
  226.  
  227. -J
  228.  
  229.  
  230.  
  231.  
  232.  
  233. From: Steve Porter [mailto:SPorter@securednet.ca]
  234.  
  235. Sent: Monday, November 9, 2015 6:47 PM
  236.  
  237. To: Henri St. Louis <HSTLouis@securednet.ca>; Kenneth Inkster <KInkster@securednet.ca>; Doug Leece <DLeece@securednet.ca>; Primeau, Michael <Michael.Primeau@encana.com>; Kramer, Quinn <qfk@sentinelgrp.ca>; Najo Ifield <nifield@cimation.com>; dallas.young@imperativesecurity.com; jude.naidoo@scalar.ca; jay.heidecker@gmail.com
  238.  
  239. Subject: BSides Update
  240.  
  241.  
  242.  
  243. Hi everyone,
  244.  
  245.  
  246.  
  247. First, I'd like to thank everybody from coming out last week even though it wasn't the best of venues to discuss the conference due to the noise levels (my bad there). We'll fix that before the next meeting and line up a boardroom for next meeting.
  248.  
  249.  
  250.  
  251. While I didn't have a lot of time to speak with everybody last week, a few of us did have a great chance to speak with Jack Daniel and gather a lot of information about what does and doesn't work when trying to organize a BSides conference.
  252.  
  253.  
  254.  
  255. One of the things that needs to be agreed upon is that any actions taken on behalf of BSides Calgary must be centralized and agreed upon by the entire group. I am working on getting the credentials for the old Twitter and Gmail accounts that were created by Jeremy a few years ago. If I do not have the creds within the week then it's been advised by the Security BSides committee to start new accounts. In addition to these 2 accounts, a Wiki page needs to be maintained (mandatory) and a website can be created if we choose to do so.
  256.  
  257.  
  258.  
  259. The current task at hand is to secure a venue. A couple of ideas that came up include;
  260.  
  261. - Ken suggested looking into Fort Calgary and it looks like we can book the Original 1875 Fort (yellow zone on map) @ $3750.00 for a 2 day event.
  262.  
  263. - I've also submitted a request for more info and pricing from the BMO centre.
  264.  
  265. - Dallas and/or Jay were going to look into pricing for the Danish Cultural Center and Mike was following up with Mount Royal and another one that I forgot now.
  266.  
  267.  
  268.  
  269. Let's try to have a list of possible venues and pricing for at least 3 or 4 options by midweek so that we can put it t a vote and hopefully have a decision by the end of the week. After that then we can start pushing for sponsors, speakers and events.
  270.  
  271.  
  272.  
  273. Feedback is always welcome and please reply to all so that everybody stays informed and can provide feedback throughout the entire process.
  274.  
  275.  
  276.  
  277. Regards,
  278.  
  279.  
  280.  
  281. Steve Porter, CISSP, QSA, GPEN, GWAPT, GMOB, GCIH, GICSP
  282.  
  283. President
  284.  
  285. Secured Net Solutions Inc.
  286.  
  287. 4th Floor, 909 17 Ave SW
  288.  
  289. Calgary, AB T2T 0A4
  290.  
  291. P: (403) 714-1801
  292.  
  293. E: sporter@securednet.ca
  294.  
  295.  
  296.  
  297. Secure File Drop: https://transfer.securednet.ca/filedrop/sporter
  298.  
  299.  
  300.  
  301. This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the original sender of this email.
  302.  
  303. This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the original sender of this email.
  304.  
  305. This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the original sender of this email.
  306.  
  307.  
  308.  
  309.  
  310.  
  311. ---
  312.  
  313.  
  314.  
  315. Jay,
  316.  
  317. Thank you. FYI I reached out the original person a few times before handing it over to Steve. He was made to wait several weeks and after no response, he was given the green light.
  318.  
  319. Thank you,
  320.  
  321. Michelle Klinger
  322.  
  323. Sent from mobile device
  324.  
  325. On Dec 28, 2015 7:40 PM, "Jay Heidecker" <jheidecker@seekintoo.com> wrote:
  326.  
  327. Steve,
  328.  
  329.  
  330.  
  331. Your last email, in full:
  332.  
  333.  
  334.  
  335. Jay,
  336.  
  337.  
  338.  
  339. I don’t have the time nor desire to respond to your poor attempt at trying to apologize and this will be the last email that you receive from me. The group has decided that we are sticking with the original planning team that was put together and that extra people will not help at this time.
  340.  
  341.  
  342.  
  343. Regarding the credentials that you have (that should have been sent to BSides team) you can securely send them to us using the link below or continue to hold them. It doesn’t matter, we have created new accounts to use and will not be held hostage by somebody attempting to force the team to use a specific tool because that one person wants to use it.
  344.  
  345.  
  346.  
  347. https://transfer.securednet.ca/filedrop/sporter
  348.  
  349.  
  350.  
  351. Perhaps one day you will understand what it means to be part of a team and how teams work, until then, good luck to you.
  352.  
  353.  
  354.  
  355. The credentials were sent to me because there was already a planning committee of around 10 people struck up over two years ago, and while it is unfortunate you were never included in that group, there were ongoing talks of the event as recently as this summer. I was asked to come to the kick off meeting by one of the people you invited because it struck them as odd so many were left out, so no more talk about Cowboys, OK? We attended the kick off session asking to be involved and you paid some nice lip service to that, and then immediately ostracized us when we started a Slack channel to help collaborate planning online. There were half a dozen people waiting for you to join, by the way. Only one of the original BSides Calgary planners was ever notified (not asked mind you,) that you would be taking over planning of this event. In conclusion, go fuck yourself.
  356.  
  357.  
  358.  
  359. You’ve created your new accounts like you said, and I will delete all of the stuff I am currently administering , as requested.
  360.  
  361.  
  362.  
  363. I hope you have a great conference. I will reach out to you later so that we can sponsor the event, but I get the feeling your sponsorship committee might not approve.
  364.  
  365.  
  366.  
  367. -J
  368.  
  369.  
  370.  
  371.  
  372.  
  373. From: Steve Porter [mailto:SPorter@securednet.ca]
  374.  
  375. Sent: Monday, December 28, 2015 4:06 PM
  376.  
  377. To: Michelle KL <securityindepth@gmail.com>; Jay Heidecker <jheidecker@seekintoo.com>
  378.  
  379. Cc: David Mortman <mortman@gmail.com>; Mike Dahn <mikedahnsf@gmail.com>; Jack Daniel <jackadaniel@gmail.com>; Galactica Actual <info@bsidesyyc.com>
  380.  
  381. Subject: RE: BSides Calgary
  382.  
  383.  
  384.  
  385. Hello Michelle,
  386.  
  387.  
  388.  
  389. Thank you for your email and for trying to move things along here. Regarding the last communication that I had with Jay, I had asked him to send the credentials for the accounts that he held in a secure manner (using a secure portal that our company uses) but he chose not to do this.
  390.  
  391.  
  392.  
  393. Here is the link that allows for secure communications, as provided to Jay before;
  394.  
  395. https://transfer.securednet.ca/filedrop/sporter
  396.  
  397.  
  398.  
  399. As for including the local community; as I mentioned in a previous email, the current planning group is not excluding anybody from participating, attending, speaking or sponsoring the event. That would definitely go against the spirit and goals of a BSides event.
  400.  
  401.  
  402.  
  403. We have a good core planning team that is very well connected to the infosec community in Calgary and surrounding areas. What we do not require at this time is people who do not know how to be part of a team and act as cowboys doing what they want without agreement or consensus from the planning team. This approach completely goes against the idea of having a team/group to coordinate the event.
  404.  
  405.  
  406.  
  407. Regards,
  408.  
  409.  
  410.  
  411. Steve Porter, CISSP, QSA, GPEN, GWAPT, GMOB, GICSP
  412.  
  413. President
  414.  
  415. Secured Net Solutions Inc.
  416.  
  417. 4th Floor, 909 17 Ave SW
  418.  
  419. Calgary, AB T2T 0A4
  420.  
  421. P: (403) 714-1801
  422.  
  423. E: sporter@securednet.ca
  424.  
  425.  
  426.  
  427. Secure File Drop (Direct): https://transfer.securednet.ca/filedrop/sporter
  428.  
  429. Secure File Drop (PCI): https://transfer.securednet.ca/filedrop/pci
  430.  
  431.  
  432.  
  433. From: Michelle KL [mailto:securityindepth@gmail.com]
  434.  
  435. Sent: Monday, December 28, 2015 3:55 PM
  436.  
  437. To: Jay Heidecker <jheidecker@seekintoo.com>
  438.  
  439. Cc: Steve Porter <SPorter@securednet.ca>; David Mortman <mortman@gmail.com>; Mike Dahn <mikedahnsf@gmail.com>; Jack Daniel <jackadaniel@gmail.com>; Galactica Actual <info@bsidesyyc.com>
  440.  
  441. Subject: RE: BSides Calgary
  442.  
  443.  
  444.  
  445. OK here is what's going to happen... Don't wait for the other person to reach out to you. Write an email right now to open up the communication. This dialog will be an attempt to call a truce and hand over account access to Steve. They've been given the right to hold the event prior to your planning activities. It's unfortunate but one of the rules even before planning an event is to reach out to the mothership first.
  446.  
  447. This isn't the first time a local community felt slighted for not being involved in the planning. Is it a requirement? No. Is it a good idea? Yes. So this is now the time to make it happen. That other event got fractured and did not act in ways we hope BSides coordinators representing the BSides brand should behave. So let's set egos aside from both sides and think of the community. Otherwise we will cut this baby in half, hand the bleeding halves back and use this event as an example of how not to throw an event when I talk with first time event coordinators.
  448.  
  449. Thank you,
  450.  
  451. Michelle Klinger
  452.  
  453. Sent from mobile device
  454.  
  455. On Dec 28, 2015 3:49 PM, "Jay Heidecker" <jheidecker@seekintoo.com> wrote:
  456.  
  457. Jack,
  458.  
  459.  
  460.  
  461. I'm not sure where the "escalation" has arisen? Steve's last communication with me was that he would never speak to, or e-mail me again, despite a plea to work together. Instead of beating that dead horse, I reckoned faithful and positive promotion of the event to a common goal would be the next best thing vs. working directly together. The alternative is to fracture the community by striking up a new con, which is not an issue, just a shame, since I expected more from BSides. I guess mediation, to you, means immediate C&D. My apologies that it has come to this as well. Even though I put forward my best effort to do the right thing, I was apparently very mistaken. No hard feelings. I don’t think Steve will reach out for the passwords (since I already offered that) to the accounts, and I see what looks like another domain is registered. Do you suggest I simply shutter the twitter account and google apps?
  462.  
  463.  
  464.  
  465. -J
  466.  
  467.  
  468.  
  469.  
  470.  
  471. -----Original Message-----
  472.  
  473. From: Jack Daniel [mailto:jackadaniel@gmail.com]
  474.  
  475. Sent: Monday, December 28, 2015 12:18 PM
  476.  
  477. To: Jay Heidecker <jheidecker@seekintoo.com>; Galactica Actual <info@bsidesyyc.com>
  478.  
  479. Cc: Steve Porter <SPorter@securednet.ca>; Mike Dahn <mikedahnsf@gmail.com>; Michelle KL <securityindepth@gmail.com>; David M <mortman@gmail.com>
  480.  
  481. Subject: BSides Calgary
  482.  
  483.  
  484.  
  485. I'm sorry it has escalated to this.
  486.  
  487.  
  488.  
  489. Jay, please immediately cease impersonating the authorized BSides organizer, and immediately cease using any Security BSides artwork, marks, or other trademarks.
  490.  
  491.  
  492.  
  493. Steve and his team hold the valid event and trademark agreement, you do not.
  494.  
  495.  
  496.  
  497. Please don't escalate this further, BSides is a brand build by thousands and this kind of action damages all of their hard work.
  498.  
  499. Further, BSides can't afford legal defense of our trademarks, but we'll find the money if we have to- we are required to protect our trademarks from misuse.
  500.  
  501.  
  502.  
  503.  
  504.  
  505. ______________________________________
  506.  
  507. Jack Daniel,
  508.  
  509. Co-founder, Director
  510.  
  511. Security BSides, securitybsides.org
  512.  
  513. This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the original sender of this email.
  514.  
  515.  
  516.  
  517. ---
  518.  
  519.  
  520.  
  521. Hi again,
  522.  
  523.  
  524.  
  525. No problems here. Input and feedback is always welcome via info@bsidescalgary.org and @BSides_Calgary.
  526.  
  527.  
  528.  
  529. As for using SecuredNet’s portal to send the credentials, I only suggested it as a onetime use between Jay and I. It is not being promoted as a means of communication for the event and I won’t suggest it going forward. Instead, I’ve setup a dropbox account where the credentials can be placed for easy access by the team.
  530.  
  531.  
  532.  
  533. BSides Calgary Dropbox: https://www.dropbox.com/request/7It1vEYv1vcumRw2V4Md
  534.  
  535.  
  536.  
  537. Regards,
  538.  
  539.  
  540.  
  541. Steve Porter, CISSP, QSA, GPEN, GWAPT, GMOB, GICSP
  542.  
  543. President
  544.  
  545. Secured Net Solutions Inc.
  546.  
  547. 4th Floor, 909 17 Ave SW
  548.  
  549. Calgary, AB T2T 0A4
  550.  
  551. P: (403) 714-1801
  552.  
  553. E: sporter@securednet.ca
  554.  
  555.  
  556.  
  557. Secure File Drop (Direct): https://transfer.securednet.ca/filedrop/sporter
  558.  
  559. Secure File Drop (PCI): https://transfer.securednet.ca/filedrop/pci
  560.  
  561.  
  562.  
  563. From: Michelle KL [mailto:securityindepth@gmail.com]
  564.  
  565. Sent: Monday, December 28, 2015 4:15 PM
  566.  
  567. To: Steve Porter <SPorter@securednet.ca>
  568.  
  569. Cc: Michael Dahn <mikedahnsf@gmail.com>; David Mortman <mortman@gmail.com>; Jack Daniel <jackadaniel@gmail.com>; Jay Heidecker <jheidecker@seekintoo.com>; Galactica Actual <info@bsidesyyc.com>
  570.  
  571. Subject: RE: BSides Calgary
  572.  
  573.  
  574.  
  575. We get it. No need to rehash who didn't or won't do what. We are past that. I'm also not asking for people to be added to the team but it would do well to have a conversation and get any feedback or input or even hear their concerns. THAT is the BSides way.
  576.  
  577. So, I look forward to seeing an email from Jay on how to move forward with credential hand over. Also I recommend avoid using anything affiliated with your employer for the event. It make us uneasy and we don't want to start with bad perception.
  578.  
  579. Thanks. Again I don't want explanations and excuses. Just get it done.
  580.  
  581. Thank you,
  582.  
  583. Michelle Klinger
  584.  
  585. Sent from mobile device
  586.  
  587.  
  588.  
  589.  
  590.  
  591. some slack convos
  592.  
  593. -----------------
  594.  
  595.  
  596.  
  597. [7:10] Also, I got a message on linkedin from Steve Porter asking for these credentials
  598.  
  599.  
  600.  
  601. ​[7:12]
  602.  
  603. I don't know him from adam, so figured I've give them to you instead
  604.  
  605.  
  606.  
  607. ​[7:13]
  608.  
  609. he also claims I had a gmail account, which I'm not sure of - I had registered bsidesyyc.com and had it hooked up to google apps, but I let that lapse.
  610.  
  611.  
  612.  
  613. [3:33 PM]
  614.  
  615. who is steve?
  616.  
  617.  
  618.  
  619. [3:33 PM]
  620.  
  621. the "sanctioned" and singular BSides Calgary organizer.
  622.  
  623.  
  624.  
  625. [3:34 PM]
  626.  
  627. sanctioned by who? lol ...
  628.  
  629.  
  630.  
  631. [3:43 PM]
  632.  
  633. what has he done to build the conference? cause until I heard from you, I hadn't heard anything since the last calsec I attended. So maybe if things aren't moving forward, he's part of the problem, not the solution. I could be wrong as I haven't hard but I wouldn't take it like you fucked up anything J.
  634.  
  635.  
  636.  
  637. [4:10 PM]
  638.  
  639. Bsidesyyc: a fireside chat about security policies and the newest requirements of PCI DSS
  640.  
  641.  
  642.  
  643.  
  644.  
  645. [1:23 PM]
  646.  
  647. I just spent the last hour reaching out to people I know to submit talks
  648.  
  649.  
  650.  
  651. ​[1:23]
  652.  
  653. people who could probably bring really great content
  654.  
  655.  
  656.  
  657. [1:24 PM]
  658.  
  659. well it's not like they can't.. i was not going to mediate submissions, just get community feedback and forward to Steve
  660.  
  661.  
  662.  
  663. [1:25 PM]
  664.  
  665. no.. but this guy’s attitude makes me want to retract all of that
  666.  
  667.  
  668.  
  669. ​[1:25]
  670.  
  671. I lean more to avoiding the event than participating at this rate
  672.  
  673.  
  674.  
  675. [4:49 PM]
  676.  
  677. anyway i took the high road and peaced out..
  678.  
  679.  
  680.  
  681. ​[4:50]
  682.  
  683. you can still use the form or send email direct, doesn't matter
  684.  
  685.  
  686.  
  687. ​[4:51]
  688.  
  689. fuck bsides.. a buddy of mine who was invoved in bsides vegas for several years reached out and said it wasn't worth it
  690.  
  691.  
  692.  
  693. ​[4:51]
  694.  
  695. after seeing that jack daniel was giving me shit
  696.  
  697.  
  698.  
  699. ​[4:51]
  700.  
  701. :simple_smile:
  702.  
  703.  
  704.  
  705. ​[4:54]
  706.  
  707. apparently a lot of them thrive on 90210-like drama so mabye this will even help with publicity
  708.  
  709.  
  710.  
  711. ​[4:54]
  712.  
  713. although i still want to boycott it because of this steve guy
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!