2016-07-19 1:21 GMT+03:00 Robin H. Johnson <robbat2@xxxxxxxxxx>: > On Mon, Jul 18, 2016 at 10:48:16AM +0300, Victor Efimov wrote: >> <ListAllMyBucketsResult >> xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Owner><ID>someowner</ID><DisplayName>SOMEOWNER</DisplayName></Owner> >> >> note the "someowner" is used as id. >> Problem that S3-compatible library that I use crashes on this, it >> expects 64 character hex string. >> >> According to S3 docs owner id indeed is 64 char hex string: >> http://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html >> === >> The canonical user ID is a long string, such as >> 79a59df900b949e55d96a1e698fbacedfd6e09d98eacf8f8d5218e7cd47ef2be. >> === > It's an example where it happens to be a 64-hex string, not a > specification that says it MUST be a 64-hex string. > > The specification implied by this page is simply it's a long string (and > opaque). ok, I found another page: http://docs.aws.amazon.com/AmazonS3/latest/dev/example-walkthroughs-managing-access-example4.html ==== The canonical user ID is the Amazon S3–only concept. It is s 64-character obfuscated version of the account ID. ==== now they say it's length is 64 > >> How to qualify this? >> 3) Bug in library which should not validate this field that way? > This is definitely a library bug. It should not be making assumptions > about the nature or formatting of the ID string. > > -- > Robin Hugh Johnson > Gentoo Linux: Dev, Infra Lead, Foundation Trustee & Treasurer > E-Mail : robbat2@xxxxxxxxxx > GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 > GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 > _______________________________________________ > ceph-users mailing list > ceph-users@xxxxxxxxxxxxxx > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com