TheImpossible Years is a 1968 American comedy film directed by Michael Gordon, and starring David Niven. The film also features Lola Albright, Chad Everett, Ozzie Nelson in his final film appearance, and Cristina Ferrare, who was 17 years old at the time the film was shot. It is based upon the 1965 play of the same name by Bob Fisher and Arthur Marx, the son of Groucho Marx, and was adapted for the screen by George Wells.
Jonathan Kingsley is a professor of psychiatry at the local university. An author of numerous books on parenting, he and wife Alice are raising two teenage daughters. The elder, Linda, 17, begins to display uncharacteristic behavior: walking as if on air, smiling incessantly for no reason, cleaning up her room daily, showing politeness toward her little sister, and more. It is suspected that she has lost her virginity while on a school field trip to Catalina Island, and Kingsley's general practitioner confirms this. Linda, while being interrogated, admits as much, and she reveals that she is married. She insists on concealing the identity of her husband until the film's conclusion.
MGM bought the film rights to the play in 1965 for $350,000.[2] George Wells completed the script by March 1966.[3] MGM announced it for production in August 1966. The movie was greenlit by the team of Robert O'Brien and Robert M. Weitman.[4] Filming took place in October 1967.
At one stage, Peter Sellers was announced for the lead[5] but by May, David Niven had been signed. Christina Ferrare, who played Niven's nubile daughter, had been under contract to 20th Century Fox for a year.[6] The film featured the final movie performance of Ozzie Nelson.[7]
LinkedIn and 3rd parties use essential and non-essential cookies to provide, secure, analyze and improve our Services, and to show you relevant ads (including professional and job ads) on and off LinkedIn. Learn more in our Cookie Policy.
Despite this, I feel blessed. For better or worse, growth and hardship are two sides of the same coin. This year was my once in a lifetime opportunity to step up to the plate in a way I never had to before. I had to grow personally and professionally to survive this year, as did we all. I am sharing three major lessons for me to reflect on in future years when things are easier again:
3. Be grateful for the little things. I never thought I would take for granted the ability to drive up to a coffee shop an enjoy a casual bite to eat. That I would miss using my building's underequipped basement gym. That I would miss the smiles of strangers now hidden underneath masks. I tried to be outside as much as the weather allowed this year, and recently, have been miserably running in winter gear.
The TL2 project (that became FZS) grew its workforce slowly, ever since 2007, as we covered more geographic ground, or met a new need. ICCN grew quickly after 2014 with a single grant and a neophyte head warden. His job was apparently accomplished by surrounding himself with staff holding the right titles: researcher, community organizer, public relations expert. ICCN headquarters, 100 km from the nearest park border, was filled with sedentary experts.
Most new park guards were sent to the field, their job was known, park protection. But, ICCN had no funds for the operations of their non-guard staff. In Sept 2021, I found over 50 employees still sitting at ICCN headquarters in Kindu. Many of them sitting there for more than 6 years.
It was not fair; everyone employed by ICCN needs a chance to show what they can do. It does not sweeten the situation for ICCN to see their FZS counterparts working in the park and getting paid much higher salaries. A critical complication is that ICCN workers are state employees; FZS, even as the co-management partner, does not have the final say in their employment fate. The Direction of ICCN in Kinshasa is the employer.
The top guards are truly dedicated; We moved through the park together to review guards at all the posts. It was strange, as the daughter of a pacifist, who was a conscientious objector during WWII, to be accompanied by bodyguards and saluted by armed park guards, but the leaders of the guard force understood well the importance of discipline and well-defined objectives.
During the year 2022 we grew from 8 patrol posts to 10, making the park more secure and integrating more of the bufferzone villages into our efforts. We marked the park border through an important area, and created a community reserve outside the park. More about these incremental successes in the next posts.
No doubt you made the best of a difficult or impossible situation, but it sounds like you succeeded at the most important task: protection of the Park during your tenure. Best of luck to your successor.
We started this blog in 2007 when we took up the challenge of the TL2 area, a mainly forested wilderness block in the center of the Democratic Republic of Congo that had never been explored. A small American NGO, Lukuru, took us on. John trained field teams. Soon we and our teams were piling up discoveries: new species, new distributions, new dangers, new friends, and beautiful new places to walk, watch and be at home. For more about TL2 and our new next adventure _read on.
Connatre et Protger = Know and Protect. Our mission is to assist the Democratic Republic of Congo in the conservation of its rare and/or disappearing species and to promote knowledge and protection of its least altered and largest wilderness areas. These latter help global climatic stability and nurture key biodiversity that, in turn, nurtures the human world. For more_read here.
While traveling by air, I checked this laptop in my luggage to make it easily accessible to border agents, both domestic and foreign, to tamper with if they chose to. When staying in hotels, I left the laptop sitting on the desk in my room while I was away during the day, to make sure that any malicious housekeepers with permission to enter my room, or anyone else who broke into my room, was free to tamper with it if they chose to. I also put a bunch of hacker stickers all over it, hoping that this would make it a more enticing target.
For example, in March 2017, before flying to Amsterdam to attend a Tor Project meeting with developers, volunteers, and advocates for the open-source anonymity network, these were the checksums I generated:
Ten days later, after I had returned from my trip, I generated another set of checksums. They all turned out to be exactly the same, which allowed me to confirm that the data on my hard disk had not changed at all.
I had hoped that the BBB would provide power to the SPI flash chip, allowing me to read and write directly to that chip. But instead the BBB immediately powered off. It turns out that, the way this specific laptop was wired, the power for the SPI chip was not isolated from the rest of the system. In order to provide power to that chip, I also needed to provide power to rest of the components of the motherboard, and that takes more watts than my BBB was able to handle. This was annoying because one of the reasons I chose a Lenovo computer as my honeypot laptop is because I have had success doing this exact process on other Lenovo computers in the past, dumping the BIOS firmware by connecting a BBB to the SPI flash chip.
So I decided to change strategies. Instead of dumping the BIOS firmware by connecting wires directly from the SPI flash chip, I would instead use a piece of software called chipsec, running on the honeypot laptop itself, to dump the firmware. However, this strategy has a few downsides compared to directly connecting to the chip:
In order to use chipsec, I set up a USB stick with the operating system Ubuntu (another popular Linux distribution). With the hard disk removed from the honeypot laptop, I plugged in my Ubuntu USB stick, powered on the laptop, and booted to Ubuntu. I put a copy of chipsec on an SD memory card, which I also plugged into the laptop. From there, I was able to run a specific chipsec command to dump the BIOS firmware and save it to the SD card, which I could then inspect on my other computer.
Looking at two BIOS firmware images that had different checksums, I was able to use UEFITool to extract the same components from both, and then generate new checksums for those individual components to see if they matched. I discovered that there was only one small part of the firmware images that differed, and that part did not include any programs. It turns out, each time I powered on the honeypot laptop and opened the boot menu to tell it to boot from my Ubuntu USB stick, it saved information related to booting to a USB stick in that section of the firmware, and this information was slightly different each time, which caused the firmware images to always have different checksums.
So I amended my plan for detecting tampering in the BIOS firmware. To compare firmware images from before and after my trip, I would have to open each image in UEFITool, extract all of the components except for the one that I knew changed, generate checksums for those components, and then compare those checksums to make sure they matched.
Traveling with a honeypot laptop was a lot of work. It required spending a few hours both before and after each trip if I hoped to actually catch an evil maid attacker in the act. So after two years without catching anyone, I have decided to retire the project.
I was able to do this entire project with 100% free and open source software, thanks to projects like Debian and Ubuntu and tools like dd, sha256sum, flashrom, chipsec, and UEFITool. Other than the honeypot laptop itself, you can buy all of the hardware tools I used, like screwdrivers, a USB enclosure, and a BeagleBone Black, for less than $100.
After graduating, I was given the opportunity to attend Suffolk University. It was an opportunity that I had to take for myself, my friends, my supporters, and kids who were younger than me to show them that anything that seems impossible is possible with hard work.
3a8082e126