![]() |
Team 548 Einstein Statement
Team 548 has released a statement regarding the events on Einstein.
You can read it here, along with FIRST's official response. Please keep this civil! -Nick |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
For additional consideration, from Frank:
Blog Date: Monday, August 20, 2012 - 09:38 Hello Teams, Team 548 contacted me recently and asked if I would be willing to publish a statement from them regarding the events on Einstein on the FRC Blog. You can find their statement here. This statement represents, in part, their Steering Committee’s understanding of events that took place during the Einstein matches. To be clear, there are some differences between this understanding of events and the events as presented in the Einstein Report. FIRST continues to stand by its report. (My emphasis). |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
It gets you thinking, though, doesn't it? Was banning him from ever participating in FIRST again really the right thing to do?
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Unfortunately, creating an interruption is not the way to 'make a point'. Sorry, I'm not giving anyone a pass on this one. You're supposed to listen to staff and volunteers, and this person didn't.
Good on 548 for coming forward, although the major discrepancies between their statement and FIRST's report still leaves questions for me. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
Quote:
|
Re: Team 548 Einstein Statement
I think it's a good thing 548 came out and said this. I very much hope that they stay a respected team in our FIRST community and continue to be successful. In regards to the individual, what's been said has already been said and I don't need to go into that. Great job 548, you guys have done nothing wrong in this process, and have my respect for coming out about it.
|
Re: Team 548 Einstein Statement
There are some major discrepancies present here. While not to start another famous "CD-Massacre" the report and this letter do not match up. I applaud 548 for coming forth with this, it takes a lot of bravery to do that. However, the information they have been given and the conclusions they came to simply don't make sense when you stack them up against the report and individual accounts of that afternoon.
Still, kudos 548 for at least making the statement in the first place. Now we can move on a little more. -Nick |
Re: Team 548 Einstein Statement
Quote:
Because the individual did this only after attempting to interact with the field personnel, I feel his actions were entirely warranted and correct. Of course, this is all predicated on 548's version of events being correct. It seems believable to me, primarily because FIRST was so vague in this area. |
Re: Team 548 Einstein Statement
Quote:
Wow. -Nick |
Re: Team 548 Einstein Statement
Quote:
Before passing judgment on this, I had to ask myself 'Had he been listened to, would things have played out differently?' I'm not sure of the answer, and in turn not sure how I feel. |
Re: Team 548 Einstein Statement
Quote:
PS: ^ look at this Lawrence guy. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
Quote:
Quote:
Okay, before this thread crashes, lets go back to praising 548 for saying "we're sorry." -Nick |
Re: Team 548 Einstein Statement
Quote:
This mentor did not tell his team the full story, in my opinion. And this statement makes him look even worse (to me) because none of the other accusations that many are thinking about are addressed. Maybe he said this was the reasoning and that it only happened on Einstein and was a method of protest to protect team 548's wins last season? Maybe he did this at other events to gain competitive advantage? Those are my beliefs, and I'd like to see this same person address those beliefs. Even if he confirms or denies this, I honestly think more than just the Einstein teams deserve an apology. Yes these are bold statements, but I am perfectly confident that I am not the only one with these beliefs. Kudos to the rest of 548 for releasing this statement. A bit late, but that is understandable. Yes you still have the support of other teams in FIRST (at least mine). |
Re: Team 548 Einstein Statement
548 shouldn't have had to apologize. Regardless of what one individual did, he acted alone and not as a member of the team; whether right or wrong, it wasn't the team's fault.
|
Re: Team 548 Einstein Statement
Quote:
-Nick |
Re: Team 548 Einstein Statement
Quote:
There are any number of things which could have been done after Einstein to fix this issue. Don't fall into the trap of "he spoke up and was ignored so he had to make his point." There are plenty of ways to get "unignored" (later on) without knowingly sabotaging an event. The existence of this vulnerability could have been made known, and fixed, after the fact. Suspecting that someone else is exploiting it, is not a valid reason for exploiting it yourself. Kudos to 548 for coming forward, I expect nothing less from such a well regarded team. Their team leadership stepped forward. They communicated the facts they have, without editorializing. They apologized. -John |
Re: Team 548 Einstein Statement
Quote:
I have a very hard time believing everything in 548's statement just because of this single sentence - "The actions of the individual were not intended to harm a team or alliance, nor intended to alter the outcome of the matches on Einstein." That's exactly what it did. Regardless of the intention, that's what happened. Teams were harmed, match outcomes were effected and the 2012 FRC season was damaged just to prove a point. There's a time and a place for this kind of thing, but not like this. Common sense - use it. |
Re: Team 548 Einstein Statement
I am glad the they came out with this statement but there is way to much mitigating going on and it leaves a bad taste in my mouth.
I am hoping that its just because some lawyers told them to how to say it (after all it is a very litigious world) and not the teams true feelings. |
Re: Team 548 Einstein Statement
Quote:
-Nick |
Re: Team 548 Einstein Statement
This is poorly written and a less than ideal admission of guilt.
Quote:
|
Re: Team 548 Einstein Statement
Quote:
This is the same "rule" that most organizations and companies have. If I were to talk onto a plane wearing a company shirt and start talking about something bad for the company, it reflects on the company. If I happen to encounter one of our customers and start having a discussion about our products, I'm required to file a report about the encounter. In this case, an individual who could be identified as belonging to their team performed actions of which the community disproves. Whether or not the team made a public statement, enough people witnessed the incident to ensure that something would be said and spread via rumor. In such a situation, it would go directly against the team and many people would blame the team. By stepping forward as a team, publicly apologizing, and clearly stating that the individuals actions were not representative of the team, this team is performing the necessary PR to move past the incident. All that said, I personally believe this was the act of an individual, and not something that was sanctioned by the team. I think it really helps to highlight the fact that poor choices can be made by anyone, even a 7-year veteran mentor of a well respected team. I hope this doesn't tarnish the team's reputation in years to come, and I really hope the immediate community they interact with at off season events, districts, and such maintains respect for this team through these difficult times. |
Re: Team 548 Einstein Statement
Quote:
I'm like you - I personally don't use it on principle, and I cringe when I see it, but it's not incorrect per se. I don't know that it's poorly written - like SAM said, it reeks of lawyerspeak - and understandably so. This team has strong ties to its sponsors, as many do, and when people's livelihoods are at stake, you bet the lawyers are called in. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
It takes balls to associate one's team or company with an incident like this. The team wrote and released this statement with the full knowledge that (fair or not) some people might look at them a little differently for a while (it's just human nature...and yes I am aware that a large portion of the FRC community already knew/thought they knew the team anyhow). Hopefully now we can move forward. |
Re: Team 548 Einstein Statement
Without locking down the entire field environment (i.e. banning personal laptops for driver's stations), how could FIRST prevent this type of issue in the future? This is more of an industry-directed question rather than a FIRST-directed question.
|
Re: Team 548 Einstein Statement
Quote:
Furthermore, it took twenty one years for someone to do this. I expect it to take just as long before the next incident. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
I'm going to agree with two of the posts in here just to clarify some points based on experience at one of my jobs (I help teach cyber security and ethics is a huge part of it).
Quote:
Quote:
THIS is the correct process, the person raised the issue at the time. It was not addressed. He should have documented his findings and sent them to FIRST. After giving FIRST a period of time to respond or fix the issue (think 6 months) he could have published a paper documenting his findings. At the end he should have included his original communication with FIRST and any steps they took or responses. As it stands the person went from doing the right thing to being an attacker when they tried to "demonstrate" the vulnerability. |
Re: Team 548 Einstein Statement
Quote:
From an IT/IA perspective, the plans FIRST described in the report are vague at best, yet it's probably best that way. If we openly crowd-sourced amongst our intelligent community engineers to figure out how the FRC system could be vulnerable, then the companies working on securing the field would be better-equipped to understand what 0-day issues need to be addressed. @Alec: I too dislike putting my 6 vacation days, 100's of hours, and several dollars of support at the mercy of GP in such a competitive program. Yet at this point we should contribute to the solution rather than further highlighting the problem. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Kudos to 548 for coming out and releasing a statement. I still love your team! ;)
Let's not rehash all of this again guys as we still don't know what happened. 548's report differs from FIRST's report but that doesn't tell us which one stands true at the end of the day. There were still other factors that played into this aside from the individuals action(s). |
Re: Team 548 Einstein Statement
Quote:
Companies fall victim to situations like this all the time. In FIRST's case, it results in a disrupted competition. For other companies, it results in stolen consumer credit card information, a hacked website that installs a virus or trojan on consumers computers, a defaced website in general, or any number of other "bad" things. No company is immune from outside attacks... why should FIRST be any different? |
Re: Team 548 Einstein Statement
Remember, FIRST did not cause this. It was a bug in the newer Field AP firmware that created this security hole.
-Nick |
Re: Team 548 Einstein Statement
Thank you, 548, for stepping up. Even though it wasn't the team's fault, it was the right thing to do, I believe.
It takes real guts to do that. I don't know if I could have done the same. You didn't lose any of the respect I had for you. If anything, I now appreciate you more for coming forward, and I believe there are many others who feel the same way. As for this discussion... I think it is too early to discuss this. All that could've been said about the field system was said when the report came out. The things that can be said about the apology will now be all mixed up with emotions (namely anger from what I've seen in some comments). I think this discussion should be paused, and re-started in a week or so, so that everyone has a chance to think, relax, and digest. |
Re: Team 548 Einstein Statement
Given this admission/apology, I do wonder how this may affect the status of 548's paid entry into the 2013 Championship.
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
I think that 548's Steering Committee did a good job at responding to and handling the situation. Any mentor or student on a team is a representative of that team and officially associated with the team. This isn't just because you're wearing a team's t-shirt or branding, it's also because students and mentors officially register with a team through FIRST. If an individual on a team is involved in a negative situation, the leadership of the team is brought into the situation as well (ex-Football and Basketball players acting inappropriately).
Jon made a good point: Quote:
As for the individual, Jon and Andrew make great points: Quote:
Quote:
|
Re: Team 548 Einstein Statement
I just wanted to thank 548 for taking the courageous step of publishing this piece. Having committed no fault of their own, they've admirably given our community further impetus to move past the individual's conduct and embrace the challenges and opportunities this situation has exposed in our future. We owe it to ourselves honor just that.
I am impressed with the general tone of this thread in this point. I hope our students --and adults -- can continue to learn from the commendable behavior of 548, all the Einstein teams, and everyone involved in the invetigation. (Certainly some in their echelons may still be recovering, but hopefully this helps the process on tragically affected teams.) I know I will work to develop and retain this culture change, and while I hope we can avoid or preempt such incidents in the future, I believe we'll be better equipped as a community if we must handle one again. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
The actions of a single person does indeed reflect upon a team, but in this case it is very clear that this person acted alone. Certainly an error in judgment to take that action.
Team 548 is a class act all the way. Every family has its Black Sheep, so I do not put any blame on the team. So, their coming out and issuing an apology was above and beyond the call of duty. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
People pushed & pushed for "the team" and/or "the person" to finally come forward, and I really hope that we can leave it at 548's statement. It may not be 100% what everyone dreamed of... but I don't think anything will ever make the situation right.
The team could and SHOULD only have issued their understanding of what happened, which means they are 100% reliant on what the mentor told them happened. Whether the mentor told them the entire truth or not, what are we so worried about? The person is banned, the vulnerability fixed, tons of more issues were found and tediously documented, so lets move on. People that are worried about "discrepancies" are you looking to call the team or the mentor a liar? What good does that do? Or are you legitimately interested to know if there was "a second attacker"? And if so, are we just on our next witch hunt? I'm not sure people are fully understanding the team's statement. I pieced this together long before the team's statement, and I'm not sure people are getting it... I'm going to stop dancing around the numbers/"vaguery".... Quote:
Quote:
Quote:
I don't think this person was doing it to intentionally harm an alliance or to prove their ultimate hacking skills... I think it was a sad, last ditch effort to get the attention of FIRST and get their alliance "a fair shot" at competing. Lets let go of the details and all move on. The issue has been fixed, the team has come out into the open & apologized, and many other good things have resulted from all of this. So lets focus on moving forward. |
Re: Team 548 Einstein Statement
Kudos to 548 for coming forward and releasing this information. Don't worry, we still love you guys, and if anything, respect you even more for doing a difficult task such as this.
Also, I would like to wholeheartedly thank (even though I may get some crap for this) the individual who caused all of this. What he/she did was a good thing at the wrong time, the worst time. However, I'm going through this with an optimistic viewpoint. From what I'm reading, this individual's best interest was to show the problem to the FTA before it became a larger issue (based on the claim the individual saw some other interference). The individual also came forward to FIRST and admitted to the crime committed, as well as cooperated with FIRST to identify and ultimately come closer to solving the problem. How the individual effected Einstein was devastating to the students who worked hard to get there, but I believe it wasn't done with a cruel heart. From what I hear, this mentor was a fun and enthusiastic person geared towards inspiring and teaching today's youth, exactly what an ideal mentor would be like. Life banishment from the place where he can help and inspire students is probably one of the worst ideas ever. Maybe a temporary banishment (a few years or so) to let them think about what they've done. And then if Team 548 wants this mentor back, I think he/she should be allowed back, to continue inspiring and teaching students. What the individual did is completely terrible, but is it something forgivable? |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
Otherwise, Kim's statement accurately sums up my thoughts: Quote:
|
Re: Team 548 Einstein Statement
Disclaimer: The following is a hopeful opinion which is not proven. This disclaimer takes the place of all references to the fact that this is only one potential version of the situation, but deserves consideration nonetheless.
I can't really get mad about the "discrepancies" because I don't think the team statement is intended to be that deceitful. The series of events before the purposeful interference as we know them sound very emotionally stressful to the individual. High emotional stress inherently leads to poor judgement, and, in the long term, poor memory and recall. Even before he/she got busted, I'm willing to bet it would have been hard for him/her to recall the whole story. After the release of the Einstein Report, and the individual's subsequent ban for life, his/her story becomes shoddy at best. This is compounded by the possibility that the individual tried to convince him/herself that he/she isn't as guilty as he/she really is, leading to a real belief that is different from reality. By the time Steering Committee was told the story, it was probably far diverged from the truth. On the other hand, the well-documented unreliability of witnesses probably means the Einstein Report's version isn't all true, either. Like so many things, two sides of the same story are neither the truth nor lies, and the reality lies somewhere in between them. A couple other things: Quote:
I'm not comparing the magnitudes of each situation, just the framework. I'm also not calling the individual a murderer at all, I truly believe this was a good individual who made a bad choice. 2. Is it really one of the "worst ideas ever"? It's harsh, but you have to set a precedent and say "This is not acceptable in FIRST." 3. Not yet, it seems. But that doesn't mean it will never will be. After a while, everyone can look back differently. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
Lifetime ban is not only appropriate it's necessary. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
I simply don't believe the "protest" idea. The attacker could have indefinitely delayed the match by disconnecting a robot before the match itself started. This would have been an equally effective protest, but would not have risked affecting the outcome of the matches.
|
Re: Team 548 Einstein Statement
Quote:
Based on multiple other reports, I'm going to give little weight to what the now-banned party says happened, and I'm not going to apologize for that. But I will accept Team 548's statement at face value, put it behind me, move forward, and strongly encourage everyone else to do the same. |
Re: Team 548 Einstein Statement
Lack of grammar is not the only way something can be poorly written. It's poorly written because it is not explicitly clear who is being referred to. Not explicit enough for the circumstances.
It makes no sense why anyone should talk about forgiveness since no party here has sought it or made extremely explicitly clear who is at fault. On a personal level, I find the use of words like 'unfortunately' in an apology to be less than genuine. Stating the intent of someone while simultaneously not specifying who that it is we are talking about is laughable. As is the double standard of an individual not representing a team at a competition, but we're all such loyal team players to preserving anonymity. On a related note, genuine apologies are rare in our society, so it is with a complete lack of surprise that I find many cannot identify one or misidentify it. Ah, but I digress. |
Re: Team 548 Einstein Statement
Quote:
"I've found that being outraged on behalf of others is often a misuse of energy." Whether you're mad at the Robostangs, the singular individual, FIRST, or life, lamenting about the state of the world's apology writing is not going to help. *I don't know if there is a member of Team 548 named John Smith, nor do I intend to accuse anyone on the team of being the anonymous individual. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
Quote:
Quote:
Secondly, whether the individual made one attack or 100 attacks is a moot point. The individual's actions (regardless of intent) were malicious and he or she was punished accordingly. The job of the CD community is not to further scapegoat the individual for more attacks than he admitted to, as no proof exists. Instead, we should collectively be accepting of 548's generous apology (one they by no means had to provide) and we should all encourage FIRST to try and eliminate dead robots (due to control system failures) almost completely by 2014. |
Re: Team 548 Einstein Statement
I for one am quit satisfied with team 548 statement. Team 548 is also a victim in all of this. Having a "mentor out of control" can tear the guts out of a team. You have scars inside and outside of the team that takes years to recover. It is time to let team 548 work thru this and end this thread.
|
Re: Team 548 Einstein Statement
Quote:
Quote:
|
Re: Team 548 Einstein Statement
Quote:
We've heard 2 sides of the story so far, and unless someone would like to point out something I missed that puts them in direct conflict, I think it's only fair to evaluate this based on what we know. Everyone was feeling a lot of emotions at the moment, and the attack in response could have been from a moment of desperation. I'm not condoning what happened, but I am trying to understand it. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Two thoughts:
1. I can't imagine what next year will be like for the rookie members of 548. How does that conversation go? 2. I've yet to see a post from any of the directly affected Einstein teams in this thread (There is one on the first page from a Robonaut; it points to the article and offers no opinion on the subject). My first inclination is that they are coming together privately as teams to determine exactly how they feel about it; when they've grokked it in fullness, they'll make public statements as they see fit. My second inclination is simply there's nothing left to say. |
Re: Team 548 Einstein Statement
I'd like to start off by thanking the Robostangs for their statement. It takes a lot of guts to put yourself up in front of the Chief Delphi community. Your team still has as much respect from me as it did before.
One thing that no one has really thought of is the affects this has on the students that are part of that team. Regardless of what actually happened, how do you think they feel? I know that if one of my trusted mentors did something like this it'd take a long time for me to hold my head up high at a competition again. Arguing about whether or not the individuals acts were in good taste is pointless, nothing we say or do now can change what happened on Einstein. The same go with whether or not 548's apology was written by lawyers. Does it matter in the grand scheme of things? It is, after all, still an apology to the community. DISCLAIMER: This post is filled with my own thought's and opinions and does not necessarily reflect those of my team. |
Re: Team 548 Einstein Statement
Quote:
Quote:
|
Re: Team 548 Einstein Statement
Quote:
No one ever clicks on a list of networks again and misses the button? No one ever asks why documenting issues has to reach the public level? No one is ever curious again? No one ever considers using this particular ISM band again like this? I would feel much more comfortable with harsh punishment if you couldn't trip over this. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
Unfortunately the back story in this case seems to flow in a direction that you'd end up making the public report. I and others I know have since submitted concerns and vulnerabilities to FIRST and frankly no one I know has received so much as a confirmation e-mail. So what this will lead to is a pretty serious problem. FIRST has an investment in this control system for a while and that while definitely includes this upcoming year. I know for a fact that these vulnerabilities remain and their mitigation procedure will not address them so long as the control system remains essentially as it is. In 6 months if I publish my results publicly I can't with a straight face ever look at a hard to explain robot failure and not assume that I provided the core bit of knowledge that someone of less skill used to possibly cause that. This is a very bad situation. It does not excuse the interloper at all. It may not have been apparent to the interloper they would face this additional level of inertia in handling the security issues. There have been moments in my long involvement with FIRST that I felt I was utterly and sometimes quite wrongly ignored. Even that said I can think of a dozen ways in 1 minute that I can get my point across without using Einstein like that and compounding the existing issues with harm to every aspect of FIRST. I appreciate curiosity but I appreciate the value of the scientific method to satisfy that curiosity. There was no careful control for this experiment and therefore it's not an experiment. What it really is a bunch of intelligent people chasing individual agendas not working *together* and in the process making the situation much worse. Worse Einstein has become the distraction for who knows how many other possible interruptions that could have been caused accidentally or with intent. There's nothing in that report that closes that door, worse the lack of logs literally blows that door wide open. |
Re: Team 548 Einstein Statement
Quote:
The real fields are almost only available during competitions. This leaves I suppose the initial practice matches before the actual competition venues. One of the items I listed you could do quite utterly by mistake (I'm not saying this person didn't have intention to try it, I'm just saying we have no idea how many other people did that by mistake). |
Re: Team 548 Einstein Statement
Quote:
Let's think about it this way: You have a practice day (well, if you aren't in the districts, you do--even then you have some practice time). Do it to your own team then, it doesn't affect anybody else then--just make sure your team knows you're doing it. Typically, there's about an hour before matches start on any given competition day (depending on opening ceremony start time in relation to pit opening time--don't try anything during the ceremony!). And there is often a couple hours at the end of the day, with the exception being the last day. If you think that there is a problem with field vulnerability, or other system problems, Do Not Wait. Talk to the FTA during any of those "down" time periods--or ask in a shorter break, say between matches, if you can demonstrate the issue during them. If you are invited to demonstrate it, that's when you should do it--during lunch may also be an option. You can bet that if the vulnerability issue had been demonstrated to an FTA before Einstein, it would have been fixed or blocked before Einstein--it's one of those cases where "one guy knows, so we don't know how many others know". |
Re: Team 548 Einstein Statement
Quote:
Quote:
Great if they trip over it. Not so great if they don't. Additionally I can demonstrate additional issues right now. I know for a fact that several FIRST people know about them. Following only the reporting advice to e-mail the address on the report a person would literally be left in a vacuum. I have made it a point to make this harder to ignore because I expect that someone will do something about it. I'm growing ever more concerned that is not the case. By September FIRST is hard at work generating the documents and written parameters for 2013 in their final form. It's now August 21, 2012. So logistically when and where is this exploration going to get done? |
Re: Team 548 Einstein Statement
I will open by sharing that I feel good about the way FIRST has conducted themselves throughout this process. I believe that FIRST and the volunteers who participated in the investigation have demonstrated FIRST's values of Gracious Professionalism and Coopertition.
FIRST has shown respect for all of the individuals involved and the FRC community in their transparency and communications of the process and outcomes. They have investigated, learned and put plans in place to correct and improve their hardware, systems and processes. They have maintained their integrity and sensitivity to the Einstein teams and the FRC community throughout the process. What concerns me about some of the FRC community's response and the FIRST FRC Team 548 Einstein Statement is what it reveals about the FRC community's culture. I have read some comments in this thread suggesting that the interference of the Einstein matches was somehow excusable or justifiable. After reading the report, I come away with the sense that the document actually minimizes the egregiousness of the action. Certainly folks may and should be forgiven for failures. However, that does not remove the consequences, nor does it restore trust. GP means that we compete like crazy and at the same time play fair, maintain our integrity, while showing respect for our partners and opponents. I know that there have been times when I have not been a gracious professional. When I recognize it, I admit it, apologize, ask for forgiveness from the person I offended and resolve to do better. I see something like that in their statement and I hope that they do come out of this stronger and better. But ... what does it say about our culture that this happened and that there are attempts to excuse, justify or minimize it? I would echo what someone said in a previous post, albeit perhaps in a different context. We still have a long way to go. |
Re: Team 548 Einstein Statement
Quote:
EDIT: whoops, there was a 6th page and at least two people already said relatively the same thing:o |
Re: Team 548 Einstein Statement
Quote:
6 months is the end of January 2013. If I follow through with the 6 month process as it stands now I'll be giving the next interloper the perfect window of opportunity for 2013 by publishing in late January. FIRST who might do nothing with the knowledge till then would have little time to react. Worse FIRST will have solidified all their purchases and shipped all the kits of parts. Suffice it say I'm not thrilled with this. Worse even if I don't point it out then depending on a number of likely factors these exploits will be readily available to any interlopers that we don't know about if they've stumbled on them. If that's not a house of cards I don't know what is. So if I publish that information I risk FIRST responding by sanctioning me. If I don't publish that information who knows if or when it'll get exploited. For those who get the reference: 'The only way to win is not to play' and unfortunately I don't mean looking for security problem. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
August leaves 10 days. September they build the documents and the rules. October and November they setup the kits of parts. December is anything that rolls over and of course countless holidays. January, February and March is already too late. So in reality I've disclosed them to FIRST now. If I wait until after next season who knows what might happen. If I levy that sort of consequence on FIRST what might they do? Cause clearly other people have openly declared risk before that was not mitigated. It's not just about shifting a few days. It's about the body politic. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
I think the 548 statement was the right thing to do, they should be proud of what they did.
I would also like to point out that I see FIRST as a "sport". Back in high school I was on the varsity football team and there was some "cheating" going on there too. But I would like to say that I have seen more backstabbing in FRC than I did in football. People are people and that will never change, if you have a person who is willing to talk behind your back, then they will do it in FRC too. I had some team-mates who are my friends do this to me and it really hindered the way people see me, and still do to this day. But I am working hard to fix it still almost 3 years later. |
Re: Team 548 Einstein Statement
Quote:
This is a situation in which you have on one hand a vulnerability and a certain set of skills, resources and knowledge to outline it. The other you have an organization pushed to the limits exposed to that vulnerability and perhaps not inclined to deal with it. There's no reason...literally at all...to expect that I or any other researcher have the ability to influence FIRST corporate. That's the point. The implied threat of exposure is a weak threat with FIRST because FIRST is a corporation with hundreds of thousands of kids impacted by it. You're not just costing their corporate bottom line or reputation. As all of these similar topic represent you're messing with the kids and it's not one step removed like disclosing some banking data. Unfortunately this matters. There are too many disclosures I'm aware of and the costs on the other side of that big stick are too great. |
Re: Team 548 Einstein Statement
Quote:
The notion that one is threatening FIRST with disclosure is incorrect as well. FIRST should want to fix this issue (if they aren't there are other issues that are completely irrelevant to the discussion) and by letting them know you plan on publishing the findings at a later date you are simply being courteous and giving them a chance to fix the issue before it becomes public. No threats implied at all. |
Re: Team 548 Einstein Statement
Quote:
In 17 years my experience calling the FIRST switch board is dismal. Asking questions in the actual Q&A forum has often been criticized above and beyond this point (to the point I know people who intentionally avoid it). My experience obviously differs from your own. You might consider it not a threat to make such a disclosure with lots of time to resolve it, but under the current circumstances I see nothing, at all, that prevents FIRST from viewing your eventual disclosure as an open challenge to their authority. Right on topic the last person that pointed out something was asked to leave. One could argue that it would have been subsequently followed up. However, no where in any discussion that I have seen (or the reports) did it indicate what the process for that follow up was or was ever outlined to the reporting party. So I bring this back full circle. There are disclosures of issues I am aware of. What is the process by which these courtesies are reciprocated? I posed that same question weeks ago as well. |
Re: Team 548 Einstein Statement
One perspective that I think has not been brought up, that I think deserves attention is the competition rules. [T14] states:
"If a team needs clarification on a ruling or score, a pre-college student from that team should address the Head Referee after a field reset has been signaled. An team signals their desire to speak with the Head Referee by standing in the red or blue Question Box which will be placed on the floor at each end of the scoring table. Depending on timing, the Head Referee may postpone any requested discussion until the end of the subsequent Match." While that does not mention the FTA, it is the closest thing I could find to how an official interaction is made concerning the results of a match. I'm not saying this would have affected how staff reacted but I'd like to point out that, from my interpretation of that rule, the proper way for the mentor to bring this up at the field is not at all. If (s)he wanted, (s)he could have revealed this vulnerability to a team member, the team member would have stood in the question box and voiced these concerns with to the Head Referee, who would (hopefully) confer with the technical staff present, and things could have played out differently. I'm not saying they necessarily would have, but we do have rules about who engages field staff, it clearly indicates that only pre-college students may do so, and I know, when I'm volunteering on the field, I would rather talk to a student than a mentor. |
Re: Team 548 Einstein Statement
I've been watching this thread with much interest lately, and a few interesting points that (I believe) have not been addressed are still fresh in my mind.
First, aren't we forgetting the second person who brought down communications? The story that is corroborated both by the 548 mentor and the official report implies that there was a second attacker, who interestingly attacked the wifi network only after the 548 mentor did his three second demo attack. Most people appear to be assuming that the 548 mentor did all of the wifi atacks, which just doesn't appear to add up. Why did the second attacker act? Did they believe something similar to the first attacker, that they were being attacked? Or did they simply have a malicious intent? Second, was there institutional knowledge of this security hole? It appears that at least two (and probably more, if this thread is any indicator) FRC members knew of this specific hole. Did no one on the official FRC team know of this? This seems unlikely to me, but depending on the extent of the knowledge of this hole, it certainly could be true. If so, why didn't they attempt to patch it? If not, does this point to an institutional problem in a lack of focus on security? In either case, more needs to be done to recognize and address future security holes. Third, why did we never learn about this hole at Einstein, where it's relativity unlikely that two separate people coincidentally used this technique to bring down a match. Were there smaller incidents at regionals and division championships that simply did not get noticed until Einstein? Were people with knowledge of this quite until then, or simply unnoticed? And why did a thread never appear on CD with information about this? Surely, unless there was malicious intent, any loyal FIRSTer would rather report this than use it in a match. Were malicious (or simply very quite) people the only ones who ever knew or suspected a exploit of this type? Hopefully, my questions were constructive and not offensive. I'm just a little surprised that I've never seen them asked or answered yet. |
Re: Team 548 Einstein Statement
Quote:
Now, would it have been helpful to send a message by that route? Maybe--but that involves a) finding a student who isn't trying to fix something and b) having said student wait until they could get the head ref's attention. Then the head ref has to decide that it's important enough to call the FTA or FTAA away from whatever he's doing (probably trying to fix the problem with 118, in the case of 548's matches), oh and did I mention that by now it's second-or third-hand @DampRobot: I didn't pick up the implication of a second person involved in the official report. I got that only from 548's account. Also, a 3 second attack like that one would result in needing to reconnect the wifi, which can take a little bit of time, regardless of if there's another attacker or not. I think a lot of the questions you have are going to be very difficult to answer without putting people under suspicion of cheating or of total ignorance, either of which I'm reluctant to do. |
Re: Team 548 Einstein Statement
Quote:
I missed any implication of a second person in the Report. Where are you referring? Quote:
I know what's done is done, but hopefully an earnest examination will help anyone thinking of doing something like this in the future. No matter how helpless you feel thinking someone else is targeting your team, there are always other ways. In fact, you can't count on anyone even listening to you, much less getting a replay, if you try to interfere yourself. (Not that this is the key reason against interference.) |
Re: Team 548 Einstein Statement
Quote:
Also note, the robot remained connected to the field and in those cases where the team was using video from the robot, all status and video continued to be displayed at the driver's station. The robot was connected, just the command link from driver's station to robot was interrupted. Quote:
Quote:
To be absolutely clear, there are many people on or near the field during events. Some of these are non-technical volunteers and some have been tech volunteers in the past and some are volunteers who are also on teams competing on the field. Approaching one of those volunteers and expecting the same response as a field expert to a technical issue like this is a bad use of time. At every event there is a crew of volunteers whose directive is to make every robot play, that is the Robot Inspectors. During Champs finals, (all divisions and Einstein) there are inspectors assigned to the field to assist teams with problems and work with the head referee and FTA. There were two experienced division LRIs on Einstein, one on each side of the field during the matches and in the pit area assisting teams between matches. If you have a problem and cannot get resolution, please check in with an inspector or LRI. We want everyone to play, as often as they wish, within the rules of the competition. |
Quote:
It's the "1000 monkeys with 1000 typewriters" postulate at work, and I think it would be wise of FIRST to challenge all teams to try and find these exploits and notify FIRST as they appear. Crowd-source the troubleshooting of these systems, and allow teams to have active feedback throughout the season. It would solve a lot of problems. And I agree with the idea that FIRST should have some kind of pre-written response to let teams know that emails are at least going through. |
Re: Team 548 Einstein Statement
Quote:
Simply put: the problem with the "1,000 monkeys with 1,000 typewriters" postulate in reality is filtering out the 99%+ gibberish content they've created. |
Re: Team 548 Einstein Statement
Quote:
|
Re: Team 548 Einstein Statement
Quote:
This would be easier to accomplish with more open documentation about the field (so it can be more readily replicated) and more access to fields (itself not a trivial request). Of course all of that is useless without clear lines of communications and process. Also there are probably more devices than one might realize at any one event that can use 5GHz because they are not line of sight to the field. Consider all the driver's station laptops in the pits. I'll assume that no one on the field with a 5GHz laptop has time to be doing anything but what is expected of them. With Windows Vista and above it would be very simple to craft a background script running as system that would exploit the failed connect attempt hole totally hidden from all but the most experienced eyes even on a driver's station on the field (in effect malware for the field). This wouldn't seem out of place at all because of the driver station software reliance on Windows. Also if someone had a COTS computing device on the robot a similar tactic with wider OS selection would be possible. I am comfortable making this statement because this particular vulnerability is much easier to remedy than others I am aware of. |
| All times are GMT -5. The time now is 21:36. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi