The Clue of the Hissing Serpent

The Clue of the Hissing Serpent is Volume 53 in the original The Hardy Boys Mystery Stories published by Grosset & Dunlap.

The Clue of the Hissing Serpent
AuthorFranklin W. Dixon
CountryUnited States
LanguageEnglish
SeriesThe Hardy Boys
GenreDetective, mystery
PublisherGrosset & Dunlap
Publication date
1974
Media typePrint (hardback & paperback)
Pages181 pp
ISBN0-448-08953-X
OCLC1009042
LC ClassPZ7.D644 Cm
Preceded byThe Shattered Helmet 
Followed byThe Mysterious Caravan 

This book was written for the Stratemeyer Syndicate by Andrew E. Svenson in 1974.[1]

Plot summary

The Hardy brothers and Chet meet a wealthy balloonist named Albert Krassner, who is in possession of the Ruby King, a valuable life-sized chess piece that is the prize for a chess tournament. The boys soon learn that a gang wants to steal the Ruby King. Then the Ruby King mysteriously disappears from the Krassner safe, sending the Hardy Boys to Hong Kong. There they capture the gang and find the Ruby King.

gollark: As if that's possible.
gollark: Fearsome.
gollark: I might have to release apioforms from the beecloud.
gollark: It must comfort you to think so.
gollark: > There is burgeoning interest in designing AI-basedsystems to assist humans in designing computing systems,including tools that automatically generate computer code.The most notable of these comes in the form of the first self-described ‘AI pair programmer’, GitHub Copilot, a languagemodel trained over open-source GitHub code. However, codeoften contains bugs—and so, given the vast quantity of unvettedcode that Copilot has processed, it is certain that the languagemodel will have learned from exploitable, buggy code. Thisraises concerns on the security of Copilot’s code contributions.In this work, we systematically investigate the prevalence andconditions that can cause GitHub Copilot to recommend insecurecode. To perform this analysis we prompt Copilot to generatecode in scenarios relevant to high-risk CWEs (e.g. those fromMITRE’s “Top 25” list). We explore Copilot’s performance onthree distinct code generation axes—examining how it performsgiven diversity of weaknesses, diversity of prompts, and diversityof domains. In total, we produce 89 different scenarios forCopilot to complete, producing 1,692 programs. Of these, wefound approximately 40 % to be vulnerable.Index Terms—Cybersecurity, AI, code generation, CWE

References


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.