Its secure :)
Well, I am fairly sure that protocol i proposed is secure because it relies
on the fact that public key cryptography works. Thing is that after both
sides „agree” on new randomly generated key you can tell the operator
that the key was doughnut but it won't matter anymore and session will remain
secure. And operator is unable to insert his key because initial „easy”
key was transmited using third party. One key can be reused (assuming you
didnt tell it to operator) and it would still not matter because operator
has 1 guess per session.
- Re: [Trisquel-users] Remote Support (aka Teamviewe... chris
- Re: [Trisquel-users] Remote Support (aka Teamv... krofnica996
- Re: [Trisquel-users] Remote Support (aka T... Michał Masłowski
- Re: [Trisquel-users] Remote Support (a... krofnica996
- Re: [Trisquel-users] Remote Suppo... Michał Masłowski
- Re: [Trisquel-users] Remote S... krofnica996
- Re: [Trisquel-users] Remote S... krofnica996
- Re: [Trisquel-users] Remote S... Michał Masłowski
- Re: [Trisquel-users] Remote S... krofnica996
- Re: [Trisquel-users] Remote S... Michał Masłowski
- [Trisquel-users] Antwort: Rem... krofnica996
- Re: [Trisquel-users] Remote Support (aka T... krofnica996
- Re: [Trisquel-users] Remote Support (aka Teamviewer Rep... icarolongo
- Re: [Trisquel-users] Remote Support (aka Teamviewer Rep... chris
- Re: [Trisquel-users] Remote Support (aka Teamviewer Rep... matt . ivie
- Re: [Trisquel-users] Remote Support (aka Teamviewer Rep... icarolongo
- Re: [Trisquel-users] Remote Support (aka Teamviewer Rep... icarolongo