Description of problem:

Using the application "osc", I get in some conditions/some repositories the following message:

```
repa@pascua mtl]$ osc commit
IncompleteRead(0 bytes read)
```

Version-Release number of selected component (if applicable):

Tried both osc as installed by default in Fedora 32 (0.167.1-281.1.4), and the version in the obs://build.opensuse.org/openSUSE:Tools repository. Found a similar report for arch:

https://github.com/openSUSE/osc/issues/771

where the problem was traced down to python-m2crypto, version 0.35.2, same as installed in Fedora 32

```
base) [repa@pascua mtl]$ rpm -q python3-m2crypto
python3-m2crypto-0.35.2-6.fc32.x86_64
```

How reproducible:


Steps to Reproduce:
1. any `osc` command using the remote repository

Actual results:
```
repa@pascua mtl]$ osc commit
IncompleteRead(0 bytes read)
```

Expected results:

Successful commit or more sensible error message. 

Additional info:

The bug apparently depends on the required communication; sometimes it would occur and an `osc update` would then succeed and set the state of the communication to one that would allow a later commit. 

According to information in the link above, this can be caused by a known bug in python-m2crypto that has a fix in a pull request.