Page 1 of 20 1234511 ... LastLast
Results 1 to 15 of 292
  1. #1
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)

    Looking inside your screenshots



    Donate to Remove Ads, Get ShoutBawx - Elite Forum Access
    Updated 12/09 (the watermarking apparently started in 2007):

    DISCLAIMER: This thread post contains detailed information on how to view a hidden watermark which has been verified to exist embeded in JPG screenshots produced by the WoW client. The watermark itself includes, encoded in unencrypted bytes, the user's account name (\World of Warcraft\WTF\Account\), an HH:MM timestamp and the IP address of the server. If you do not care about Blizzard secretly watermarking your screenshots without any specific prior notification in the ToS or EULA, then this post probably isn't for you Thank you for your attention.

    Dear everyone

    This post may have been moved to WoW General, but it still remains an exploit - one which is used against us...

    1) Go somewhere where there aren't any (or a lot) of textures. I used the druid blink bug to go to the north end of the world but you should go below Dalaran in Crystalsong Forest, as bluesius suggested, because you will get a better screenshot if you stick your face in the pure white trees.

    2) Type:

    /console SET screenshotQuality "9"

    Make sure you use 9, not 10.

    3) Take a few screenshots of the clear, no textures, white area by zooming into a tree and hitting ALT Z, so that your entire screen is white.



    4) Open this image in an image editing program like IrfanView (it's freeware), click CTRL+E, select the Sharpening filter, use the highest possible sharpening value (99) and click OK. Now do this two more times, again: CTRL+E, Sharpen 99, OK.

    5) You are now looking at your character's WoW watermark / custom bar-code / qr code look-a-like / call it what you will:



    Apparently, each user has a different set of these repeatable patterns, which contain account and realm information, and it looks like if they are scanned by software that recognizes them, they can reveal our character's account name/id, the time of the screenshot and the the full information of the realm, including its IP address (think "private servers").

    Note that if your screen resolution is too high, the pattern will look something like this:

    (larger footprint)

    The pattern, which consists of approximately 88 bytes of data, repeats itself many times depending on the resolution of your screen. See below for a colored representation: the account id and realm information are depicted in red and the current time (seconds not included) is depicted in blue:




    IMPORTANT NOTE: IF YOU CAN'T BOTHER READING ANYTHING ELSE, READ THIS:

    The secret watermark which is being intentionally embedded inside WoW generated screenshots below top quality, DOES NOT CONTAIN the account password, the IP address of the user or any personal information like name/surname etc. It does contain the account ID, a timestamp and the IP address of the current realm. It can be used by malicious hackers to link alt. characters to accounts and target specific spam or scam attacks, and it can be used by Blizzard to track down private WoW servers.

    Based on Blizzard's ToS (http://us.blizzard.com/en-us/company/legal/wow_tou.html), Blizzard is allowed to communicate information about our hard drive, CPU, operating systems, IP addresses, running tasks, account name and current time and date. It never mentions anything though about embedding some of these data into every screenshot we capture using the WoW printscreen tool. The users [mistakenly] assume that Blizzard will use a safe channel via battle.net, not our public screenshots that we share with the world, unaware of their secret contents. This unencrypted watermarking mechanism fails to protect our privacy, not from Blizzard employees (they already know everything about our computer systems), but from malicious hackers looking for something or someone to take advantage of.

    If they only wanted it for screenshot-authenticity reasons, as some argued, they could have just watermarked a unique version of their logo or perhaps an encrypted key. But we found account and realm information which means that its aim is to secretly track the users, in addition to the known tracking methods that we agree to in the ToS.

    _Mike, schlumpf and Master674 have managed to disassemble the watermark data and help us verify which pieces of information are contained inside. Do note that this covert watermarking has been confirmed, by multiple sources, to have started immediately or soon after Patch 2.1.0 in 2007 (before the Activision deal), which introduced JPG screenshots for the first time (http://us.battle.net/wow/en/game/patch-notes/2-1-0), so you may want to delete/remove from the public domain all your JPG screenshots captured by WoW. Sorry Activision haters, looks like this one was on Blizzard

    The contained information can be easily recovered and decrypted by malicious hackers (if we did it, so can they). For example, someone could use this to identify which account holds which characters and perhaps stalk and annoy its user, or help perpetrators choose their phishing victims with a more targeted approach. They could unleash Web spider bots scanning for WoW screenshots, decode their hidden watermark data and quickly create a comprehensive database of which account has which alts in it, that they can then sell to anyone interested. Perhaps someone is already using this since the watermark has been around for five years already.

    Bear in mind that when this started, back in 2007, we were still using our account name to login so, before the battle.net conversion in 2009, the watermarks actually had really sensitive information... Between May 22, 2007 and November 11, 2009, any malicious hacker who knew about this could have used a screenshot of a lucrative character to find their actual username & active realm and then either try to scam them out of their password, or just brute-force it.

    It looks like when Blizzard decided to add JPG screenshots into the WoW client, they also teamed up with Digimarc (http://www.digimarc.com) to provide us this wonderful service of secretly tagging our in-game screenshots with our account and realm information. Although it has not yet been verified, it is possible that Blizzard is using an automated monitoring service which downloads image files from various Internet sites and checks them for the presence of their embedded digital watermark data, kindly provided by Digimarc: http://www.google.co.uk/patents/US7653210

    I must repeat, once more, that these patterns are not "random artifacts", because random artifacts don't produce account IDs: http://www.ownedcore.com/forums/worl...ml#post2493377 (Looking inside your screenshots)

    Thanks to _Mike, we also verified that there is no pattern included in high quality screenshots like TGA and JPG/10. So, in order to avoid any further watermarking, type: /console SET screenshotQuality "10" which will set the quality of your screenshots to the maximum and create screenshots that do not include the watermark.

    l0l1dk has developed a tool to disable the addition of watermarks in the lower quality screenshots but use it at your own risk/responsibility because it could corrupt the WoW client, which could then require a clean re-installation of the game (it's also against the ToS). It is much simpler to just set the JPG quality to max.

    Finally, a lot of people are asking how we managed to decode the watermark pattern. Well it took a lot of teamwork, which you can find in the next pages here, and we came up with two source codes which successfully read the pattern data:

    Java: http://www.ownedcore.com/forums/worl...ml#post2492716

    C#: http://www.ownedcore.com/forums/worl...ml#post2493450

    Try it yourselves. Read the rest of the thread for more information. If you have any comments, ideas or suggestions please share. Politeness is appreciated.
    Attached Images Attached Images
    Last edited by Sendatsu; 09-13-2012 at 01:35 PM.

  2. #2
    Elite User Pickle Tickler for a nickle

    CoreCoins User

    SniffingPickles's Avatar
    Reputation
    482
    Join Date
    Jul 2012
    Posts
    1,147
    CoreCoins
    9194

    Trade Feedbacks

    Status
    Superior trader
    Positive
    4 (100%)
    Negative
    0 (0%)
    upload your images on an external image hosting site: imgur.com


    No one responded because they couldn't see them

  3. #3
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Quote Originally Posted by Snicklesworth View Post
    upload your images on an external image hosting site: imgur.com


    No one responded because they couldn't see them
    Thank you.

    *UPDATED*
    Last edited by Sendatsu; 09-11-2012 at 12:56 PM.

  4. #4
    Contributor
    Reputation
    201
    Join Date
    Dec 2007
    Posts
    398
    CoreCoins
    18

    Trade Feedbacks

    Status
    Superior trader
    Positive
    1 (100%)
    Negative
    0 (0%)
    For quite a while i suspected this kind of tracking was possible. thank you for researching & proving it to be true!
    +cookies your way

    Edit: To people who do not understand the importance, this shows how Blizzard has possible ways of tracking screenshots to the related accounts even with name/character model / etc censored out. It also provides knowledgeable people with more ways to censor the image to prevent the above from happening.

  5. #5
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Quote Originally Posted by 403Forbidden View Post
    For quite a while i suspected this kind of tracking was possible. thank you for researching & proving it to be true!
    +cookies your way

    Edit: To people who do not understand the importance, this shows how Blizzard has possible ways of tracking screenshots to the related accounts even with name/character model / etc censored out. It also provides knowledgeable people with more ways to censor the image to prevent the above from happening.
    Thank you! If you actually want to censor your screenshot, apart from the character name and chat, you also have to blur out the shape of the pattern in the last image (http://i.imgur.com/3FDgG.jpg). It's like a capital T merged with an inverted capital T (dots added for centering), so it basically looks like an Ξ with a smaller middle line for small resolutions and a larger middle line for large resolutions:


    ___
    ..|..
    --!--


    It's always in the middle of your screen, and always the same pattern per character. That is why my screenshots are so low-res, I couldn't afford them being recognized.
    Last edited by Sendatsu; 09-11-2012 at 12:58 PM.

  6. #6
    Contributor
    Reputation
    253
    Join Date
    Jun 2012
    Location
    FR
    Posts
    185
    CoreCoins
    127

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    For me it looks like JPG compression artifacts, remember thath JPG is a highly destructive algorithm.
    Try entering this :

    /console SET screenshotFormat "tga"
    /console SET screenshotQuality "12"
    Redo your method and we'll see.

  7. #7
    Contributor
    Reputation
    227
    Join Date
    Mar 2007
    Posts
    153
    CoreCoins
    2

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Maybe this is just a watermark to prove it's from WoW itself and not a manipulated image (even the pattern changes).
    But i will try to reproduce this and then I will try to decode it somehow.

    // Edit

    Got those patterns too. But i think - like others in this thread told already - this is just because the jpeg compression. Can't see any difference on two different accounts on the same place.
    Last edited by allesist; 09-08-2012 at 01:06 PM.

  8. #8
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Quote Originally Posted by AraiXplorer View Post
    For me it looks like JPG compression artifacts, remember thath JPG is a highly destructive algorithm.
    Try entering this :



    Redo your method and we'll see.
    Thank you for the suggestion. I just experimented with all the qualities of JPG and the patterns disappear only at quality 10 (there is no higher quality than 10). Qualities 1-9 include these patterns. The lossless TGA format has no patterns in any of the qualities.

    If this indeed was JPG artifacts I would expect them to spread throughout the image. If an image format expert can give some insight on this it would be great.

    For now I am switching to JPG quality 10 until I know more. Thanks for the tip.

  9. #9
    Contributor
    Reputation
    253
    Join Date
    Jun 2012
    Location
    FR
    Posts
    185
    CoreCoins
    127

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Long story short : JPG is bad, go PNG people.

    @Frito : Tinfoil hats off to you

  10. #10
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Quote Originally Posted by Fritomaster View Post
    Since the human eye is much more sensitive to luminance than chrominance, you can afford to discard much more information about an image’s chrominance, especially the higher frequencies.
    We agree that JPG removes a lot of information from the image to make it smaller, but from all over the image, not always just the middle Ξ section.

    The number used to calculate the quantization constants is stored in the JPEG image file’s header, making decoding of the coefficients possible.
    The file header is not visible in the image, so it's not that.

    Since the output file contains Huffman codes, the original encoding information (like the Huffman tree or the data table generated from the Huffman tree) must also be stored in the output file in order for decompression to be possible. (...) One drawback is that the actual output file is larger than it needs to be. This is because information about the compressed data’s frequencies must also be stored in order to make data decompression possible.
    Ok so let's say that what I'm looking at is the storage of a Huffman tree embedded into the graphics. How can two different images (http://i.imgur.com/nClSc.jpg & http://i.imgur.com/0PWKW.jpg) have the same hidden pattern inside? They are different images so a different Huffman tree must have been created for each. I merged the top part of the first image with the bottom part of the second and I found the same pattern repeated 5 times in 3 different rows (2-1-2).

    Any suggestions? Politeness is appreciated

  11. #11
    Master Sergeant pac7's Avatar
    Reputation
    21
    Join Date
    Oct 2008
    Posts
    76
    CoreCoins
    97

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Interesting find, rep+
    Blizz has alot of cash to develop such complex algorythms to track you.

    I always knew they were monitoring me.
    Last edited by pac7; 09-08-2012 at 04:59 PM.

  12. #12
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Quote Originally Posted by Fritomaster View Post
    But here you go I took the "Secret Barcode" and I went ahead and converted every color in the pattern to a more noticeable one.
    Feel free to decode my account information and I'll be waiting on my ban from blizzard.
    http://img12.imageshack.us/img12/8409/secretsa.png
    The screenshot you just posted is from a high resolution monitor. Can you confirm?
    Last edited by Sendatsu; 09-09-2012 at 11:31 PM.

  13. #13
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    You see, I was going through my old screenshots and I found one from early 2011 where I print-screened a buggy field that was all light brown:

    http://i.imgur.com/QFugi.jpg

    I then sharpened the image and found this pattern:

    http://i.imgur.com/auofc.jpg

    This pattern is completely different from the current pattern that I found on my screenshots from yesterday and today (http://i.imgur.com/3FDgG.jpg).

    Update: this happens when the screen resolution is too high because the pattern tries to make sure it will be visible enough so that at least one complete piece of it survives after any image modifications.

    You asked me why I sharpen the image. Well if you zoom into my sharpened image above, you will see this:

    ===> http://i.imgur.com/Qc5ME.jpg <===

    Does this remind you of something? Maybe this:

    http://i.imgur.com/Okxgz.jpg

    QR codes are basically visual representations of binary digits which, when translated into ASCII, form text. So, these patterns that I found in the images are not just random artifacts or removal of colors that the human eye can't see: they are actually machine readable data.

    You are claiming that this extra padding has been added by the JPG compression algorithm Blizzard is using to assist with the decompression of the screenshots, and I respect that. I just don't see the reason why this extra "padding" has to be added in such a visible place in all images regardless of their compression needs. I captured a black screen with JPG quality 9 and it created a larger file than a JPG quality 10, because JPGs 1-9 also contain this extra padding inside, whereas 10s don't.

    This could just be a method Blizzard is using to decrease the size of really colorful files, thinking that adding this padding (which might only contain decompression information) is worth it, because who ever captures monochrome screens, right? :P

    I was a bit worried to discover a machine readable data pattern (custom bar-code, as I called it :P) hidden within every screenshot I shot since 2010.
    1) I still don't understand why the new pattern is comprised of the same 3 elements repeating again and again (wasn't one time enough?).
    2) I also don't understand why two different images produced the same patterns (if it were just decompression information, shouldn't it be different?).
    3) And finally, if Blizzard indeed came up with their own proprietary JPG compression algorithm that uses padded pattern-data to assist with the decompression, how will all the image software applications of the world know how to understand this custom system if Blizzard never advertised it? Because I have never before seen so much intentional "noise" (ehem) inside a jpg file I sharpened.

    Anyhow, I don't know how you translate these codes into binary digits and text but I would be really interested to ask a Blizzard developer what information is stored inside.
    Last edited by Sendatsu; 09-09-2012 at 11:37 PM.

  14. #14
    Contributor
    Reputation
    200
    Join Date
    Sep 2012
    Posts
    95
    CoreCoins
    1

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    Quote Originally Posted by wowsc4p3 View Post
    Seriously, if it was some kind of tracking system, they'd use EXIF fields which JPGs can contain. Screenshots don't look malformed, and such, the data you're viewing has been generated using the input as an image, and anything not visible on the screenshot; isn't on the screenshot. Simple as.
    I couldn't find any patterns by sharpening your image which either means a) you used JPG quality 10 or b) it was too colorful for a human to notice.

    If they used EXIF/IPTC comments, anyone would be able to read their extra data in plain text format. By embedding the data inside the screenshot (by padding it among its bytes while at the same time keeping it as invisible a possible), they manage to create a mechanism where only their programmers are able to extract the hidden information contained inside (like steganography does). Still, this is "security by obscurity". If a hacker is dedicated enough, they can easily reserve-engineer it and figure out what it says.

    Screenshots don't look malformed when you are viewing a lot of colors, but when it's monochrome it can be easily spotted. By using sharpening techniques you can "single out" the hidden data and can easily see that they create a standardized pattern that resembles a machine readable code.

    Just because you can't see IR light, doesn't mean your remote control magically changes the channels of your TV every time you press a button. The hidden data are there; I just wonder what they hold.
    Last edited by Sendatsu; 09-08-2012 at 08:22 PM.

  15. #15
    Private
    Reputation
    69
    Join Date
    Jun 2012
    Posts
    12
    CoreCoins
    8

    Trade Feedbacks

    Status
    n/a
    Positive
    0 (0%)
    Negative
    0 (0%)
    For those of you who want to check it out... You don't have to take several screenshots and merge together. Just fly up to the world ceiling and take a screenshot just below the horizon.

    Also, if you turn down the screenshot quality in-game you can see the effect without using any other image editing software. (Just remember to set it back to 10 after.)
    /console set screenshotQuality 1
    Last edited by McYawgi; 09-11-2012 at 02:10 PM.

 

 
Page 1 of 20 1234511 ... LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT -4. The time now is 03:46 PM. Powered by vBulletin® Version 4.2.0
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Content Relevant URLs by vBSEO Resources saved on this page: MySQL 20.00%
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2014 DragonByte Technologies Ltd.
Digital Point modules: Sphinx-based search

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113