DisplayPort does away with all that legacy. I assume the hardware to implement it is much simpler and more reliable.
DisplayPort does away with all that legacy. I assume the hardware to implement it is much simpler and more reliable.
>DisplayPort uses a scrambler as part of its line encoding in order to flatten the Fourier spectrum of its emissions and suppress spectral peaks caused by particular image contents. This reduces the chances of any particular image content causing a problem spectral peak during SDIP-27 and EMI spectrum measurements. According to the standard, the scrambler reduces spectral peaks by about 7 dB. As a side effect, the scrambler also makes it far more difficult, probably even impractical, for an attacker to reconstruct any information about the displayed image from the DisplayPort emissions. [..] DisplayPort uses a small number of fixed bit rates, independent of the video mode used. Unlike with most other digital interfaces, video data is transmitted in data packets with header and padding bytes, and not continuously with a television-like timing. As a result, DisplayPort cables are not a common source of van-Eckstyle video emanations and this again will make it very hard for an eavesdropper to synchronize to the transmitted data.
Speaking of which: how does one force HDCP (say, in Linux)? That would transform this technology from a DRM nuisance (strippers easily available on AliExpress) into a Van Eck-countermeasure.
HDCP itself needs to be licensed in order to generate it, and that licence is only available to HDMI Adopter companies. However there is code to get some chipsets to turn it on: https://github.com/intel/hdcp
Grab it now before Intel deletes it completely.
HDCP is really a very ugly protocol designed just for anti-copying, I wouldn't build anything relying on it, and everything is harder with HDCP from an AV integration perspective. If you have long links that you want to secure, use something like SDVoE with encryption and authentication (bits are easily flipped in HDCP).
As a programmer myself, I have to say no to electronic voting systems. We need to keep it low tech.
Even if the code is released:
(1) Who can read and understand tens or hundreds of thousands of lines of probably not very comprehensible code? Not many people can and even fewer will.
(2) Is the code running on the machines the same as the published code?
I don't even know what code is running on my phone or laptop right now.
Disclosure: I used to work for an Election Services company.
I can explain a voting process with pen and paper to a child.
When you vote with some sort of association with your name I can look up how you voted after the fact and if you didn't vote for Pedro I can blow up your house.
The fact is that the secret, anonymous ballot is the only valid way of voting.
If you could do that at a scale large enough to affect the result, I would think you could also do that at each ballot box and make the vote counters report the results you want them to report.
Also, if you could do that at scale, why would you bother with elections at all?
IMO, the main problem with digital voting is that it makes it possible to change the vote count without needing lots of people to do so.
With thousands of ballot boxes, open counting of votes for each ballot box and the publication of election results per ballot box that’s basically impossible.
I think few fraudsters will be happy with slightly increasing their odds by swinging the vote by a few hundred votes. Instead, they’ll want almost certainty, if not complete certainty.
(I still support electronic voting though).
Screen scraping is the least of the problems.
Voting machines are simply not trustworthy given these requirements for a free and fair election:
0. Freedom to vote or not
1. Anonymity in that no vote may be associated with the voter who cast it
(These two are most of why e-voting is not trustworthy and are what differentiates banking from voting.)
2. Transparency. The law, means, methods must all be known to the voting public. It is their election. In particular, seeing how a cast vote moves through the entire process and into the final tally is necessary.
3. Oversight. The first two of these foundation requirements necessary for free and fair public elections have an important ratification:
The record of votes cast must be human readable and said record must be used directly to realize the final tally of all votes cast.
There is a chain of trust between voter intent and the vote cast. When one casts a vote on physical media, that is a direct record of voter intent. The voter can be sure their intent adds to the tally because they can directly verify their votes cast.
Electronic votes are a vote by proxy. The direct expression of intent is not kept and exists as a bit of skin residue left on the machine interface. Put simply, we ask people to vote and then we discard their expression!
What gets used instead is whatever the machine thought the voter intent was!
Consider this: You have a machine in front of you with two buttons. One brings the world into harmony, the other casts it into war, grief and darkness.
You can:
A. Submit a paper form you fill out manually indicating your choice
, or
B. Press one of the buttons and get a receipt for your records.
Say this machine has an indicator showing your choice and a third "approval" button you use when you feel good about the machine getting your choice right.
How do you the voter know the receipt and or indicators match what the proxy machine says your choice was.
What happens when we have a dispute? We know the machine can't be trusted to match receipts. With the direct expression of intent lost, what do we bring to court?
We can and have brought paper ballots into court to resolve and election facing genuine ambiguity.
I submit to you we can't really be sure who wins an electronic election, unless we also associate your identity with the vote.
Say a bunch of people get to choose the fate of the world this way. What is your confidence level?
How do we know the machines tallied up the winning choices correctly?
What do the tests for that look like and how do they get around the forced trust problem we have with all electronic inputs today?
There is a lot more trouble to discuss. What I put here is the core trouble and computers have always had this problem too.
It just does not present any real difficulty, until elections are brought into the discussion.
Display trust issues are well above the core tech trust issues we face today.
[1] https://everymac.com/monitors/apple/studio_cinema/specs/appl...
I also think that DP rouuuughly reflects CRT timings complete with active vs. blanking intervals, but doesn't actually have a fixed pixel clock (perhaps it does? I didn't quite figure out synchronous/asynchronous pixel transmission when reading the spec) and doesn't transmit hsync pulses once per scanline.
From memory IBM offered a crt with DVI.
You wish. DP sends exactly same bytes DVI does (blanking and all), just broken up into packets.
MST is quite complicated and appears to interleave bytes from different video streams within 64-byte packets (rather than solely during blanking):
> The MTP (Multi-stream Transport Packet) is 64 link-symbol (1 byte of video data or special symbols) cycles (that is, 64 time slots) long, starting with MTP Header in the first time slot (or Time Slot 0), and is constantly transported regardless of the presence/absence of streams.
> The Payload Bandwidth Manager of each uPacket TX in the path from a DP Source to a target Sink device allocates time slots within the MTP to a VC (Virtual Channel) Payload to establish the virtual channel for transporting a stream.