Remove crypto functions already available in library dependency

[vladimir-v-diaz]

Description of issue:

Some crypto functions implemented in TUF are duplicates of functions available in securesystemslib.

Current behavior:

For example, generate_and_write_rsa_keypair() is also provided by securesystemslib's equivalent.

Expected behavior:

The TUF library should replace all crypto functions that are already available in securesystemlib.

[Skchoudhary]

Hi @vladimir-v-diaz, I would like to work on this issue.Can you guide me which methods/file to look.

[awwad]

There's an example in the description.

[vladimir-v-diaz]

Thanks for the interest, @Skchoudhary. You would essentially replace the crypto functions in repository_lib.py that are duplicated in SSLib's interface.py.

@awwad will be able to confirm the specific functions that you are thinking of replacing. A pull request will make it easier for him to give you feedback.

[mallenjr]

Has this issue been resolved? I am looking at the code in the file mentioned above and from what I can tell the functions have all been converted over to the functions that are available in securesystemslib.

[tobithegreat]

Hello! It seems like this issue hasn't been resolved yet. I'd like to submit a pull request if that's alright.

[joshuagl]

I think this issue was resolved by PR #460? Or is it preferable to go one step further and remove the tuf methods which simply wrap functionality in securesystemslib? Such as import_ed25519_publickey_from_file()?

[lukpueh]

It looks like (pending) #804 also made some contributions there. I'll go ahead and review it.

Regarding you question, @joshuagl, I think (for now) we want to keep the wrappers to not change TUFs interface.