| Name | smbprotocol JSON |
| Version |
1.14.0
JSON |
| download |
| home_page | None |
| Summary | Interact with a server using the SMB 2/3 Protocol |
| upload_time | 2024-08-25 21:26:33 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.8 |
| license | MIT License Copyright (c) 2017 Jordan Borean, Red Hat Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| keywords |
smb
smb2
smb3
cifs
python
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# smbprotocol
SMBv2 and v3 Client for Python.
[](https://github.com/jborean93/smbprotocol/actions/workflows/ci.yml)
[](https://codecov.io/gh/jborean93/smbprotocol)
[](https://badge.fury.io/py/smbprotocol)
[](https://github.com/jborean93/smbprotocol/blob/master/LICENSE)
SMB is a network file sharing protocol and has numerous iterations over the
years. This library implements the SMBv2 and SMBv3 protocol based on the
[MS-SMB2](https://msdn.microsoft.com/en-us/library/cc246482.aspx) document.
## Features
* Negotiation of the SMB 2.0.2 protocol to SMB 3.1.1 (Windows 10/Server 2016)
* Authentication with both NTLM and Kerberos
* Message signing
* Message encryption (SMB 3.x.x+)
* Connect to a Tree/Share
* Opening of files, pipes and directories
* Set create contexts when opening files
* Read and writing of files and pipes
* Sending IOCTL commands
* Sending of multiple messages in one packet (compounding)
* Experimental support for both standalone and DFS server shares
This is definitely not feature complete as SMB is quite a complex protocol, see
backlog for features that would be nice to have in this library.
## Requirements
* Python 3.7+
* For Kerberos auth on Linux
* [python-gssapi](https://github.com/pythongssapi/python-gssapi)
* [pykrb5](https://github.com/jborean93/pykrb5)
To use Kerberos authentication on Linux, further dependencies are required, to install these dependencies run
```bash
# for Debian/Ubuntu/etc:
sudo apt-get install gcc python-dev libkrb5-dev
pip install smbprotocol[kerberos]
# for RHEL/CentOS/etc:
sudo yum install gcc python-devel krb5-devel krb5-workstation python-devel
pip install smbprotocol[kerberos]
```
Kerberos auth with Windows should just work out of the box with the `pyspnego` library but on Linux, the
`python-gssapi` library must be installed and `smbprotocol` requires a particular GSSAPI extension to be available to
work. This extension should be installed on the majority of MIT or Heimdal Kerberos installs but that is not a
guarantee. To verify that Kerberos is available on Linux you can run the following check in a Python console:
```python
try:
from gssapi.raw import inquire_sec_context_by_oid
print("python-gssapi extension is available")
except ImportError as exc:
print(f"python-gssapi extension is not available: {exc}")
```
If it isn't available, then either a newer version of the system's gssapi implementation needs to be setup and
python-gssapi compiled against that newer version. In the absence of this extension, only NTLM auth is used.
## Installation
To install smbprotocol, simply run
```bash
pip install smbprotocol
# To install with Kerberos support
pip install smbprotocol[kerberos]
```
This will download the required packages that are used in this package and get
your Python environment ready to go.
## Additional Info
One of the first steps as part of the SMB protocol is to negotiate the dialect
used and other features that are available. Currently smbprotocol supports
the following dialects;
* `2.0.0`: Added with Server 2008/Windows Vista
* `2.1.0`: Added with Server 2008 R2/Windows 7
* `3.0.0`: Added with Server 2012/Windows 8
* `3.0.2`: Added with Server 2012 R2/Windows 8.1
* `3.1.1`: Added with Server 2016/Windows10
Each dialect adds in more features to the protocol where some are minor but
some are major. One major changes is in Dialect 3.x where it added message
encryption. Message encryption is set to True by default and needs to be
overridden when creating a Session object for the older dialects.
By default, the negotiation process will use the latest dialect that is
supported by the server but this can be overridden if required. When this is
done by the following code
```python
import uuid
from smbprotocol.connection import Connection, Dialects
connection = Connection(uuid.uuid4(), "server", 445)
connection.connect(Dialects.SMB_3_0_2)
```
While you shouldn't want to downgrade to an earlier version, this does allow
you to set a minimum dialect version if required.
## Examples
There are 2 different APIs you can use with this library.
* `smbprotocol`: Low level interface that can do whatever you want but quite verbose
* `smbclient`: Higher level interface that implements the builtin `os` and `os.path` file system functions but for SMB support
The `examples` folder contains some examples of both the high and low level
interface but for everyday user's it is recommended to use `smbclient` as it
is a lot simpler.
### smbclient Interface
The higher level interface `smbclient` is designed to make this library easier
for people to use for simple and common use cases. It is designed to replicate
the builtin `os` and `os.path` filesystem functions like `os.open()`,
`os.stat()`, and `os.path.exists()`. It is also designed to handle connections
to a DFS target unlike `smbprotocol`.
A connection made by `smbclient` is kept in a pool and re-used for future
requests to the same server until the Python process exists. This makes
authentication simple and only required for the first call to the server. Any
DFS referrals are also cached in that Python process. This optimises any
future requests to that same DFS namespace.
The functions in `smbclient` have a global config object that can be used to
set any connection defaults to use for any future connections. It can also be
used to specify any domain based DFS settings for more advanced setups. It is
recommended to use `ClientConfig()` to set any global credentials like so:
```python
import smbclient
smbclient.ClientConfig(username='user', password='password')
```
The `ClientConfig` is a singleton and any future instanciations of that
object will just update the keys being set. You can set the following keys on
the `ClientConfig`:
* `client_guid`: The client GUID to identify the client to the server on a new connection
* `username`: The default username to use when creating a new SMB session if explicit credentials weren't set
* `password`: The default password to use for authentication
* `domain_controller`: The domain controller hostname. This is useful for environments with DFS servers as it is used to identify the DFS domain information automatically
* `skip_dfs`: Whether to skip doing any DFS resolution, useful if there is a bug or you don't want to waste any roundtrip requesting referrals
* `auth_protocol`: The authentication protocol to use; `negotiate` (default), `kerberos`, or `ntlm`
* `require_secure_negotiate`: Control whether the client validates the negotiation info when connecting to a share (default: `True`).
* More information can be found on [SMB3 Secure Dialect Negotiation](https://docs.microsoft.com/en-us/archive/blogs/openspecification/smb3-secure-dialect-negotiation)
As well as setting the default credentials on the `ClientConfig` you can also
specify the credentials and other connection parameters on each `smbclient`
function or when registering a new server. These functions accept the
following kwargs:
* `username`: The username used to connect to the share
* `password`: The password used to connect to the share
* `port`: Override the default port (`445`) to connect to
* `encrypt`: Whether to force encryption on the connection, requires SMBv3 or newer on the remote server (default: `False`)
* `connection_timeout`: Override the connection timeout in seconds (default: `60`)
If using Kerberos authentication and a Kerberos ticket has already set by
`kinit` then `smbclient` will automatically use those credentials without
having to be explicitly set. If no ticket has been retrieved or you wish to use
different credentials then set the default credentials on the `ClientConfig`
or specify `username` and `password` on the first request to the server.
For example I only need to set the credentials on the first request to create
the directory and not for the subsequent file creation in that dir.
```python
import smbclient
# Optional - specify the default credentials to use on the global config object
smbclient.ClientConfig(username='user', password='pass')
# Optional - register the credentials with a server (overrides ClientConfig for that server)
smbclient.register_session("server", username="user", password="pass")
smbclient.mkdir(r"\\server\share\directory", username="user", password="pass")
with smbclient.open_file(r"\\server\share\directory\file.txt", mode="w") as fd:
fd.write(u"file contents")
```
If you wish to reset the cache you can either start a new Python process or
call `smbclient.reset_connection_cache()` to close all the connections that
have been cached by the client.
## Logging
This library makes use of the builtin Python logging facilities. Log messages
are logged to the `smbprotocol` named logger as well as `smbprotocol.*` where
`*` is each python script in the `smbprotocol` directory.
These logs are really useful when debugging issues as they give you a more
step by step snapshot of what it is doing and what may be going wrong. The
debug side will also print out a human readable string of each SMB packet that
is sent out from the client so it can get very verbose.
## Testing
To this module, you need to install some pre-requisites first. This can be done
by running;
```bash
# Install in current environment.
# Recommend to have virtual environment installed at .venv path.
pip install -r requirements-dev.txt
pip install -e .
# you can also run tox by installing tox
pip install tox
```
From there to run the basic tests run;
```bash
py.test -v --cov smbprotocol --cov-report term-missing
# or with tox for dedicated virtual environments and multiple Python versions.
tox
```
Before sending the code for review, besides making sure all the test pass,
check that the code complies with the coding standards:
```bash
source ./build_helpers/lib.sh
lib::sanity::run
```
There are extra tests that only run when certain environment variables are set.
To run these tests set the following variables;
* `SMB_USER`: The username to authenticate with
* `SMB_PASSWORD`: The password to authenticate with
* `SMB_SERVER`: The IP or hostname of the server to authenticate with
* `SMB_PORT`: The port the SMB server is listening on, default is `445`
* `SMB_SHARE`: The name of the share to connect to, a share with this name must exist as well as a share with the name`$SMB_SHARE-encrypted` must also exist that forces encryption
From here running `tox` or `py.test` with these environment variables set will
activate the integration tests.
This requires either Windows 10 or Server 2016 as they support Dialect 3.1.1
which is required by the tests.
If you don't have access to a Windows host, you can use Docker to setup a
Samba container and use that as part of the tests. To do so run the following
bash commands;
```bash
source ./build_helpers/lib.sh
lib::setup::smb_server
```
This command will also set the required `SMB_*` env vars used in testing.
## Backlog
Here is a list of features that I would like to incorporate, PRs are welcome
if you want to implement them yourself;
* Multiple channel support to speed up large data transfers
* Lots and lots more...
Raw data
{
"_id": null,
"home_page": null,
"name": "smbprotocol",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": null,
"keywords": "smb, smb2, smb3, cifs, python",
"author": null,
"author_email": "Jordan Borean <jborean93@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/41/0d/d178f651591de45607d6dfc5637e7dcd8c5190b137275303cda005d9a13a/smbprotocol-1.14.0.tar.gz",
"platform": null,
"description": "# smbprotocol\nSMBv2 and v3 Client for Python.\n\n\n[](https://github.com/jborean93/smbprotocol/actions/workflows/ci.yml)\n[](https://codecov.io/gh/jborean93/smbprotocol)\n[](https://badge.fury.io/py/smbprotocol)\n[](https://github.com/jborean93/smbprotocol/blob/master/LICENSE)\n\nSMB is a network file sharing protocol and has numerous iterations over the\nyears. This library implements the SMBv2 and SMBv3 protocol based on the\n[MS-SMB2](https://msdn.microsoft.com/en-us/library/cc246482.aspx) document.\n\n\n## Features\n\n* Negotiation of the SMB 2.0.2 protocol to SMB 3.1.1 (Windows 10/Server 2016)\n* Authentication with both NTLM and Kerberos\n* Message signing\n* Message encryption (SMB 3.x.x+)\n* Connect to a Tree/Share\n* Opening of files, pipes and directories\n* Set create contexts when opening files\n* Read and writing of files and pipes\n* Sending IOCTL commands\n* Sending of multiple messages in one packet (compounding)\n* Experimental support for both standalone and DFS server shares\n\nThis is definitely not feature complete as SMB is quite a complex protocol, see\nbacklog for features that would be nice to have in this library.\n\n\n## Requirements\n\n* Python 3.7+\n* For Kerberos auth on Linux\n * [python-gssapi](https://github.com/pythongssapi/python-gssapi)\n * [pykrb5](https://github.com/jborean93/pykrb5)\n\nTo use Kerberos authentication on Linux, further dependencies are required, to install these dependencies run\n\n```bash\n# for Debian/Ubuntu/etc:\nsudo apt-get install gcc python-dev libkrb5-dev\npip install smbprotocol[kerberos]\n\n# for RHEL/CentOS/etc:\nsudo yum install gcc python-devel krb5-devel krb5-workstation python-devel\npip install smbprotocol[kerberos]\n```\n\nKerberos auth with Windows should just work out of the box with the `pyspnego` library but on Linux, the\n`python-gssapi` library must be installed and `smbprotocol` requires a particular GSSAPI extension to be available to\nwork. This extension should be installed on the majority of MIT or Heimdal Kerberos installs but that is not a\nguarantee. To verify that Kerberos is available on Linux you can run the following check in a Python console:\n\n```python\ntry:\n from gssapi.raw import inquire_sec_context_by_oid\n print(\"python-gssapi extension is available\")\nexcept ImportError as exc:\n print(f\"python-gssapi extension is not available: {exc}\")\n```\n\nIf it isn't available, then either a newer version of the system's gssapi implementation needs to be setup and\npython-gssapi compiled against that newer version. In the absence of this extension, only NTLM auth is used.\n\n\n## Installation\n\nTo install smbprotocol, simply run\n\n```bash\npip install smbprotocol\n\n# To install with Kerberos support\npip install smbprotocol[kerberos]\n```\n\nThis will download the required packages that are used in this package and get\nyour Python environment ready to go.\n\n\n## Additional Info\n\nOne of the first steps as part of the SMB protocol is to negotiate the dialect\nused and other features that are available. Currently smbprotocol supports\nthe following dialects;\n\n* `2.0.0`: Added with Server 2008/Windows Vista\n* `2.1.0`: Added with Server 2008 R2/Windows 7\n* `3.0.0`: Added with Server 2012/Windows 8\n* `3.0.2`: Added with Server 2012 R2/Windows 8.1\n* `3.1.1`: Added with Server 2016/Windows10\n\nEach dialect adds in more features to the protocol where some are minor but\nsome are major. One major changes is in Dialect 3.x where it added message\nencryption. Message encryption is set to True by default and needs to be\noverridden when creating a Session object for the older dialects.\n\nBy default, the negotiation process will use the latest dialect that is\nsupported by the server but this can be overridden if required. When this is\ndone by the following code\n\n```python\nimport uuid\n\nfrom smbprotocol.connection import Connection, Dialects\n\nconnection = Connection(uuid.uuid4(), \"server\", 445)\nconnection.connect(Dialects.SMB_3_0_2)\n```\n\nWhile you shouldn't want to downgrade to an earlier version, this does allow\nyou to set a minimum dialect version if required.\n\n\n## Examples\n\nThere are 2 different APIs you can use with this library.\n\n* `smbprotocol`: Low level interface that can do whatever you want but quite verbose\n* `smbclient`: Higher level interface that implements the builtin `os` and `os.path` file system functions but for SMB support\n\nThe `examples` folder contains some examples of both the high and low level\ninterface but for everyday user's it is recommended to use `smbclient` as it\nis a lot simpler.\n\n### smbclient Interface\n\nThe higher level interface `smbclient` is designed to make this library easier\nfor people to use for simple and common use cases. It is designed to replicate\nthe builtin `os` and `os.path` filesystem functions like `os.open()`,\n`os.stat()`, and `os.path.exists()`. It is also designed to handle connections\nto a DFS target unlike `smbprotocol`.\n\nA connection made by `smbclient` is kept in a pool and re-used for future\nrequests to the same server until the Python process exists. This makes\nauthentication simple and only required for the first call to the server. Any\nDFS referrals are also cached in that Python process. This optimises any\nfuture requests to that same DFS namespace.\n\nThe functions in `smbclient` have a global config object that can be used to\nset any connection defaults to use for any future connections. It can also be\nused to specify any domain based DFS settings for more advanced setups. It is\nrecommended to use `ClientConfig()` to set any global credentials like so:\n\n```python\nimport smbclient\n\nsmbclient.ClientConfig(username='user', password='password')\n```\n\nThe `ClientConfig` is a singleton and any future instanciations of that\nobject will just update the keys being set. You can set the following keys on\nthe `ClientConfig`:\n\n* `client_guid`: The client GUID to identify the client to the server on a new connection\n* `username`: The default username to use when creating a new SMB session if explicit credentials weren't set\n* `password`: The default password to use for authentication\n* `domain_controller`: The domain controller hostname. This is useful for environments with DFS servers as it is used to identify the DFS domain information automatically\n* `skip_dfs`: Whether to skip doing any DFS resolution, useful if there is a bug or you don't want to waste any roundtrip requesting referrals\n* `auth_protocol`: The authentication protocol to use; `negotiate` (default), `kerberos`, or `ntlm`\n* `require_secure_negotiate`: Control whether the client validates the negotiation info when connecting to a share (default: `True`).\n * More information can be found on [SMB3 Secure Dialect Negotiation](https://docs.microsoft.com/en-us/archive/blogs/openspecification/smb3-secure-dialect-negotiation)\n\nAs well as setting the default credentials on the `ClientConfig` you can also\nspecify the credentials and other connection parameters on each `smbclient`\nfunction or when registering a new server. These functions accept the\nfollowing kwargs:\n\n* `username`: The username used to connect to the share\n* `password`: The password used to connect to the share\n* `port`: Override the default port (`445`) to connect to\n* `encrypt`: Whether to force encryption on the connection, requires SMBv3 or newer on the remote server (default: `False`)\n* `connection_timeout`: Override the connection timeout in seconds (default: `60`)\n\nIf using Kerberos authentication and a Kerberos ticket has already set by\n`kinit` then `smbclient` will automatically use those credentials without\nhaving to be explicitly set. If no ticket has been retrieved or you wish to use\ndifferent credentials then set the default credentials on the `ClientConfig`\nor specify `username` and `password` on the first request to the server.\n\nFor example I only need to set the credentials on the first request to create\nthe directory and not for the subsequent file creation in that dir.\n\n```python\nimport smbclient\n\n# Optional - specify the default credentials to use on the global config object\nsmbclient.ClientConfig(username='user', password='pass')\n\n# Optional - register the credentials with a server (overrides ClientConfig for that server)\nsmbclient.register_session(\"server\", username=\"user\", password=\"pass\")\n\nsmbclient.mkdir(r\"\\\\server\\share\\directory\", username=\"user\", password=\"pass\")\n\nwith smbclient.open_file(r\"\\\\server\\share\\directory\\file.txt\", mode=\"w\") as fd:\n fd.write(u\"file contents\")\n```\n\nIf you wish to reset the cache you can either start a new Python process or\ncall `smbclient.reset_connection_cache()` to close all the connections that\nhave been cached by the client.\n\n\n## Logging\n\nThis library makes use of the builtin Python logging facilities. Log messages\nare logged to the `smbprotocol` named logger as well as `smbprotocol.*` where\n`*` is each python script in the `smbprotocol` directory.\n\nThese logs are really useful when debugging issues as they give you a more\nstep by step snapshot of what it is doing and what may be going wrong. The\ndebug side will also print out a human readable string of each SMB packet that\nis sent out from the client so it can get very verbose.\n\n\n## Testing\n\nTo this module, you need to install some pre-requisites first. This can be done\nby running;\n\n```bash\n# Install in current environment.\n# Recommend to have virtual environment installed at .venv path.\npip install -r requirements-dev.txt\npip install -e .\n\n# you can also run tox by installing tox\npip install tox\n```\n\nFrom there to run the basic tests run;\n\n```bash\npy.test -v --cov smbprotocol --cov-report term-missing\n\n# or with tox for dedicated virtual environments and multiple Python versions.\ntox\n```\n\nBefore sending the code for review, besides making sure all the test pass,\ncheck that the code complies with the coding standards:\n\n```bash\nsource ./build_helpers/lib.sh\n\nlib::sanity::run\n```\n\nThere are extra tests that only run when certain environment variables are set.\nTo run these tests set the following variables;\n\n* `SMB_USER`: The username to authenticate with\n* `SMB_PASSWORD`: The password to authenticate with\n* `SMB_SERVER`: The IP or hostname of the server to authenticate with\n* `SMB_PORT`: The port the SMB server is listening on, default is `445`\n* `SMB_SHARE`: The name of the share to connect to, a share with this name must exist as well as a share with the name`$SMB_SHARE-encrypted` must also exist that forces encryption\n\nFrom here running `tox` or `py.test` with these environment variables set will\nactivate the integration tests.\n\nThis requires either Windows 10 or Server 2016 as they support Dialect 3.1.1\nwhich is required by the tests.\n\nIf you don't have access to a Windows host, you can use Docker to setup a\nSamba container and use that as part of the tests. To do so run the following\nbash commands;\n\n```bash\nsource ./build_helpers/lib.sh\n\nlib::setup::smb_server\n```\n\nThis command will also set the required `SMB_*` env vars used in testing.\n\n\n## Backlog\n\nHere is a list of features that I would like to incorporate, PRs are welcome\nif you want to implement them yourself;\n\n* Multiple channel support to speed up large data transfers\n* Lots and lots more...\n",
"bugtrack_url": null,
"license": "MIT License Copyright (c) 2017 Jordan Borean, Red Hat Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the \"Software\"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED \"AS IS\", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ",
"summary": "Interact with a server using the SMB 2/3 Protocol",
"version": "1.14.0",
"project_urls": {
"homepage": "https://github.com/jborean93/smbprotocol"
},
"split_keywords": [
"smb",
" smb2",
" smb3",
" cifs",
" python"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "585ec6b03b4cd151c5c4efc284350d5b4c96c32627f983ec50d9f3f96a563467",
"md5": "7b778fb8806867a6922b57c1432cd807",
"sha256": "e9a9c88d35b8f758fe03f27278ebb956743842e99794bb280ea7ea00293e7168"
},
"downloads": -1,
"filename": "smbprotocol-1.14.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "7b778fb8806867a6922b57c1432cd807",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 125160,
"upload_time": "2024-08-25T21:26:32",
"upload_time_iso_8601": "2024-08-25T21:26:32.113755Z",
"url": "https://files.pythonhosted.org/packages/58/5e/c6b03b4cd151c5c4efc284350d5b4c96c32627f983ec50d9f3f96a563467/smbprotocol-1.14.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "410dd178f651591de45607d6dfc5637e7dcd8c5190b137275303cda005d9a13a",
"md5": "ca5c38cbe82d7995ed2147021a7d2950",
"sha256": "4918ba10a0b0b344308e7a043c1c6741bf7282c3937059a5852de702d3b684da"
},
"downloads": -1,
"filename": "smbprotocol-1.14.0.tar.gz",
"has_sig": false,
"md5_digest": "ca5c38cbe82d7995ed2147021a7d2950",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.8",
"size": 182800,
"upload_time": "2024-08-25T21:26:33",
"upload_time_iso_8601": "2024-08-25T21:26:33.640355Z",
"url": "https://files.pythonhosted.org/packages/41/0d/d178f651591de45607d6dfc5637e7dcd8c5190b137275303cda005d9a13a/smbprotocol-1.14.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-08-25 21:26:33",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "jborean93",
"github_project": "smbprotocol",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "smbprotocol"
}
