Results 1 to 7 of 7

Thread: Your Rights to Accessible Health Care (USA)

  1. #1

    Your Rights to Accessible Health Care (USA)

    Here is a good article about this from the University of Alabama Spain Rehab Center Pushin' On newsletter, (Vol. 34(1), page 2-3).


  2. #2

    Don't have Adobe Flash Player available

    The document will not load. The home page just shows some hipster who should be baited with paleo.

    This page requires you to have Adobe Flash Player version later than 11.3 This content requires the Adobe Flash Player.

    Do I look that stupid that I would use malware from Adobe?

    I use viewer built into Chrome, Xpdf or GhostView wrapper with GhostScript to view PeDoFiles.

    These silly page turning things make websites inaccessible which are illegal in Australia. The hipster may also get a white cane inserted.

  3. #3
    Works fine for me. Tons of sites required Adobe Flash player. Don't understand your reference to it as malware.

    Thanks for bumping this up so that those who want this information and have Flash player can access it!


  4. #4

    Flash obfuscation

    Quote Originally Posted by SCI-Nurse View Post
    Tons of sites required Adobe Flash player. Don't understand your reference to it as malware.
    The Flash obfuscated link is here:

    The web hipsters who do those sites will get flamed with nitrous oxide acetylene or plasma.

    Adobe software is a rootkit or backdoor so I simply won't use it.

    See how much Adobe care about their users here:
    The trend is in the wrong direction.

    There is no need for proprietary Flash as it has been superseded by the W3C's HTML 5 for some time now.

    Page turners turn the not very accessible PeDoFile into totally inaccessible images. The novelty is of no value. Sometimes screen readers are able to extract and read text from PeDoFiles if the text is in a single column of no more than 80 characters. My feeble eyes can still read on screen if 80 character columns can be made to occupy the whole width.

    Someone wanted to do page turners for PeDoFiles on our companies website and I had to fire off a very stern warning.

  5. #5
    Moved hijacked thread to the Computer forum. Edited version still remains in original forum.


  6. #6
    Should I click on a link to upgrade Flash?
    Rock bottom is relative to how high you bounce when you hit.
    --General George Patton

    Complex problems need to be solved collectively.
    ––Paul Nussbaum

  7. #7

    I only run malware in tea bag Windows snap shot

    Quote Originally Posted by PN View Post
    Should I click on a link to upgrade Flash?
    I don't click.

    Chrome updates it and I have a cron job that does:-
    apt-get update && \
    apt-get install flashplugin-nonfree && \
    update-flashplugin-nonfree --install
    for Mozilla. However, these are disabled and require confirmation to activate in each case. I also have tools to pull flash apart and analyze them which you should always do before playing them. The flash player itself is a root kit. It is so bad that it _is_ malware. Too much of a pain to run in chroot, so I don't run it. Also, not all flash sites are compatible with Lightspark which I trust more.

    Browser plugins often must run in the same chroot as the browser and so may compromise that browser!

    I have Adobe Reader in its own chroot for playing DRMed PeDoFIles. Each chroot has Debian package manager and just what is required to run the app. Packages are updated as root. App only runs as user via chroot helper program below (which must be compiled and setuid root so ignore the BINFMTC):-

    /*BINFMTC: -O -Wuninitialized -Werror -pedantic-errors
    This needs to be setuid root (i.e. mode 04750) for Linux.
    It can not be run as a script. Makes no noise as no <stdio.h>.
    Returns a non-zero status on failure otherwise returns COMMAND status.
    This must not be run as root otherwise we still have CAP_SYS_CHROOT
    and can chroot back!
    I think the coreutils chroot is broken.
    Usage: chrootordie NEWROOT COMMAND ARGS (including argv[0])
    Including argv[0] is more flexible and allows multiple wrappers,
    but with very long initial command line. Change argv+3 to argv+2
    if you do not want this or align with historical implementations.
    Don't fill the chroot with devices that expose root or proc.
    Being able to supply argv[0] is sometimes handy
    chrootordie /var/amd64 /bin/echo echo "Hello, world!"
    chrootordie /var/amd64 /bin/dash sh -c 'echo "Hello, world!"'
    #include <unistd.h>
    #include <assert.h>
    #define ordie(a) (void)((a)?0:(_exit(123),-1))
    int main(int argc, char **argv, char **envp)
        uid_t ruid;
        assert((ruid=getuid())>0); /* cowardly refuse to run as root */
        assert(chdir(argv[1])==0); /* check dir first */
        assert(geteuid()==0); /* need root */
        assert(chroot(argv[1])==0); /* do it as root */
        assert(setuid(ruid)==0); /* no longer need CAP_SYS_CHROOT */
        assert(geteuid()>0); /* cowardly refuse to run as root */
        (void)setsid(); /* no controlling TTY for GUI apps */
    /* Now we can't chroot back */
    /* Run COMMAND with ARGS and environ */
        return 127;
    Some example scripts:-

    G_SLICE=always-malloc \
    LD_LIBRARY_PATH=/usr/local/seamonkey \
    exec /usr/local/bin/chrootordie /var/i386 \
    /usr/local/seamonkey/seamonkey-bin \
    /usr/local/seamonkey/seamonkey-bin \
    "$@" 0</dev/null 2>/tmp/${0##**/}.$LOGNAME 1>&2 \
    3<&- 4<&- 5<&- 6<&- 7<&- 8<&- 9<&- &
    umask 066
    chrootordie /var/i386 \
    /opt/Adobe/Reader9/bin/acroread \
    acroread "$@" 0</dev/null 2>&1 3<&- 4<&- 5<&- 6<&- 7<&- 8<&- 9<&- | \
    setsid logger -t acroread -p \
    1>&- 2>&- 3<&- 4<&- 5<&- 6<&- 7<&- 8<&- 9<&- &
    Last edited by zagam; 03-06-2017 at 10:25 PM. Reason: Readability and examples

Similar Threads

  1. Your Rights to Accessible Health Care (USA)
    By SCI-Nurse in forum Care
    Replies: 3
    Last Post: 03-06-2017, 09:20 AM
  2. Replies: 0
    Last Post: 04-08-2003, 11:20 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts