python/python-smbprotocol
SHA256
14
0
Fork 0
forked from pool/python-smbprotocol
Code Pull Requests Activity

Accepting request 881292 from home:mnhauke

Browse Source 
- Update to version 1.5.0
  * Added smbprotocol.exceptions.SMBConnectionClosed that is
    raised when trying to send or receive data on a connection
    that has been closed.
  * Added smbprotocol.exceptions.WrongPassword that is raised when
    some servers indicate the password is not correct or the
    account is locked out.
  * Do not attempt to reuse any cached connections that have been
    closed in smbclient
  * Added a lock when writing to the socket, only 1 thread can
    write a message at a single point in time
  * Revamped the SMB receiver code to simplify the logic and make
    it more durable
    + Removed the TCP recv thread for each connection, now each
      connection uses just 1 thread instead of 2.
    + Be more defensive when reading data from a socket to ensure
      we get all the data we require.
    + Handled server side FIN packets that close the connection
      unexpectedly, any requests waiting for a response will
      raise SMBConnectionClosed.

OBS-URL: https://build.opensuse.org/request/show/881292
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-smbprotocol?expand=0&rev=20
This commit is contained in:
Matej Cepl
2021-03-25 12:24:08 +00:00
committed by Git OBS Bridge
parent 2a7e3b4934
commit 9d9acb8ffe
4 changed files with 28 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
python-smbprotocol.changes
View File

@@ -1,3 +1,27 @@
-------------------------------------------------------------------
Thu Mar 25 09:39:12 UTC 2021 - Martin Hauke <mardnh@gmx.de>
- Update to version 1.5.0
* Added smbprotocol.exceptions.SMBConnectionClosed that is
raised when trying to send or receive data on a connection
that has been closed.
* Added smbprotocol.exceptions.WrongPassword that is raised when
some servers indicate the password is not correct or the
account is locked out.
* Do not attempt to reuse any cached connections that have been
closed in smbclient
* Added a lock when writing to the socket, only 1 thread can
write a message at a single point in time
* Revamped the SMB receiver code to simplify the logic and make
it more durable
+ Removed the TCP recv thread for each connection, now each
connection uses just 1 thread instead of 2.
+ Be more defensive when reading data from a socket to ensure
we get all the data we require.
+ Handled server side FIN packets that close the connection
unexpectedly, any requests waiting for a response will
raise SMBConnectionClosed.
-------------------------------------------------------------------
Wed Feb 3 22:22:15 UTC 2021 - Martin Hauke <mardnh@gmx.de>