#182 Error in s3cfg parser for add_headers

[Roland Dunker]

Hello,

I tried to use s3cmd with “Server Side Encryption with KMS managed key” and add the value “add_headers = x-amz-server-side-encryption:aws:kms” in .s3cfg. When I try to upload a file I got following Error:

DEBUG: Unicodising '/usr/bin/s3cmd' using UTF-8
DEBUG: Unicodising 'put' using UTF-8
DEBUG: Unicodising 'information.xml.1' using UTF-8
DEBUG: Unicodising 's3://obs-1000026418-sapfics-poc-backup/' using UTF-8
DEBUG: Unicodising '--debug' using UTF-8
Invoked as: /usr/bin/s3cmd put information.xml.1 s3://obs-1000026418-sapfics-poc-backup/ --debug
Problem: ValueError: too many values to unpack
S3cmd: 2.0.0
python: 2.7.13 (default, Jan 11 2017, 10:56:06) [GCC]
environment LANG=en_US.UTF-8

Traceback (most recent call last):
File "/usr/bin/s3cmd", line 2996, in <module>
rc = main()
File "/usr/bin/s3cmd", line 2719, in main
cfg = Config(options.config, options.access_key, options.secret_key, options.access_token)
File "/usr/lib/python2.7/site-packages/S3/Config.py", line 156, in init
self.read_config_file(configfile)
File "/usr/lib/python2.7/site-packages/S3/Config.py", line 287, in read_config_file
(key, value) = option.split(':')
ValueError: too many values to unpack</module>

The command option s3cmd --add-header=x-amz-server-side-encryption:aws:kms works.
​

[Roland Dunker]

thank you very much.

Von: Florent Viard fviard@users.sourceforge.net
Gesendet: Mittwoch, 8. April 2020 02:15
An: [s3tools:bugs] 182@bugs.s3tools.p.re.sourceforge.net
Betreff: [s3tools:bugs] #182 Error in s3cfg parser for add_headers

• status: open --> closed-fixed
• Comment:

Thank you for your report.
Indeed, there was a bug.
I duplicated your issue on the following ticket of github:
https://github.com/s3tools/s3cmd/issues/1087
(fyi, it is on the github platform that the main developpement is going on now)

I have pushed a fix for this issue that is in the "MASTER" version in github, but if you want to use a release with the issue fixed, please wait for the next release to come, that will probably be 2.2.0.

---

[bugs:#182]https://sourceforge.net/p/s3tools/bugs/182/ Error in s3cfg parser for add_headers

Status: closed-fixed
Group: Malfunction
Labels: s3cmd
Created: Wed Apr 24, 2019 09:53 AM UTC by Roland Dunker
Last Updated: Wed Apr 24, 2019 09:53 AM UTC
Owner: nobody

Hello,

I tried to use s3cmd with “Server Side Encryption with KMS managed key” and add the value “add_headers = x-amz-server-side-encryption:aws:kms” in .s3cfg. When I try to upload a file I got following Error:

DEBUG: Unicodising '/usr/bin/s3cmd' using UTF-8
DEBUG: Unicodising 'put' using UTF-8
DEBUG: Unicodising 'information.xml.1' using UTF-8
DEBUG: Unicodising 's3://obs-1000026418-sapfics-poc-backup/' using UTF-8
DEBUG: Unicodising '--debug' using UTF-8
Invoked as: /usr/bin/s3cmd put information.xml.1 s3://obs-1000026418-sapfics-poc-backup/ --debug
Problem: ValueError: too many values to unpack
S3cmd: 2.0.0
python: 2.7.13 (default, Jan 11 2017, 10:56:06) [GCC]
environment LANG=en_US.UTF-8

Traceback (most recent call last):
File "/usr/bin/s3cmd", line 2996, in <module>
rc = main()
File "/usr/bin/s3cmd", line 2719, in main
cfg = Config(options.config, options.access_key, options.secret_key, options.access_token)
File "/usr/lib/python2.7/site-packages/S3/Config.py", line 156, in init
self.read_config_file(configfile)
File "/usr/lib/python2.7/site-packages/S3/Config.py", line 287, in read_config_file
(key, value) = option.split(':')
ValueError: too many values to unpack</module>

The command option s3cmd --add-header=x-amz-server-side-encryption:aws:kms works.
​

---

Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/s3tools/bugs/182/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

[Florent Viard]

Thank you for your report.
Indeed, there was a bug.
I duplicated your issue on the following ticket of github:
https://github.com/s3tools/s3cmd/issues/1087
(fyi, it is on the github platform that the main developpement is going on now)

I have pushed a fix for this issue that is in the "MASTER" version in github, but if you want to use a release with the issue fixed, please wait for the next release to come, that will probably be 2.2.0.