diff --git a/next/pw-change.html b/next/pw-change.html index 4c8a49f99..eac38a34f 100644 --- a/next/pw-change.html +++ b/next/pw-change.html @@ -437,31 +437,44 @@ for submissions ONLY WHEN THE CONTEST IS open IOCCC submit server may be offline and unreachable as a website.

To login and change your password, open https://submit.ioccc.org -in your browser. It should look like this:

-

submit server login screen

+in your browser. The important lines should say:

+
+

Status: Not logged in.
+Username: Enter Username
+Password: Enter Password

+

The username is the UUID you are provided when a judge replies to your request to register for the IOCCC and the password is the initial password you are given. Click “Login”.

After you log in, if this is the first time you have logged in with this UUID, you will be required to change your password. Assuming everything is fine, that would look something like:

-

submit server initial login requires your password to be changed

-

As you can see, on your first login you MUST change your password. If you do -not do this within 72 hours YOUR ACCOUNT WILL BE CLOSED and you’ll have to -register again! In that case, it will say something like this:

+

It will then tell you that you MUST change your password within a certain +time (that it will give you) and then tell you the following about the new +password:

-

ERROR: Sorry (tm Canada 🇨🇦) you cannot login at this time.

+

Please enter your current password, a new password, and then reenter the same +new password.
+Your password MUST be:
+- At least 15 characters long
+- At most 40 characters long
+- NOT contain nor be a sub-string of the current password
+- NOT contain nor be a sub-string of your username
+- New password must NOT have been Pwned

+

Pwned passwords are passwords that have been previously exposed in some published data breach.

+
+

Again, if you do not change your password within 72 hours YOUR ACCOUNT WILL BE +CLOSED and you’ll have to register again! In that case it’ll say something +like:

+
+

ERROR: Sorry (tm Canada 🇨🇦) you cannot login at this time.

Assuming you did login in time, you should put in your login (UUID username), your old (initial) password and a new password and then click “Change Password”.

NOTE: if you have put in your old password, you’ll get the following error:

-

ERROR: Password not changed
-ERROR: invalid old password

+

ERROR: Password not changed
+ERROR: invalid old password

Once you’ve changed your password successfully you will be able to log in again with your UUID username and new password. When you have done this it will diff --git a/next/pw-change.md b/next/pw-change.md index 784f3aec1..e31cff818 100644 --- a/next/pw-change.md +++ b/next/pw-change.md @@ -16,11 +16,11 @@ for submissions **ONLY WHEN THE CONTEST IS [open](../faq.html#open)**. See may be offline and unreachable as a website. To login and change your password, open [https://submit.ioccc.org](https://submit.ioccc.org) -in your browser. It should look like this: +in your browser. The important lines should say: -submit server login screen +> **Status**: Not logged in.
+> **Username**: Enter Username
+> **Password**: Enter Password The username is the UUID you are provided when a judge replies to your request to register for the IOCCC and the password is the initial password you are @@ -30,23 +30,34 @@ After you log in, if this is the first time you have logged in with this UUID, you will be required to change your password. Assuming everything is fine, that would look something like: -submit server initial login requires your password to be changed +It will then tell you that you **MUST** change your password within a certain +time (that it will give you) and then tell you the following about the new +password: -As you can see, on your first login you **MUST** change your password. If you do -not do this within 72 hours **YOUR ACCOUNT WILL BE CLOSED** and you'll have to -register again! In that case, it will say something like this: +> Please enter your current password, a new password, and then reenter the same +new password.
+> Your password MUST be:
+> - At least 15 characters long
+> - At most 40 characters long
+> - NOT contain nor be a sub-string of the current password
+> - NOT contain nor be a sub-string of your username
+> - New password must NOT have been [Pwned](https://haveibeenpwned.com/Passwords) +> +> [Pwned](https://haveibeenpwned.com/Passwords) passwords are passwords that have been previously exposed in some published data breach. -> ERROR: Sorry (tm Canada 🇨🇦) you cannot login at this time. +Again, if you do not change your password within 72 hours **YOUR ACCOUNT WILL BE +CLOSED** and you'll have to register again! In that case it'll say something +like: + +> **ERROR: Sorry (tm Canada 🇨🇦) you cannot login at this time.** Assuming you did login in time, you should put in your login (UUID username), your old (initial) password and a new password and then click "Change Password". **NOTE**: if you have put in your old password, you'll get the following error: -> ERROR: Password not changed
-> ERROR: invalid old password +> **ERROR: Password not changed**
+> **ERROR: invalid old password** Once you've changed your password successfully you will be able to log in again with your UUID username and new password. When you have done this it will diff --git a/next/register.html b/next/register.html index f26e31688..3288e14c2 100644 --- a/next/register.html +++ b/next/register.html @@ -441,13 +441,14 @@ in order to register for the IOCCC.

  • Click the ((Next >>)) button
  • NOTE: For submissions with multiple authors, only one author needs to subscribe.

    -

    signup for a mailing list screenshot

    -

    After clicking ((Next >>)), you will be notified that you will receive an email:

    -

    verify your email notification screenshot

    +

    The first step of registering is to put in your email address in the field: +Your Email Address. Then select from the drop-down what you would like to do, +in this case you want to Subscribe.

    +

    After clicking ((Next >>)) and you will be notified that you will receive an +email. It will tell you that they have sent an email to verify your address. +Remember that if you don’t receive it in a few minutes you should check your +Spam or Junk folders in case your email client or your ISP marks as +spam.

    @@ -468,19 +469,14 @@ you have tried a few times, Contact the IOCCC to a IOCCC judges for assistance.

    This email will contain a URL of the form: https://www.freelists.org/v/ioccc28-reg/SOME-RANDOM-STUFF.

    -

    Click on that link. The email might look the below:

    -

    Subscription consent email screenshot

    NOTE: If you prefer to NOT click links in email, simply copy that URL from your “Subscription consent email” and paste it into your browser.

    +

    Note that the email should be from FreeLists List Manager.

    Step D: Confirm your email click

    -

    In your browser, for the link referenced in Step C, click the ((Next >>)) button.

    -

    confirm your email screenshot

    +

    In your browser, for the link referenced in Step C, click the +((Next >>)) button. It is the page with the header text of Verify your email.

    @@ -490,15 +486,14 @@ URL from your “Subscription consent email” and paste it into your browser.Have read, understand, and agree to their “Privacy Policy”
  • Are the owner or authorized user of the email you registered
  • -

    Once you have done this by clicking the 3 checkboxes, click the ((Next >>)) -button:

    -

    complete subscription screenshot

    -

    After clicking ((Next >>)), you will be notified that you will receive an email:

    -

    registration is complete screenshot

    +

    Once you have done this by clicking the 3 tick boxes (or if you prefer, +checkboxes), click the ((Next >>)) button.

    +

    After clicking ((Next >>)), you will be notified that you will receive an +email. The website should say:

    +
    +

    All set! The last stage of the process has been started. You should receive a +verification email within a few minutes.

    +

    Step F: Read the Welcome email

    @@ -506,9 +501,6 @@ button:

    (ecartis@freelists.org) with the subject:

        Welcome to 'ioccc28-reg'

    Read the “Welcome” email.

    -

    Welcome email screenshot

    NOTE: The “Welcome” email is usually sent by the FreeLists List Manager within a minute after clicking the ((Next >>)) button. If you don’t see the “Welcome” email, check your spam folder.

    diff --git a/next/register.md b/next/register.md index 128dde047..c04f8f37c 100644 --- a/next/register.md +++ b/next/register.md @@ -22,16 +22,15 @@ For details see the "[how the contest status impacts registration](#status_impac **NOTE**: For submissions with multiple authors, only one author needs to subscribe. -signup for a mailing list screenshot - -After clicking **((Next >>))**, you will be notified that you will receive an email: - -verify your email notification screenshot +The first step of registering is to put in your email address in the field: +`Your Email Address`. Then select from the drop-down what you would like to do, +in this case you want to **Subscribe**. +After clicking **((Next >>))** and you will be notified that you will receive an +email. It will tell you that they have sent an email to verify your address. +Remember that if you don't receive it in a few minutes you should check your +**Spam** or **Junk** folders in case your email client or your ISP marks as +spam.
    ## Step C: Open the Subscription consent email message @@ -59,27 +58,18 @@ you have tried a few times, [Contact the IOCCC](../contact.html) to ask the This email will contain a URL of the form: `https://www.freelists.org/v/ioccc28-reg/SOME-RANDOM-STUFF`. -Click on that link. The email might look the below: - - -Subscription consent email screenshot - **NOTE**: If you prefer to **NOT** click links in email, simply copy that URL from your "Subscription consent email" and paste it into your browser. +Note that the email should be from `FreeLists List Manager`.
    ## Step D: Confirm your email click
    -In your browser, for the link referenced in [Step C](#step_c), click the **((Next >>))** button. - -confirm your email screenshot - +In your browser, for the link referenced in [Step C](#step_c), click the +**((Next >>))** button. It is the page with the header text of `Verify your +email`.
    ## Step E: Verify you have read the mailing list polices and that you consent to receiving emails @@ -91,18 +81,14 @@ The FreeLists service requires that you verify that you: - Have read, understand, and agree to their "_Privacy Policy_" - Are the owner or authorized user of the email you registered -Once you have done this by clicking the 3 checkboxes, click the **((Next >>))** -button: +Once you have done this by clicking the 3 tick boxes (or if you prefer, +checkboxes), click the **((Next >>))** button. -complete subscription screenshot +After clicking **((Next >>))**, you will be notified that you will receive an +email. The website should say: -After clicking **((Next >>))**, you will be notified that you will receive an email: - -registration is complete screenshot +> All set! The last stage of the process has been started. You should receive a +verification email within a few minutes.
    @@ -118,10 +104,6 @@ You should receive an automated Welcome message from the FreeLists List Manager Read the "Welcome" email. -Welcome email screenshot - **NOTE**: The "Welcome" email is usually sent by the FreeLists List Manager within a minute after clicking the **((Next >>))** button. If you don't see the "Welcome" email, check your spam folder. diff --git a/next/submit.html b/next/submit.html index efb065e1a..6a5da1d9f 100644 --- a/next/submit.html +++ b/next/submit.html @@ -433,11 +433,7 @@ is only ready for submissions IOCCC submit server might be offline and unreachable as a website.

    To login, open https://submit.ioccc.org -in your browser. Fill in your login credentials and click “Login”. -It might look something like:

    -

    submit server login page screenshot

    +in your browser. Fill in your login credentials and click “Login”.

    NOTE: if the contest is NOT open you will see something like this instead:

    The contest is NOT yet open for submissions.
    @@ -452,22 +448,48 @@ details. After that you will have to log back in.

    Once you’ve logged in, you will see submit slots. Each slot is for one submission so if you update a submission, make sure you choose the right one so you do not replace the wrong one!

    -

    Here is what it looks like without any uploads and no slot selected:

    -

    submit server submission slots list to select from with no slot selected
- screenshot

    -

    Select a slot and then select a file by clicking the button “Choose File”. After -doing this, it should look something like:

    -

    submit server submission slot selected with a file chosen to be uploaded screenshot

    -

    If you need to change the file to upload, you can mouseover the file and click -it. If you wait a moment it’ll show the current filename.

    +

    It will show text and radio buttons for each row (up to 10 numbered 0 through +9):

    + + + + + + + + + + + + + +
    SelectSlot Information
    0: [N]Status: slot empty
    +

    The [N] is a radio button. Tick that to select that slot. Then further down +the page you’ll see the text along the lines of:

    +
    +

    IMPORTANT: Upload only XZ compressed tarballs whose filename is:

    +

    submit.7ec754d4-8670-421a-a1b6-7dd3dc5f215e-SLOT.TIMESTAMP.txz

    +

    where SLOT is a slot number, and TIMESTAMP is the build time as a Unix +timestamp.

    +

    We highly recommend that you use mkiocccentry(1) to create your submit file as +it must pass the txzchk(1) sanity checks, and when the uncompressed tarball is +untarred, the resulting directory must pass chkentry(1).

    +
    +

    NOTE: the 7ec754d4-8670-421a-a1b6-7dd3dc5f215e is your UUID. MAKE SURE +YOU CHANGE IT TO YOUR UUID!

    +

    NOTE: the SLOT and TIMESTAMP in the filename are generated based on +your input in mkiocccentry(1).

    +

    Now select the slot you need and then scroll down and click the link that says: +Choose File. A file select option in your browser should open up. Browse for +your XZ compressed tarball that was generated by mkiocccentry(1) and +then click whatever button your browser has to upload the file.

    +

    You can see the filename of your **XZ compressed tarballthat was **generated bymkiocccentry(1)** you're about to upload if you mouseover it and wait a moment; if you have made a mistake in your file selection, you may click the link that saysChoose File` again. Fix your mistake by choosing the correct +file in the file selection pop-up in your browser.

    Once you’re certain you have selected the correct file, click “Submit”, below the file selection step.

    When it’s uploaded it should say something like:

    -

    • Uploaded file: submit.9971ada4-b6ae-427d-a7ec-e67a30362cdb-0.1740838915.txz

    +

    • Uploaded file: submit.9971ada4-b6ae-427d-a7ec-e67a30362cdb-0.1740838915.txz

    And in the slot it will give you important details like:

      @@ -480,6 +502,9 @@ tarball listing).
    • the upload date.
    • the SHA256 hash of the file.
    +

    Again the 7ec754d4-8670-421a-a1b6-7dd3dc5f215e is your UUID, the SLOT is the +slot number and TIMESTAMP is the build time as a Unix +timestamp.

    Now if you’re done, log out.

    If, on the other hand,, you upload a file that is too big you will see something like:

    @@ -499,27 +524,27 @@ then you MUST upload a properly named XZ compressed tarball, mkiocccentry!

    If later on you log in and see something like:

    -

    Status: server slot error code: 1! Use mkiocccentry to rebuild and resubmit to -this slot.

    +

    Status: server slot error code: 1! Use mkiocccentry to rebuild and resubmit to +this slot.

    or:

    -

    Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.

    +

    Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.

    -

    … or ANY other error then you MUST FIX your submission, repackage your +

    … or ANY OTHER ERROR then you MUST FIX your submission, repackage your tarball with mkiocccentry and upload to the same slot again! If you do not fix -this your submission WILL be rejected for violating Rule +this your submission WILL BE REJECTED for violating Rule 17!

    After the submission deadline is reached, you can log in to check the status of your submissions. This is what it will say when the judges have verified that your tarball / submission has been validated (NOT judged), by txzchk(1) and chkentry(1):

    -

    Status: the format of this submission has been validated.

    +

    Status: the format of this submission has been validated.

    IMPORTANT: this does NOT mean that your submission does not violate the rules or that everything is OK once the tarball is extracted; it simply means -the tests performed by the tools passed. If you find a flaw in the tool and +the tests performed by the tools passed. If you find a flaw in a tool and abuse it and the tests pass then you stand a significant chance of having your submission rejected for violating Rule 17, even if the tests passed.

    diff --git a/next/submit.md b/next/submit.md index c81131ad3..ea9ff15d2 100644 --- a/next/submit.md +++ b/next/submit.md @@ -11,11 +11,6 @@ might be offline and unreachable as a website. To login, open [https://submit.ioccc.org](https://submit.ioccc.org) in your browser. Fill in your login credentials and click "Login". -It might look something like: - -submit server login page screenshot **NOTE**: if the contest is NOT open you will see something like this instead: @@ -34,28 +29,50 @@ Once you've logged in, you will see submit slots. Each slot is for one submission so if you update a submission, make sure you choose the right one so you do not replace the wrong one! -Here is what it looks like without any uploads and no slot selected: +It will show text and radio buttons for each row (up to 10 numbered `0` through +`9`): -submit server submission slots list to select from with no slot selected
- screenshot +| Select | Slot Information | +| -------| -------------------- +| 0: [N] | Status: slot empty | -Select a slot and then select a file by clicking the button "Choose File". After -doing this, it should look something like: +The `[N]` is a radio button. Tick that to select that slot. Then further down +the page you'll see the text along the lines of: -submit server submission slot selected with a file chosen to be uploaded screenshot +> IMPORTANT: Upload only XZ compressed tarballs whose filename is: +> +> `submit.7ec754d4-8670-421a-a1b6-7dd3dc5f215e-SLOT.TIMESTAMP.txz` +> +> where `SLOT` is a slot number, and `TIMESTAMP` is the build time as a [Unix +timestamp](https://unixtime.org/). +> +> We highly recommend that you use `mkiocccentry(1)` to create your submit file as +it must pass the `txzchk(1)` sanity checks, and when the uncompressed tarball is +untarred, the resulting directory must pass `chkentry(1)`. -If you need to change the file to upload, you can mouseover the file and click -it. If you wait a moment it'll show the current filename. +**NOTE**: the `7ec754d4-8670-421a-a1b6-7dd3dc5f215e` is your UUID. **MAKE SURE +YOU CHANGE IT TO YOUR UUID**! + +**NOTE**: the `SLOT` and `TIMESTAMP` **in the filename** are generated based on +your input in `mkiocccentry(1)`. + +Now select the slot you need and then scroll down and click the link that says: +`Choose File`. A file select option in your browser should open up. Browse for +your **XZ compressed tarball** that was **generated by `mkiocccentry(1)`** and +then click whatever button your browser has to upload the file. + +You can see the filename of your **XZ compressed tarball` that was **generated +by `mkiocccentry(1)`** you're about to upload if you mouseover it and wait +a moment; if you have made a mistake in your file selection, you may click the +link that says `Choose File` again. Fix your mistake by choosing the correct +file in the file selection pop-up in your browser. Once you're certain you have selected the correct file, click "Submit", below the file selection step. When it's uploaded it should say something like: -> • Uploaded file: submit.9971ada4-b6ae-427d-a7ec-e67a30362cdb-0.1740838915.txz +> • Uploaded file: `submit.9971ada4-b6ae-427d-a7ec-e67a30362cdb-0.1740838915.txz` And in the slot it will give you important details like: @@ -69,6 +86,10 @@ tarball listing). - the upload date. - the SHA256 hash of the file. +Again the `7ec754d4-8670-421a-a1b6-7dd3dc5f215e` is your UUID, the `SLOT` is the +slot number and `TIMESTAMP` is the build time as a [Unix +timestamp](https://unixtime.org/). + Now if you're done, log out. If, on the other hand,, you upload a file that is too big you will see something @@ -91,16 +112,16 @@ package it with `mkiocccentry`! If later on you log in and see something like: -> Status: server slot error code: 1! Use mkiocccentry to rebuild and resubmit to -this slot. +> **Status: server slot error code: 1! Use mkiocccentry to rebuild and resubmit to +this slot.** or: -> Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot. +> **Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.** -... or **ANY** other error then you **MUST FIX** your submission, repackage your +... or **ANY OTHER ERROR** then you **MUST FIX** your submission, repackage your tarball with `mkiocccentry` and upload to the same slot again! If you do not fix -this your submission **WILL** be rejected for violating [Rule +this your submission **WILL BE REJECTED** for violating [Rule 17](rules.html#rule17)! After the submission deadline is reached, you can log in to check the status of @@ -108,11 +129,11 @@ your submissions. This is what it will say when the judges have verified that your tarball / submission has been validated (NOT judged), by `txzchk(1)` and `chkentry(1)`: -> Status: the format of this submission has been validated. +> **Status: the format of this submission has been validated.** **IMPORTANT**: this does **NOT** mean that your submission does not violate the rules or that everything is OK once the tarball is extracted; it simply means -the tests performed by the tools passed. If you find a flaw in the tool and +the tests performed by the tools passed. If you find a flaw in a tool and abuse it and the tests pass then you stand a significant chance of having your submission rejected for violating [Rule 17](rules.html#rule17), even if the tests passed. diff --git a/png/register.0_531x445-signup.png b/png/register.0_531x445-signup.png deleted file mode 100644 index 577d8bd88..000000000 Binary files a/png/register.0_531x445-signup.png and /dev/null differ diff --git a/png/register.1_633x163-verify.png b/png/register.1_633x163-verify.png deleted file mode 100644 index 15ffd1dec..000000000 Binary files a/png/register.1_633x163-verify.png and /dev/null differ diff --git a/png/register.2_590x253-verify-email.png b/png/register.2_590x253-verify-email.png deleted file mode 100644 index ca3c6a94f..000000000 Binary files a/png/register.2_590x253-verify-email.png and /dev/null differ diff --git a/png/register.3_428x205-confirm.png b/png/register.3_428x205-confirm.png deleted file mode 100644 index 1d35d9a3b..000000000 Binary files a/png/register.3_428x205-confirm.png and /dev/null differ diff --git a/png/register.4_657x446-subscribe.png b/png/register.4_657x446-subscribe.png deleted file mode 100644 index 0b4637b8e..000000000 Binary files a/png/register.4_657x446-subscribe.png and /dev/null differ diff --git a/png/register.5_487x154-done.png b/png/register.5_487x154-done.png deleted file mode 100644 index ca16c34e5..000000000 Binary files a/png/register.5_487x154-done.png and /dev/null differ diff --git a/png/register.6_413x657-welcome.png b/png/register.6_413x657-welcome.png deleted file mode 100644 index 9d2cf7350..000000000 Binary files a/png/register.6_413x657-welcome.png and /dev/null differ diff --git a/png/submit.change-file.png b/png/submit.change-file.png deleted file mode 100644 index de1064391..000000000 Binary files a/png/submit.change-file.png and /dev/null differ diff --git a/png/submit.contest-closed.png b/png/submit.contest-closed.png deleted file mode 100644 index 0ecc13311..000000000 Binary files a/png/submit.contest-closed.png and /dev/null differ diff --git a/png/submit.file-regex-error.png b/png/submit.file-regex-error.png deleted file mode 100644 index 45e833c7e..000000000 Binary files a/png/submit.file-regex-error.png and /dev/null differ diff --git a/png/submit.file-select.png b/png/submit.file-select.png deleted file mode 100644 index 21f00bc11..000000000 Binary files a/png/submit.file-select.png and /dev/null differ diff --git a/png/submit.first-login.png b/png/submit.first-login.png deleted file mode 100644 index 1900ebb38..000000000 Binary files a/png/submit.first-login.png and /dev/null differ diff --git a/png/submit.invalid-passwd.png b/png/submit.invalid-passwd.png deleted file mode 100644 index de7c0876b..000000000 Binary files a/png/submit.invalid-passwd.png and /dev/null differ diff --git a/png/submit.login.png b/png/submit.login.png deleted file mode 100644 index 2f7548c33..000000000 Binary files a/png/submit.login.png and /dev/null differ diff --git a/png/submit.no-file-selected.png b/png/submit.no-file-selected.png deleted file mode 100644 index 56942055c..000000000 Binary files a/png/submit.no-file-selected.png and /dev/null differ diff --git a/png/submit.passwd-changed.png b/png/submit.passwd-changed.png deleted file mode 100644 index 41ec6bf9b..000000000 Binary files a/png/submit.passwd-changed.png and /dev/null differ diff --git a/png/submit.pw-change-err.png b/png/submit.pw-change-err.png deleted file mode 100644 index de7c0876b..000000000 Binary files a/png/submit.pw-change-err.png and /dev/null differ diff --git a/png/submit.slot-file.png b/png/submit.slot-file.png deleted file mode 100644 index d484218a2..000000000 Binary files a/png/submit.slot-file.png and /dev/null differ diff --git a/png/submit.slots.png b/png/submit.slots.png deleted file mode 100644 index b53f2935e..000000000 Binary files a/png/submit.slots.png and /dev/null differ diff --git a/png/submit.status-updated.png b/png/submit.status-updated.png deleted file mode 100644 index 42c30bb52..000000000 Binary files a/png/submit.status-updated.png and /dev/null differ diff --git a/png/submit.submission-uploaded.png b/png/submit.submission-uploaded.png deleted file mode 100644 index 9ba1b4a1a..000000000 Binary files a/png/submit.submission-uploaded.png and /dev/null differ