Roondar wrote:This would obviously not work. La Forge is the most likely person to do these alterations, and the Klingon sisters obviously can see whatever he does. Including the new shield frequency. By the time they could have realistically (without audience knowledge) have figured out that La Forge was the one who caused their problems, it would have been too late anyway - the battle was over very quickly.
First: Changing the shield frequency is the obvious thing to do in their situation, and they didn't even
try. That's stupid.
Second: Geordi is no doubt moving around engineering doing a variety of things in a combat situation. To think he would have his eyes constantly on the readout of shield frequency is unreasonable. The Klingons might be able to catch it occasionally, but to think they would instantly know about any frequency change is unreasonable.
Third: If all else fails, they can go to "anti-Borg" tactics and activate the routine that constantly makes random changes to shield frequency.
Finally: The whole stupidity issue could have been avoided completely if they'd just said that the first hit seriously compromised the shields instead of using the same "shield tricked" visual effect throughout the battle, making it obvious that no one was doing anything about the shield problem.
Roondar wrote:This has indeed bothered me for a long time, but I think there may be a reasonable explanation: the Enterprise was hit in it's engineering sections almost immediately. It's quite conceivable the damage done during the initial attacks reduced the Enterprise's capacity to react severely.
This would not be out of line with other situations in which a damaged ship equals one that can't fight as well.
While we wouldn't expect the ship to perform as well when damaged, we saw in "Yesterday's Enterprise" that the ship can still throw out a lot of firepower even after being damaged. Furthermore, the Enterprise took a hit from a Cardassian cruiser in "The Wounded" while the shields were down, and she was still very combat-capable afterward.
On the other hand, we've also seen that one hit can sometimes bring down all weapons on the ship, which means the whole weapon system has a single point of failure -- a design flaw if I ever heard of one.
From what we saw of the battle, though, Riker ordered one phaser shot and one photon torpedo. That pathetic level of response to an attack is really hard to excuse.
Roondar wrote:Wasn't beaming people off ships/stations something that was pretty much impossible without a com badge during most of TNG?
(not totally so, but clearly not trivial either)
Comm badges certainly help, and they're probably necessary if you want to locate a particular human among many humans to transport, but we know that their sensors can distinguish humans from other humanoids, so locking on to the Ferengi shouldn't be that big a deal. Given how worried the ghost possessing O'Brien was about the transporters in "Power Play", it seems like getting rid of boarders with the transporter should be easy.
Roondar wrote:Actually, there are authorization protocols aplenty. It's just that they're (sadly) usually hackable as well. Some of the computer security in the various shows and movies is actually quite decent.
The Federation's authorization protocols seem to work pretty well, but their
authentication protocols seem to suck. If the computer knows who you are, it generally limits your access appropriately, but it misidentifies people with shocking frequency. Case in point, Roga Danar in "The Hunted": he was able to shut down a security force field just by speaking into a security guard's comm badge. Furthermore, he was able to do use the control panels in Engineering to the point that he was literally fighting with Data for control of transporter functions.
In this case, though, you'd think they wouldn't need to worry. The command functions they're worried about generally use voice recognition to authenticate, and the Ferengi didn't seem to have any means to imitate the voices of the Enterprise's command staff.
Roondar wrote:(tbh I think the problem here is, and this is seen in almost all Sci-Fi, that the writers of Star Trek have no idea how computers and securing them works. Same with StarWars and the Ubah-Leet-Hacka R2D2 - who was not a security bypass tool, he merely had the proper network cable. His actual job was helping control/maintain specific starfighters)
I won't dispute the total lack of InfoSec knowledge by the Trek writing staff; they have a track record technical and scientific ignorance that marrs many a script.
R2-D2's hacking is an interesting side issue, though. Imperial computer networks apparently have "guest accounts" for visiting droids to use, and they can obviously be exploited. Further, if Cloud City's computer is any indication, the network itself is an AI; the city's computer
volunteered information to R2 about the condition of the
Millenium Falcon. I suspect that getting information from an Imperial computer may be more akin to social engineering than straight hacking.